W3C home > Mailing lists > Public > public-html@w3.org > September 2010

[Bug 10914] New: Allow multiple space separated values for the ARIA role attribute

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 22:28:08 +0000
To: public-html@w3.org
Message-ID: <bug-10914-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10914

           Summary: Allow multiple space separated values for the ARIA
                    role attribute
           Product: HTML WG
           Version: unspecified
          Platform: All
               URL: http://dev.w3.org/html5/spec/content-models.html#annot
                    ations-for-assistive-technology-products-aria
        OS/Version: All
            Status: NEW
          Keywords: a11y, aria
          Severity: minor
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: martin.kliehm@namics.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, public-html-a11y@w3.org


The experimental HTML5 conformance checker throws an error when more than one
space separated value is used within a role attribute. However, the Role
Attribute Draft [1] defines

"The role attribute takes as its value one or more whitespace separated
TERMorCURIEorAbsURIs as defined in [RDFA-CORE]"

The HTML5 spec fails to specify yet that one or more values is allowed, but it
seems to be the base for conformance checker implementations. Therefore I
suggest to include the sentence above, unless it doesn't need to be specified
redundantly and it is a failure on the W3C validator to implement the Role
Attribute specification properly.

Use cases for multiple roles:

1. It would be appropriate for a horizontal main navigation to have
role="navigation menubar"

2. On flickr, headings can be edited when they receive focus. It's a heading
that should be included in the taborder via tabindex="0", but as soon as it
received focus it becomes a text input field. Therefore <h1 role="heading
textbox"> would make perfect sense as the element has the potential to be both:
Schrödinger's Heading.


[1]
http://www.w3.org/TR/2010/WD-role-attribute-20100916/#s_role_module_attributes

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 30 September 2010 22:28:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:19 UTC