- From: <bugzilla@jessica.w3.org>
- Date: Thu, 19 Apr 2012 04:34:55 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16774 --- Comment #1 from steve faulkner <faulkner.steve@gmail.com> 2012-04-19 04:34:54 UTC --- (In reply to comment #0) > 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 have rewritten the Input type="text" accessible name calculation steps. see http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html#calc-iput In regards to the aria-labelledby and aria-label taking precedence, this is how it is implemented (for user agents that support the attributes) in user agents for all elements. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Thursday, 19 April 2012 04:35:03 UTC