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 HTML5 spec currently refers to ARIA as "Annotations for assistive technology products (ARIA)" This is innacurate. While the primary prupose at this time is to provide accessibility information to assistive technology, it is not intended as its exclusive purpose, as the WAI-ARIA spec states: "The WAI-ARIA specification neither requires or forbids user agents from enhancing native presentation and interaction behaviors on the basis of WAI-ARIA markup. Even mainstream user agents might choose to expose metadata or navigational features directly or via user-installed extensions; for example, exposing required form fields or landmark navigation. User agents are encouraged to maximize their usefulness to users, including users without disabilities." http://www.w3.org/WAI/PF/aria/introduction Request a change to the title of the ARIA section so the scope of ARIA is not so narrowly defined in HTML5 (http://dev.w3.org/html5/spec/embedded-content-0.html#annotations-for-assistive-technology-products-aria) and inlcude text simliar to the above to provide such guidance to all user agents.
(In reply to comment #0) > Request a change to the title of the ARIA section so the scope of ARIA is not > so narrowly defined in HTML5 > (http://dev.w3.org/html5/spec/embedded-content-0.html#annotations-for-assistive-technology-products-aria) > and inlcude text simliar to the above to provide such guidance to all user > agents. Do you have suggestion for a possible alternate title for the section?
(In reply to comment #1) > Do you have suggestion for a possible alternate title for the section? Some suggestions, in no particular order: 3.2.6 Use of WAI-ARIA Roles and Properties in HTML or 3.2.6 Using WAI-ARIA Roles and Properties in HTML or 3.2.6 Conformance Requirements for WAI-ARIA Roles and Properties in HTML or 3.2.6 WAI-ARIA Roles and Properties in HTML
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: While in theory ARIA could be exposed to other users, it would do a disservice to AT users to try to convince authors that ATs aren't the main target audience here.
Raised as issue 109 http://www.w3.org/html/wg/tracker/issues/109
Bug triage sub-team notes that this bug is in the escalation process. Assigning to Sam who sent the call for objections around http://www.w3.org/2002/09/wbs/40318/issue-109-objection-poll/results to track that this bug be handled as per outcome of the poll.
http://lists.w3.org/Archives/Public/public-html/2011Mar/0161.html
Specifically, I presume: http://www.w3.org/html/wg/wiki/ChangeProposals/ariasection#Details
The second change references a paragraph that is now absent. I've tried to put the suggested addition in the same relative location as the change proposal seems to have intended.
Checked in as WHATWG revision r5977. Check-in comment: apply wg decision http://html5.org/tools/web-apps-tracker?from=5976&to=5977