This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
3.4 Role Mapping: list item 2: Should this be a "must not"?. Depends on whether or not this is a normative document. Also need to add the list of abstract roles
According to the WAI-ARIA spec: "Q. What happens if the author uses an abstract role, or a role that does not map to a standard role for the platform accessibility API? A: This is defined in the spec: http://www.w3.org/TR/2009/WD-wai-aria-20090224/#ua_role_identify If a given role in the role attribute is abstract or has no mapping, skip that role. If no known role is found in the role attirbute, the UA will just act as if the role attribute was absent except it would still expose the role attribute's value in the xml-roles object attribute."
Changed the "should not" to "must not" and edited the Q/A a bit: Q. What happens if the author uses an abstract role, or a role that does not map to a standard role for the platform accessibility API? A: See WAI-ARIA 8.1.3 Step-by-step (links to ARIA spec). If a given role in the role attribute is abstract or has no mapping, skip that role. If no known role is found in the role attribute, the UA will just act as if the role attribute was absent except it would still expose the role attribute's value in the xml-roles object attribute.
(In reply to comment #2) > Changed the "should not" to "must not" and edited the Q/A a bit: > Where did you change this wording? Can you paste it in?
In Section 3.4 Role Mapping (http://www.w3.org/WAI/PF/aria-implementation/#mapping_role), changed "should not" to "must not" in bullet 2. In Section 6.5 (http://www.w3.org/WAI/PF/aria-implementation/#error-handling_roles), editorial rewording on the answer to the first question: Q. What happens if the author uses an abstract role, or a role that does not map to a standard role for the platform accessibility API? A: See WAI-ARIA 8.1.3 Step-by-step. If a given role in the role attribute is abstract or has no mapping, skip that role. If no known role is found in the role attribute, process it the same as if the role attribute is absent except expose the role attribute value in the xml-roles object attribute.