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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10914

--- Comment #9 from steve faulkner <faulkner.steve@gmail.com> 2010-10-04 13:16:13 UTC ---
(In reply to comment #7)
> (In reply to comment #5)
> > Does the WAI-ARIA draft define the format for the role attribute?
> ARIA defines the characteristics of the attribute
> http://www.w3.org/TR/wai-aria/host_languages#host_general_role
> ...but says the host language "will provide" it.
> (In reply to comment #4)
> > if this is correct where is the role attribute defined in the html5 spec?
> http://www.whatwg.org/specs/web-apps/current-work/#global-attributes says: "To
> enable assistive technology products to expose a more fine-grained interface
> than is otherwise possible with HTML elements and attributes, a set of
> annotations for assistive technology products can be specified (the ARIA role
> and aria-* attributes)."
> I guess for avoidance of doubt, the HTML5 spec should be edited to make it
> unambiguous that the paragraph I quoted means to "provide" the attributes whose
> characteristics are defined in
> http://www.w3.org/TR/wai-aria/host_languages#host_general_role
> and
> http://www.w3.org/TR/wai-aria/host_languages#host_general_attrs
> (In reply to comment #6)
> > The Role Attribute draft defines the format as above, see link in comment #0.
> No, that's the old XHTML2 WG role attribute that allows URIs and CURIEs. That's
> not the ARIA-only role attribute that HTML5 is integrating with. ARIA was
> specifically modified to no longer normatively refer to the Role
> Attribute/Module draft, since the Role Attribute/Module draft doesn't represent
> consensus among ARIA implementors or reflect implementation reality. (AFAIK,
> implementations don't support CURIE resolution in role.)
> It's really unfortunate that work on
> http://www.w3.org/TR/2010/WD-role-attribute-20100916/ hasn't been terminated by
> publishing it as a tombstone Note, since the document now generates confusion
> about such as comment 0 suggesting that the document were normative over HTML5
> conformance checkers.

so the current editors draft of the ARIA spec states:

"An implementing host language will provide an attribute with the following
characteristics:

The attribute name MUST be role;
The attribute value MUST allow a token list as the value;
The appearance of the name literal of any concrete WAI-ARIA role as one of
these substrings MUST NOT in and of itself make the attribute value illegal in
the host-language syntax; and
The first name literal of a non-abstract WAI-ARIA role in the list of tokens in
the role attribute defines the role according to which the user agent MUST
process the element. User Agent processing for roles is defined in the WAI-ARIA
User Agent Implementation Guide [ARIA-IMPLEMENTATION]."


Which reads to me as if HTML5 MUST allow role="navigation menubar" as
conforming.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 4 October 2010 13:16:17 UTC