WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [External Sender]What are the semantics in html?

for

From: Mallory
Date: Jul 16, 2020 10:19AM

[oh boy, first time back to email in a week]
> Patrick H. Lauke wrote,
>
> So where would you report things that take focus when they shouldn't?
> Or do you just pass them (but perhaps mention this as a best practice
> issue)?
>

I do similar as Steve: I've run across pages with tens of focusable things (the devs thought it was required for screen reader users to read the content). It made using the page with keyboard impossible. Although again, can't use 2.1.1 for that, as that says only that things CAN be operated with keyboard, not that they can be operated sanely by humans in practicality.

If it's an item here or there, I mention it. Most places I audit at, we're allowed to make "UX" tickets, for things that make it difficult for users with disabilities to operate or understand a web page, but aren't covered by WCAG.

cheers,
_mallory

On Sat, Jul 11, 2020, at 2:53 PM, Steve Green wrote:
> The success criterion states "focusable components receive focus in an
> order that preserves meaning and operability". If there are only one or
> two components that receive focus when they should not, my view is that
> neither the meaning nor operability are significantly impaired, so I
> just recommend that they are made non-focusable.
>
> However, if a lot of components receive focus when they should not, my
> view is that this impairs the operability so I report a
> non-conformance. We see this an awful lot with e-learning systems, but
> virtually nowhere else.
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
>