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 27433 - role=tabpanel should be allowed on section element
Summary: role=tabpanel should be allowed on section element
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2014-11-25 20:11 UTC by Mark Sadecki
Modified: 2016-04-27 21:15 UTC (History)
5 users (show)

See Also:


Description Mark Sadecki 2014-11-25 20:11:40 UTC Implicit ARIA Semantics [1] currently limits the role attribute on the section element to the following values:

> alert, alertdialog, application, contentinfo, dialog, document, log, 
> main, marquee, region, search, status or presentation

However, the section element [2] could conceivably be used to mark up tabpanel content in a tab widget:

> The section element represents a generic section of a document or 
> application. A section, in this context, is a thematic grouping of content.
> Each section should be identified, typically by including a heading 
> (h1-h6 element) as a child of the section element.

In fact, the non-normative example that follows explicitly makes note of this use case:

> Examples of sections would be chapters, the various tabbed pages in a 
> tabbed dialog box, or the numbered sections of a thesis. A Web site's home 
> page could be split into sections for an introduction, news items, and 
> contact information.

Here is a simple example of this use case [3].  This example currently throws a validation error.

Recommend adding 'tabpanel' to list of roles allowed on the section element in Implicit ARIA Semantics [1]

Comment 1 Arron Eicholz 2016-04-27 21:15:37 UTC
HTML5.1 Bugzilla Bug Triage: Moved to Github issue:

To file additional issues please use the W3C HTML5 Issue tracker: Thanks!