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 27096 - Unclear role+property usage
Summary: Unclear role+property usage
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Using ARIA in HTML (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-18 11:22 UTC by heydon
Modified: 2014-10-18 11:22 UTC (History)
2 users (show)

See Also:


Attachments

Description heydon 2014-10-18 11:22:34 UTC
In http://w3c.github.io/aria-in-html/#what-does-adding-a-role-do-to-the-native-semantics, under the heading "What adding a role does not do", it is reported that a button with a role of "heading" and an aria-level of "1" will become "(none) heading" in the accessibility tree. No indication that the level will/should be provided (eg. "level 1" or "first level") is given.

It is inadequate as well that the alt text for the image of this accessibility tree snippet just reads "a heading".