- From: <bugzilla@jessica.w3.org>
- Date: Wed, 20 Mar 2013 10:04:14 +0000
- To: public-html-admin@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21347 Bug ID: 21347 Summary: Editorial suggestion for section 2. Classification: Unclassified Product: HTML WG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: trivial Priority: P2 Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) Assignee: faulkner.steve@gmail.com Reporter: tink@tink.co.uk QA Contact: sideshowbarker+html-a11y-api@gmail.com CC: mike@w3.org, public-html-admin@w3.org, public-html-bugzilla@w3.org, public-html-wg-issue-tracking@w3.org 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." -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 20 March 2013 10:04:15 UTC