WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2.1 - 1.3.5 - How to capture a violation?

for

From: Jeremy Echols
Date: Jul 27, 2018 3:39PM

I think ambiguity is a slippery thing to define in any kind of normative way. Better to just say "here's a list of terms that are always known to mean a specific thing". With a clearly defined taxonomy, you don't have to build any kind of AI to guess at fields, so the programmatic use of these fields is open to a much wider audience, which can be useful.

That said, "autocomplete" feels very wrong for this purpose. I feel like this should be a new attribute, like aria-purpose or something.

It also seems like this SC should have been rolled out slowly, especially given how much confusion it's generated. I could see this as a AAA failure with some intent to make it higher priority in the future. Those of us targeting AA are going to immediately fail without another massive audit we weren't prepared for. It may even simply put off some authors entirely, and cause them to say, "AA is getting too difficult; let's just support WCAG A", which is a major loss.

I do like the intent behind this, but it's definitely a tricky one.