WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Placeholder

for

From: Patrick H. Lauke
Date: Mar 11, 2019 2:06PM

Some more related link dumpage:

https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Placeholder_Research
https://www.smashingmagazine.com/2018/06/placeholder-attribute/
https://github.com/w3c/html-aam/issues/84
https://www.nngroup.com/articles/form-design-placeholders/
http://davidmacd.com/blog/is-placeholder-accessible-label.html

And a note that there's an internal (not public) mailing list for the
WCAG working group, and that the issue of placeholder (in the context of
4.1.2 and 3.3.2, not generally in a "is it WCAG compliant" sense, as
that's too reductive a question) was discussed in August 2018, and I
believe we roughly hit on the consensus I expanded on in my previous
email (that for modern browser/AT combinations, for the most part,
placeholder is exposed as the accessible name of a form control, but
while it then arguably passes 4.1.2, it doesn't pass 3.3.2 under certain
conditions.

Note that, as ever, this has to be evaluated on a case-by-case basis
though (as the form in question may well be obvious even without an
explicit label, or there may be other things like a big fat "SEARCH"
submit button next to a text input which makes it fairly clear that the
form control is a search query input, for instance, etc)

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