This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10903 - provide an introduction to wai-aria in the wai aria section of the spec
Summary: provide an introduction to wai-aria in the wai aria section of the spec
Status: RESOLVED LATER
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, aria
Depends on:
Blocks: 10066
  Show dependency treegraph
 
Reported: 2010-09-30 20:53 UTC by steve faulkner
Modified: 2013-04-17 13:20 UTC (History)
8 users (show)

See Also:


Attachments

Description steve faulkner 2010-09-30 20:53:59 UTC
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."
Comment 1 Ian 'Hixie' Hickson 2010-10-11 22:14:52 UTC
Since this is the topic of an ongoing working group issue, I'll wait until the chairs have resolved the relevant issue before making any changes here.
Comment 2 steve faulkner 2010-10-12 09:03:21 UTC
added to HTML WG Issue http://www.w3.org/html/wg/tracker/issues/129
Comment 3 Ian 'Hixie' Hickson 2010-11-11 23:13:21 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: The chairs never got around to resolving their side of this, so I'll just close this without change. This will likely end up being done as part of that issue anyway.
Comment 4 steve faulkner 2013-01-21 13:29:28 UTC
revisit in 5.1