- From: Steve Faulkner <sfaulkner@paciellogroup.com>
- Date: Thu, 19 Apr 2012 06:37:09 +0200
- To: "'Sailesh Panchang'" <spanchang02@yahoo.com>
- Cc: <public-html-comments@w3.org>
Hi Sailesh, Please refer to the bug I created from your comments. https://www.w3.org/Bugs/Public/show_bug.cgi?id=16774 regards Stevef -----Original Message----- From: Sailesh Panchang [mailto:spanchang02@yahoo.com] Sent: 16 April 2012 23:12 To: public-html@w3.org Cc: Steve Faulkner Subject: Calculating accessible name - order 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? Sailesh Panchang Deque Systems
Received on Thursday, 19 April 2012 04:37:59 UTC