This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
per http://www.w3.org/2011/01/aria-lexical-processing it appears to be the expectation of the PFWG that the HTML5 spec should include the role attribute among the set of attributes that are considered global attributes for the language, and should define the attribute. So this is a request to make the following specific changes to the spec: 1. Add the role attribute to the list of global attributes at http://dev.w3.org/html5/spec/elements.html#global-attributes 2. Add under http://dev.w3.org/html5/spec/content-models.html#annotations-for-assistive-technology-products-aria a new "The role attribute" subsection that gives a definition for the attribute
Is the WAI working group really ok with us doing our own thing here instead of them defining the role="" attribute? In the past when we've done this kind of thing all it's done at the cross-working-group level is cause strife.
(In reply to comment #1) > Is the WAI working group really ok with us doing our own thing here instead of > them defining the role="" attribute? In the past when we've done this kind of > thing all it's done at the cross-working-group level is cause strife. this is the source of the requests for this and related bugs http://www.w3.org/2011/01/aria-lexical-processing is this document sufficient indication or do you want an offical repsonse from the PFWG?
The HTML accessibility bug triage sub-team thinks this issue should be task force priority, adding the a11yTF keyword.
So what is this attribute's definition supposed to be?
HTML A11Y TF ACTION-112 http://www.w3.org/WAI/PF/HTML/track/actions/112 is to provide this content; elevated priority.
mass-move component to LC1
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: Did Not Understand Request Change Description: no spec change Rationale: see comment 4
(In reply to comment #7) > 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: Did Not Understand Request > Change Description: no spec change > Rationale: see comment 4 I have started on some text for this bug It is available as a google doc (if anybody has any issues with it in this form please say so) https://docs.google.com/document/d/162rNFTzl_GFdLHDrdoG-GGHsNAqGUtrjEZb2eKUo_bY/edit feel free to add comments.
Decision: http://lists.w3.org/Archives/Public/public-html/2012Jul/0122.html Change Proposal: http://www.w3.org/html/wg/wiki/ChangeProposals/ARIA_Processing
I'll take this one.
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: Accepted Change Description: https://github.com/w3c/html/commit/5a88e54ff0a4dffb90e06f69584e9048c8825d82 Rationale: Applied Working Group decision.