16774 2012-04-18 13:05:49 +0000 placeholder name calculation 2012-05-15 16:13:55 +0000 1 1 1 Unclassified HTML WG HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) unspecified PC Windows NT RESOLVED FIXED a11y P2 normal --- 1 faulkner.steve faulkner.steve faulkner.steve hans.hillen mike public-html-admin public-html-bugzilla public-html-wg-issue-tracking surkov.alexander sideshowbarker+html-a11y-api oldest_to_newest 66794 0 faulkner.steve 2012-04-18 13:05:49 +0000 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? 66836 1 faulkner.steve 2012-04-19 04:34:54 +0000 (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. 66933 2 surkov.alexander 2012-04-23 04:35:22 +0000 Steve, it would be nice if you provided old and new wording. It's easier to track what was changed. 66963 3 faulkner.steve 2012-04-24 11:09:16 +0000 (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 66968 4 surkov.alexander 2012-04-24 13:32:04 +0000 (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.