WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Error identification for multiple

for

From: glen walker
Date: Aug 5, 2020 9:19AM

So more of a design question not a conformance question?

From the conformance side, 3.3.1 just says "the item that is in error is
identified and the error is described to the user in text". Whether the
error disappears when you move focus away is subjective on if it fails
"identified" and "described in text". Initially, it sounds like 3.3.1 is
ok. If the message disappears, does that mean the error is not identified
anymore? Maybe. But it sounds like the error is repeated in a list at the
top so it's still identified.

From the design side, it sounds very confusing and might be confusing for
all users, which is an ironic non-accessibility issue. At least all the
users have the same (bad?) experience. But perhaps the way it works makes
sense when you actually use it.

I don't see a need to limit the list of errors at the top. If you do limit
it, then how does the user know how many errors there are? Let's say you
limit it to 10 errors and there are 20 errors on the page. The user fixes
one of the errors, it disappears from the list, then another error appears
because there are still 19 errors. If they do that again and another error
appears, that could be frustrating. They're fixing errors but the list
keeps showing 10. When will it end?