WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: List of buttons triggers MENU role

for

From: Steve Green
Date: Oct 24, 2018 4:48AM

I have built a test page with two groups of buttons as you have described, and JAWS 2018 does not announce either of them as a menu. It seems that there must be something else in your code that is contributing to the behaviour you are seeing. Are you able to share a link?

Steve Green
Managing Director
Test Partners Ltd


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Isabel Holdsworth
Sent: 24 October 2018 11:13
To: <EMAIL REMOVED>
Subject: [WebAIM] List of buttons triggers MENU role

Hi all,

I'm creating a drag-and-drop scenario, in which items across the top of the screen can be dragged to one of two or three areas underneath.

I wanted to mark up the draggable items as buttons so screenreader users know they need to be pressed for something to happen. But when I encapsulate the buttons in a <ul> or <div role="group"> either JAWS or the browser (not sure which) seems to assign a MENU role to the whole group, which is something I don't want.

I can mark up the items as links, in which case the component works beautifully. But that would be semantically incorrect and I'd like to avoid this if possible.

Does anyone know how to disable this annoying automatic role assignment?

Thanks as always, Isabel