This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The opening paragraph of section 2 (Exposing HTML features that do not directly map to accessibility API properties), contains the following sentence: "When HTML roles, states and properties do not directly map to an accessibility API, and there is a method in the API to expose a text string, expose the undefined role, states and properties via that method." Suggest a slight editorial change to the last clause of the sentence (for greater clarity): "When HTML roles, states and properties do not directly map to an accessibility API, and there is a method in the API to expose a text string, the undefined role, states and properties should be exposed via that method." If "should" is inappropriate language for this section, then "can" could be used instead: "When HTML roles, states and properties do not directly map to an accessibility API, and there is a method in the API to expose a text string, the undefined role, states and properties can be exposed via that method."