WebAIM - Web Accessibility In Mind

E-mail List Archives

Dealing with ambiguous form fields when applying the new SC 1.3.5 Identify Input Purpose"

for

From: Detlev Fischer
Date: Nov 2, 2018 4:56AM

Hi,

this recently came up in a discussion at W3C's TPAC meeting of the
Accessibility Gudielines Working Group but John Foliot wasn't around
then, so I take it here to look for reactions from the wider community.

The Github login form (and other forms like it) https://github.com/login
allows users to supply either email or user name when logging in. This
creates a problem for using the autocomplete attribute to meet SC 1.3.5
"Identify Input Purpose". Should the autocomplete attribute not be used
here because input is not restricted to either of these values, or are
there still advantages of specifying just email OR username via the
autocomplete attribute? Would you pass or fail this login page (one
could argue that 'password' is sufficiently identified programmatically
by the type attribute)?

I have also created a COMPARE case here:
http://compare.accessiweb.org/index.php/Github_login,_username_or_email_(github.com)

If you want to contribute there, let me know, and we set you up.

Best,

Detlev

--
Detlev Fischer
Testkreis
Werderstr. 34, 20144 Hamburg

Mobil +49 (0)157 57 57 57 45

http://www.testkreis.de
Beratung, Tests und Schulungen für barrierefreie Websites


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus