21347 2013-03-20 10:04:14 +0000 Editorial suggestion for section 2. 2013-03-20 10:04:14 +0000 1 1 1 Unclassified HTML WG HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) unspecified PC Windows NT NEW P2 trivial --- 1 lwatson faulkner.steve mike public-html-admin public-html-bugzilla public-html-wg-issue-tracking sideshowbarker+html-a11y-api oldest_to_newest 84713 0 lwatson 2013-03-20 10:04:14 +0000 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."