Bug 16774 - placeholder name calculation
placeholder name calculation
Status: RESOLVED FIXED
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly)
unspecified
PC Windows NT
: P2 normal
: ---
Assigned To: steve faulkner
HTML a11y API spec bugbot
: a11y
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-18 13:05 UTC by steve faulkner
Modified: 2012-05-15 16:13 UTC (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description steve faulkner 2012-04-18 13:05:49 UTC
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?
Comment 1 steve faulkner 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.
Comment 2 alexander surkov 2012-04-23 04:35:22 UTC
Steve, it would be nice if you provided old and new wording. It's easier to track what was changed.
Comment 3 steve faulkner 2012-04-24 11:09:16 UTC
(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
Comment 4 alexander surkov 2012-04-24 13:32:04 UTC
(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.