- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 8 Aug 2018 20:08:10 +0100
- To: w3c-wai-gl@w3.org
On 08/08/2018 19:46, Jonathan Avila wrote: >> And, in Firefox and Chrome at least (possibly others, no time to test) the placeholder IS exposed by the browser as the input's programmatically determinable / accessible name. So how is it failing? > > If the placeholder is exposed as the name but doesn't provide a name for the field but rather an example value then it would fail some SC because the programmatic name isn't a name but rather something else. In the same we would fail an input for date who's aria-label was "mm/dd/yyyy". Yes, but I was responding specifically to the example Glenda provided, where the placeholder was used with "First name" as value... Getting back to the original topic: placeholder is currently one of the last resort attributes used to provide an accessible name to a control, in the absence of anything more suitable like a <label>, an aria-label, aria-labelledby or even a title attribute. We've identified that placeholder use as the sole form of labelling is strongly discouraged, but I believe we do at least partly agree here that the fact that it is used as a last resort for the accessible name calculation is correct? 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 Wednesday, 8 August 2018 19:08:40 UTC