Michael was supposed to do this for states and properties as it is a little
more complicated than roles.
For example, HTML 5 booleans are not like ARIA booleans. Michael had text
for that he was working on in the face to face in San Diego.
e.g. HTML 5 you have the checked attribute on an element, which is a
boolean, without a value indicating it is true. for ARIA you must have
checked="true"
Michael, please work with Steve.
Rich
Rich Schwerdtfeger
From: Steve Faulkner <faulkner.steve@gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>,
Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, James Craig
<jcraig@apple.com>
Date: 01/27/2012 04:35 AM
Subject: ARIA processing in host langauges
In section 7. Implementation in Host Languages of WAI-ARIA 1.0
It states that
"User Agent processing for roles is defined in the WAI-ARIA User Agent
Implementation Guide [ARIA-IMPLEMENTATION]." [1]
while for aria-* attributes it states:
"When these attributes appear in a document instance, the attributes will
be processed as defined in this specification." [1]
Why are the processing rules defined in the UA gudie for role, but not for
aria-* ?
[1] http://www.w3.org/TR/wai-aria/host_languages#host_general_role
[2] http://www.w3.org/TR/wai-aria/host_languages#host_general_attrs
--
with regards
Steve Faulkner
Technical Director - TPG
www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar -
www.paciellogroup.com/resources/wat-ie-about.html
