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 27295 - role and aria-* content attributes should be reflected DOM attributes
Summary: role and aria-* content attributes should be reflected DOM attributes
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-10 18:42 UTC by James Craig
Modified: 2016-04-20 21:30 UTC (History)
11 users (show)

See Also:


Attachments

Description James Craig 2014-11-10 18:42:01 UTC
role and aria-* content attributes should be reflected DOM attributes.

Element.role should reflect @role.
Element.ariaLabel should reflect @aria-label. (all aria-* attires, not just this one)
Comment 1 Simon Pieters 2014-11-11 10:41:05 UTC
Why?

This goes against the original design of ARIA. ARIA was supposed to work in AT+browser combinations even if the browser does not support ARIA (like IE6). Using DOM attributes means that the information is not available as a content attribute in browsers that don't support the DOM attribute, which means it's not accessible.
Comment 3 Simon Pieters 2014-11-13 12:34:47 UTC
Those threads seem to be discussing getting the computed role and label. Not getting the attribute value (when it has multiple roles). And not setting. I don't see reflected DOM attribute mentioned.
Comment 4 Arron Eicholz 2016-04-20 21:30:02 UTC
HTML5.1 Bugzilla Bug Triage: 

This bug constitutes a request for a new feature of HTML. Our current guidelines, rather than track such requests as bugs or issues, is to create a proposal for the desired behavior, or at least a sketch of what is wanted (much of which is probably contained in this bug), and start the discussion/proposal in the WICG (https://www.w3.org/community/wicg/). As your idea gains interest and momentum, it may be brought back into HTML through the Intent to Migrate process (https://wicg.github.io/admin/intent-to-migrate.html).