RE: Bug: Firefox Accessibility Inspector reports placeholder attribute as eligible for accessible name

>I don't think the core discussion here was about whether or not 
>placeholder is allowed to count as a *visible label* (as indeed the text 
>disappears after user input, causing problems), but rather whether or 
>not it's kosher for placeholder to be included in the accessible name 
>computation by browsers. Two separate issues.

For the latter I already commented. If there is an alternative thread for the other issue, OK.
Besides of that, all of this deals with different aspects of the same original problem.

- Stefan

-----Original Message-----
From: Patrick H. Lauke <redux@splintered.co.uk> 
Sent: Thursday, August 9, 2018 9:28 AM
To: w3c-wai-gl@w3.org
Subject: Re: Bug: Firefox Accessibility Inspector reports placeholder attribute as eligible for accessible name



On 09/08/2018 07:41, Schnabel, Stefan wrote:
> When placeholder is allowed as visible label replacement by the group 
> (some screen readers treat that pragmatically already as such when no 
> label is declared) we need also a user agent requirement from the group 
> not to hide it on input focus. Some browsers hide placeholder, others 
> don’t.

I don't think the core discussion here was about whether or not 
placeholder is allowed to count as a *visible label* (as indeed the text 
disappears after user input, causing problems), but rather whether or 
not it's kosher for placeholder to be included in the accessible name 
computation by browsers. Two separate issues.

P
-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke

http://flickr.com/photos/redux/ | http://redux.deviantart.com

twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Thursday, 9 August 2018 07:32:52 UTC