RE: Ref: HTML to Platform Accessibility APIs Implementation Guide

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

RE: Ref: HTML to Platform Accessibility APIs Implementation Guide

Steve Faulkner-2
Hi Sailesh,

you wrote:
Ref: HTML to Platform Accessibility APIs Implementation Guide
http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html
For accessible name / description calculation under 5.1 Input type="text" or
textarea element the suggested order is aria-labelledby, aria-label,
placeholder, then the host language's placeholder, label element and title
attributes
Comment-1:
The INPUT type=text / textarea are host language constructs. So I find it odd
that aria-attributes should take precedence unless there is a role attribute
that is present that changes the role declared by the host language.
Comment-2:
Having stated the above order of precedence, it goes on to say that when only
placeholder and label are present, the label takes precedence and should be
considered to calculate accessible name.
Then why does placeholder precede label element in the above order beginning
with aria attributes?

I created a bug and have part fixed and responded to your comments

you can respond to the bug (need to create a bugzilla account to do so)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16774


--
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