- From: Jonathan Avila <jon.avila@levelaccess.com>
- Date: Wed, 8 Aug 2018 18:46:58 +0000
- To: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
> 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". Jonathan Avila -----Original Message----- From: Patrick H. Lauke [mailto:redux@splintered.co.uk] Sent: Wednesday, August 08, 2018 1:49 PM To: Glenda Sims; Schnabel, Stefan Cc: w3c-wai-gl@w3.org Subject: Re: Bug: Firefox Accessibility Inspector reports placeholder attribute as eligible for accessible name On 08/08/2018 18:43, Glenda Sims wrote: ... > Code snippet: <input type="text" name="first" placeholder="First Name" > id="first"> ... > I believe it fails both > > * 1.3.1 Info and Relationships > o (based on F68 > https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F68 > <https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F68>) That techniques relates to programmatically determinable name. It's related to 4.1.2, not 1.3.1 ? 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? > * 2.5.3 Label in Name > o because the placeholder text fails to be the accessible name > based on F68 But I'd say it doesn't fail... 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 18:47:27 UTC