WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [External Sender]what to do in scenario where you have two sets of tabs in each direction?

for

From: Isabel Holdsworth
Date: Jul 26, 2019 5:22AM

Warning! Stream of consciousness ramble imminent :-)

A menu with submenus probably would have been the way to go - shame
that's not possible.

Screen reader users tend to understand trees in the Windows
environment, for example in File Explorer. They may well be able to
generalise that knowledge to a tree on a website if it's properly
marked up.

But how about sighted keyboard users if the tablists remain as
distinct visual entities? How would they intuit how to operate the
keyboard on two distinct option groups that are behaving like a single
group?

In a tree, DownArrow moves through the branches and Right/LeftArrow
opens and closes a sub-branch. Blind users wouldn't realise that the
focus is moving across rather than down the horizontal tablist, but
sighted users would.

Is there such thing as a horizontal tree?

Taking something that visually looks like one type of control and
marking it up as something else can in certain scenarios be the only
way to provide an accessible UI. But it can have its down sides.

Could these not just be left as tablists, with each child tablist
being assigned a label that links it to its parent in the horizontal
tablist? Or perhaps each child tablist could be a set of navigation
links with a suitable label?

Cheers, Isabel

On 23/07/2019, Steve Green < <EMAIL REMOVED> > wrote:
> Has anyone done any user testing on a tree? The last time I did was so long
> ago that ARIA hadn't even been thought of, so the results were
> unsurprisingly poor. But I am far from convinced that average screen reader
> users (let alone those below average) would be able to understand a tree and
> use it effectively unless it was on a website they visit frequently.
>
> Steve
>
>
>