- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Sep 2010 20:53:59 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10903 Summary: provide an introduction to wai-aria in the wai aria section of the spec Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: faulkner.steve@gmail.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org as the editor suggests in his change proposal "Add an introductory paragraph that explains what ARIA is before using the acronym. The exact text is left to editor discretion, but it should include an expansion of the acronym, an explanation of the purpose of the technology, and could include an example." http://lists.w3.org/Archives/Public/public-html/2010Jul/0051.html the information provided to authors about wai-aria is lacking. here is an example of the sort of information to provide "Introduction The Web Accessibility Initiative Accessible Rich Internet Applications (WAI-ARIA) Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, Dynamic HTML, JavaScript, Cascading Style Sheets, and related technologies. Currently, certain functionality used in Web sites inaccessible to some users with disabilities, especially people who rely on screen readers and people who cannot use a mouse. WAI-ARIA addresses these accessibility challenges by defining new ways for functionality to be provided to assistive technology. Desktop operating systems have long provided APIs to allow assistive technology products to access applications, by exposing the role of a control along with its states, properties, and values. WAI-ARIA allows web application developers to expose the same sorts of information for Web applications. This information is used by user agents to support the same accessibility APIs as used by desktop applications allowing authors to provide accessibility information consistent with their intent. With WAI-ARIA, developers can make advanced Web applications accessible and usable to people with disabilities. Authors often use a combination of scripting, event handlers, and CSS to create custom widgets. When there are native language features that provide the same semantic meaning and interaction behaviors as a custom widget, authors are strongly encouraged to use the native language features. In these cases, accessible user agents should have done most of the work to ensure these native language features support assistive technologies. If the author chooses to create a custom widget, thus changing the functionality of an existing HTML element, the author may need to add WAI-ARIA role and aria-* attributes to make it accessible. In these instances the author must follow the conformance rules for applying WAI-ARIA to HTML defined in this section as well as the rules for using WAI-ARIA defined in the [WAI-ARIA] specification." -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Thursday, 30 September 2010 20:54:01 UTC