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 9920 - Non-abstract role examples are incorrect
Summary: Non-abstract role examples are incorrect
Status: RESOLVED FIXED
Alias: None
Product: ARIA
Classification: Unclassified
Component: Core AAM (show other bugs)
Version: 1.0
Hardware: PC Windows XP
: P1 normal
Target Milestone: ---
Assignee: Andi Snow-Weaver
QA Contact: ARIA UA Implementors
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-14 10:03 UTC by Andi Snow-Weaver
Modified: 2010-06-29 12:37 UTC (History)
0 users

See Also:


Attachments

Description Andi Snow-Weaver 2010-06-14 10:03:07 UTC
http://www.w3.org/WAI/PF/aria-implementation/#mapping_role

If the element does not have a role attribute, or if the role attribute contains no tokens matching the name of a non-abstract WAI-ARIA role, the user agent MUST fall back on normal processing of the base markup for the element with the role attribute. For example, for <table role="log"> use the tag name "table" to determine what platform accessibility API role to use. For <input type="text" role="search">, use the platform accessibility API for a text input.

The examples in this paragraph seem to imply that there is no 'log' or 'search' role, when in fact there are both. I'd suggest changing that to 'foo' and 'bar' or perhaps to use abstract roles.
Comment 1 Andi Snow-Weaver 2010-06-29 12:37:40 UTC
Done.