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 11891 - add role attribute to list of global attributes and add definition for it
Summary: add role attribute to list of global attributes and add definition for it
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, WGDecision
Depends on: 11893
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-27 15:05 UTC by Michael[tm] Smith
Modified: 2012-08-22 23:45 UTC (History)
13 users (show)

See Also:


Attachments

Description Michael[tm] Smith 2011-01-27 15:05:21 UTC
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
Comment 1 Ian 'Hixie' Hickson 2011-02-16 09:52:50 UTC
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.
Comment 2 steve faulkner 2011-02-16 15:26:40 UTC
(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?
Comment 3 Martin Kliehm 2011-02-22 16:08:50 UTC
The HTML accessibility bug triage sub-team thinks this issue should be task force priority, adding the a11yTF keyword.
Comment 4 Ian 'Hixie' Hickson 2011-05-04 23:56:42 UTC
So what is this attribute's definition supposed to be?
Comment 5 Michael Cooper 2011-05-06 20:50:25 UTC
HTML A11Y TF ACTION-112 http://www.w3.org/WAI/PF/HTML/track/actions/112 is to provide this content; elevated priority.
Comment 6 Michael[tm] Smith 2011-08-04 05:17:37 UTC
mass-move component to LC1
Comment 7 Ian 'Hixie' Hickson 2011-08-16 05:03:22 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: Did Not Understand Request
Change Description: no spec change
Rationale: see comment 4
Comment 8 steve faulkner 2012-01-27 11:04:38 UTC
(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.
Comment 10 Edward O'Connor 2012-08-22 23:27:23 UTC
I'll take this one.
Comment 11 Edward O'Connor 2012-08-22 23:45:48 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: Accepted
Change Description: https://github.com/w3c/html/commit/5a88e54ff0a4dffb90e06f69584e9048c8825d82
Rationale: Applied Working Group decision.