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

On 07/08/2018 21:37, Patrick H. Lauke wrote:
...
> The reason why placeholder is not advisable as a sole labelling 
> mechanism is because it has usability and accessibility (e.g. for COGA) 
> issues. But is that a reason not to have browsers expose it? Should they 
> expose it only if there's another accessible name, and just as an 
> accessible description? Or not at all?

For that matter, I could make an input with just, say, aria-label, and 
that gets exposed as the accessible name...e.g. just

<input aria-label="foo">

Should this be exposed by the browser to the accessibility API as "foo" 
or not, if there's nothing else giving the input a programmatic name?

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 Tuesday, 7 August 2018 20:47:04 UTC