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 12557 - add heading to the list of allowed roles for hx's
Summary: add heading to the list of allowed roles for hx's
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-26 09:24 UTC by steve faulkner
Modified: 2011-08-10 01:06 UTC (History)
6 users (show)

See Also:


Attachments

Description steve faulkner 2011-04-26 09:24:42 UTC
the spec does not list headings as allowed roles for hx's

example
"h1 element that does not have an hgroup ancestor 	

heading role, with the aria-level property set to the element's outline depth 	

Role must be either link, menuitem, menuitemcheckbox, menuitemradio, tab, or treeitem"

for every other element that has a default role, the default role is allowed. 

suggest adding heading to the list of allwoed roles for h1 to h6 that do not have an hgroup ancestor.

example:

"Role must be either heading, link, menuitem, menuitemcheckbox, menuitemradio, tab, or treeitem"
Comment 1 brunoais 2011-04-26 09:26:21 UTC
Why should that be done?
Comment 2 brunoais 2011-04-26 09:27:35 UTC
(In reply to comment #1)
> Why should that be done?

I don0t understand well enugh
Comment 3 brunoais 2011-04-26 09:28:28 UTC
(In reply to comment #1)
> Why should that be done?

I don't understand what are you stating well enough
Comment 4 steve faulkner 2011-04-26 12:05:58 UTC
(In reply to comment #1)
> Why should that be done?

take a look at the follwoing section:
http://www.whatwg.org/specs/web-apps/current-work/multipage/content-models.html#wai-aria

(note: pointing to whatg as HTML5 has not been updated yet.)

for any element that has a 'Default implied ARIA semantic' (column 2 of table 2) that role is specifically allowed in the 'Restrictions' (column 3 of table 2) so unless there is a reasonable technical epxlanation why h1-h6 should be different then the default role should also be explicitly allowed on these elements.
Comment 5 Michael[tm] Smith 2011-08-04 05:02:09 UTC
mass-moved component to LC1
Comment 6 Ian 'Hixie' Hickson 2011-08-10 01:05:30 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: see diff given below
Rationale: Concurred with reporter's comments.
Comment 7 contributor 2011-08-10 01:06:15 UTC
Checked in as WHATWG revision r6402.
Check-in comment: <h1> is allowed to have its default role.
http://html5.org/tools/web-apps-tracker?from=6401&to=6402