-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid human text in attributes #3
Comments
Not sure what you mean here:
Attributes and elements are always written in English. When attributes require author-supplied strings, they are traditionally in the language of the document. However, because they are flat text strings, they cannot be formatted, nor can additional attributes be applied to those values, so for example in the first Canadian example, pronunciation of the text string will be impacted by the native language of the document (lang="en"), so screen readers may struggle with properly pronouncing 'Gouvernement' (en francais). |
Asking I18N to weigh in, MC will defer to their opinion |
FWIW, this is mentioned in i18n WG's guidance for spec developers. |
It's not clear to me what is the context that gave rise to the initial comment by @michael-n-cooper, so it's difficult to know what to say here. @xfq 's link certainly provides useful guidance. We strongly recommend that when designing markup you avoid creating attributes which contain text that a user will read. Unfortunately, although we made progress on this for XHTML2, we were unable to convince the HTML5 folks to provide better alternatives for |
An internationalization principle is that text should not be in attributes. Properties should be structured in a way not to use that design.
The text was updated successfully, but these errors were encountered: