Play Framework |

Enforcing good typography with Play Framework

Straight quotation marks and apostrophes (“, ‘) are easy to type but typographically they aren’t so great: Straight quotes come to us from the typewriter. In traditional printing, all quotation marks were curly. But typewriter character sets were limited by mechanical constraints and physical space. By replacing the curly opening and closing quotes with ambidextrous straight quotes, two slots became available for other characters. Word processors are not limited in this way. You can always get curly quotes. Compared to straight quotes, curly quotes are more legible on the page and match the other characters better. Therefore, straight quotes should … Continue reading Enforcing good typography with Play Framework

Play Framework: Adding a Lang Attribute

By Daniel Nixon

If we create a new Play Framework project

$ activator new play-scala play-scala

1	$ activator new play-scala play-scala

and then take a look at main.scala.html, we’ll see something like this.

@(title: String)(content: Html)

<!DOCTYPE html>

<html>
...

@(title: String)(content: Html)

<!DOCTYPE html>

<html>

...

Notice that the html element doesn’t have a lang attribute. That’s a problem. WCAG 2.0 Success Criterion 3.1.1 says: 3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A) And technique H57: Using language attributes on the html element says: The objective of this technique is to identify the default language of a document by providing the lang and/or xml:lang attribute on the html element. Identifying the language of the … Continue reading Play Framework: Adding a Lang Attribute