[Bug 27433] New: role=tabpanel should be allowed on section element


            Bug ID: 27433
           Summary: role=tabpanel should be allowed on section element
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: mark.sadecki+w3c@gmail.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org 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]

[3] https://rawgit.com/clrux/html5-tabpanel-test/master/index.html

You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 25 November 2014 20:11:48 UTC