WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [External Sender] How should work an accessible List

for

From: Mark Magennis
Date: Dec 20, 2018 10:29AM

If it's just a list of buttons (or links or mixed), it should not be a menu in the sense of the aria menu role which is for pop-up menus. It could be a menubar but I can't see much point in using menubars. They only add complication, require telling sighted user that they are menubars and how they work, and in most cases don't save much TABing in getting past them (particularly when placed immediately after a skip link).

Mark Magennis
Skillsoft | mobile: +353 87 60 60 162
Accessibility Specialist

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Isabel Holdsworth
Sent: 19 December 2018 10:22
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [External Sender] How should work an accessible List

Hi Yoandry,

What are the buttons being used for? Are you creating a toolbar or a
menu of some kind? If so then you might need to allow the arrow keys
to change the focus, but you'd also need to use ARIA to let
screenreaders and other assistive tech know what type of controls they
are and how to use them.

If you give us some more info, then I'm sure we can point you in the
right direction.

Cheers, Isabel

On 18/12/2018, glen walker < <EMAIL REMOVED> > wrote:
> Given the limited information, I agree with Brian.
>
> However, if the code is being used to create a toolbar of buttons (
> https://www.w3.org/TR/wai-aria-practices/#toolbar), then the arrow keys
> would be used to move between buttons. But in that case, your list would
> have a role of "toolbar" and your listitems would have
> role="presentation". Since that was not specified in the example, I'm
> guessing this is not a toolbar but wanted to toss that out there just in
> case.
>
> Glen
> > > > >