Add Translatable Attributes section #906
Conversation
|
The section looks fine. Nit 1: I think it would make more sense to locate the section outside of 6.2. Functionally, it is an aspect of 6.3 (Values for States and Properties) because for those four properties, the value should be translated. So I'd put it under 6.3 (either as 6.3.1 or making it 6.4). Nit 2: We're using "States and Properties" rather than "Attributes" for all headings in Section 6 (modulo 6.5.x for some reason). Therefore would it make sense to rename the new section "Translatable States and Properties" or "Translatable State and Property Values"? |
|
Update to reference HTML spec |
index.html
Outdated
| @@ -8499,6 +8499,16 @@ <h3>Value</h3> | |||
| <h2>Values for States and Properties</h2> | |||
| <p>Many <a>states</a> and <a>properties</a> accept a specific set of tokens as <span>values</span>. The allowed values and explanation of their meaning is shown after the table of characteristics. The default value, if defined, is shown in <strong>strong</strong> type, followed by the parenthetical term 'default'. When a value is indicated as the default, the user agent MUST follow the behavior prescribed by this value when the state or property is empty or unspecified. Some <a>roles</a> also define what behavior to use when certain states or properties, that do not have default values, are not provided.</p> | |||
| </section> | |||
| <section> | |||
| <h2>Translatable States and Properties</h2> | |||
| <p>The values of the following <a>states</a> and <a>properties</a> should be translated when a page is localized:</p> | |||
There was a problem hiding this comment.
Perhaps:
In order to be understandable by assistive technology users, the values of the following states and properties need to be translated when a page is localized:
This revision:
- clarifies the reason for translation.
- Avoids normative sounding language when there is no clear subject for a normative requirement.
Resolves #755
Preview | Diff