This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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?
(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.
Steve, it would be nice if you provided old and new wording. It's easier to track what was changed.
(In reply to comment #2) > Steve, it would be nice if you provided old and new wording. It's easier to > track what was changed. hi alex, chnagefile here: http://dvcs.w3.org/hg/html-api-map/rev/d4a424424472#l1.84 to http://dvcs.w3.org/hg/html-api-map/rev/d4a424424472#l1.117
(In reply to comment #3) > (In reply to comment #2) > > Steve, it would be nice if you provided old and new wording. It's easier to > > track what was changed. > > hi alex, > > chnagefile here: http://dvcs.w3.org/hg/html-api-map/rev/d4a424424472#l1.84 to > http://dvcs.w3.org/hg/html-api-map/rev/d4a424424472#l1.117 ok, thank you. html diff is not very friendly :) but it's ok.