WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Mallory
Date: Jul 10, 2020 5:29AM

Hm, if the focusable element is not in an incorrect order or doesn't have a tabindex larger than 0, it shouldn't fail Focus Order. The focus is still in visual and content order, no?

If it has no JavaScript to Do Something, it likely doesn't count as a "user interface component" and therefore is not covered by 4.1.2. 1.3.1 is also a stretch, as there's nothing in there that suggests the focusablility of something is expected to convey information (although in practice, people expect if they can Tab to it, it should Do Something. In that sense, I agree with Brian).

If it's there to allow keyboarders to scroll the content, it's a good idea to give the container a role and a name. I've heard more than one screen reader user complaining either that there's "focus mistakes" or "they made buttons I can't click", not realising these are for sighted keyboarders and don't do anything on click. Both times this was with a chat window, which had no focusables inside for keyboarders to scroll, and ideally should have a role (like "log") and a name ("Chat Window").

cheers,
_mallory

On Fri, Jul 10, 2020, at 2:18 AM, Patrick H. Lauke wrote:
> On 09/07/2020 13:26, Brian Lovely via WebAIM-Forum wrote:
> > Part of the semantics of an element being in the tab order is that that
> > element is actionable, so adding a non-actionable element to the tab order
> > with tabindex="0" is a semantic failure.
>
> Seems a bit of a stretch. It's a failure of focus order/behaviour, not
> of semantics, I'd say... (how it behaves vs what it conveys)
>
> P
> --
> Patrick H. Lauke
>
> https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > >