Support for the namespaced role attribute is going to be removed. We are
simplifying ARIA to make it more palatable for other browsers to implement it,
and less confusing for authors.
If you need to be compatible with Firefox 2, do:
<div role="wairole:menuitem" aaa:checked="true"> <!-- In FF2 still use
setAttributeNS() for aaa:checked -->
If Firefox 3 support is good enough for you, do:
<div role="menuitem" aria-checked="true"> <!-- In FF3 all of ARIA can be
declared directly in markup-->
Firefox 3 is scheduled to be shipped by January.
Notice that in both cases you use |role|, and not |xhtml:role| or |xhtml2:role|
The hardcoded "wairole:" prefix for the role value is still available for use in
text/html, but is no longer required in Firefox 3. The WAI roles can now be
accessed directly without a prefix.
- Aaron
Aaron Leventhal
IBM web accessibility architect
Mozilla accessiblity lead
http://www.mozilla.org/access
Doesn't that break XML compatibility? In any XML document, I should be able to
declare the XHTML namespace with whatever prefix I choose (according to
Namespaces in XML) and use that prefix to refer to the ROLE attribute.
I don't understand how an XML implementation can conform to the Namespaces
Recommendation and fail to support prefix:role for any prefix declared with
the appropriate namespace URI.
Sorry, I was talking about its use in HTML, and should have said that. That's
still by far the main use case.
When using it in XML (such as XUL or SVG), you can still declare the xhtml
namespace and use the role attribute from there. I'm working with Opera to
formalize the proposal and will post it here and on wai-xtech for feedback. So
you will have ample time to catch any errors on our part.
- Aaron