Editor: Steve Faulkner (firstname.lastname@example.org)
Date: February 26, 2010.
Please address feedback to the HTML Working Group mailing list (email@example.com).
Allow the a element to have a role attribute with values other than role="link".
"@cwilso I think we both know Web developers aren't going to be using the specs as a guide of what they can and can't use"
The use of ARIA in this case provides a way for developers to provide the same information about a custom control they have developed using the a element to assistive technology AT users that is available to everyone else.
Flagging the use of ARIA as a conformance error will most likely deter those people using conformance checkers from adding the ARIA attributes, while leaving an inaccessible control. The only people disadvantaged by the conformance requirements in the current spec are users with disabilities.
Remove the first row of the first table in the section 3.2.6 Annotations for assistive technology products (ARIA).
code/content to be removed:
<a href="text-level-semantics.html#the-a-element">a</a> element that represents a <a href="interactive-elements.html#hyperlink">hyperlink</a></td><td>
Add this as the first row of the second table in the section 3.2.6 Annotations for assistive technology products (ARIA).
code/content to be added:
<a href="text-level-semantics.html#the-a-element">a</a> element that represents a <a href="interactive-elements.html#hyperlink">hyperlink</a></td>
<td>If specified, role may be one of the following
button, link, menuitem, menuitemcheckbox, menuitemradio, radio, slider, scrollbar or progressbar.</td>
- Authors will not be detered (by conformance error messages) from using ARIA to provide name, role and state information to AT users that matches the information provided to other users.
- Developers will be able to use conformance checkers to check their code for correct syntax,values combinations etc of ARIA attributes providing an indication of whether they will actually work as per the ARIA spec, rather than to be told whether their use is prohibited by the HTML5 spec or not.
- HTML5 author conformance requirements will better reflect the real world uses of the a element.
- Will no longer provide an indirect mechansim for automated conformance checkers to flag potential non-conforming uses of the a element, which would otherwise be uncheckable.
Conformance Classes Changes
refer to negative effects.