WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Focus reset

for

From: glen walker
Date: Apr 18, 2023 9:50AM

The authoring practice patterns are best practices but you don't
necessarily have to follow them exactly. I rarely say that because I think
if we all design/code using similar patterns, that makes it easier for the
user to recognize those patterns on different websites and they'll
inherently know how to interact with them. In your case, you could have
the buttons be a vertical tab list, I see those occasionally, but you don't
have to style them to look like tabs on a folder. They could just be a
stack of vertical buttons.

And you could implement both arrow key navigation and tab key navigation.
Yes, the default tab design pattern uses arrow keys to navigate between the
buttons so that the tab container is one tab stop, but if your user testing
shows people are more likely to TAB to the different buttons, there's
nothing that says you can't do both. That would veer away from the keyboard
interaction pattern a bit but the end goal is to make it easy for the user
to understand.

On Mon, Apr 17, 2023 at 10:34 PM Sumit Patel < <EMAIL REMOVED> >
wrote:

> Thanks all for your responses. These buttons do not look like tabs.
> Initially even I thought the same giving "tab" role and associated
> properties . so, screen reader user will understand contents would
> have updated below after selection. They will have understanding about
> the keyboard navigation when they hear "tab" role that they need to
> use arrow keys if they want to move to other tabs. but, as mark said,
> sighted keyboard-only user won't have any idea about this as this does
> not look like a tab. They will be thinking that the other buttons are
> not keybord focusable.
>
>