Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JAWS doesn't announce collapsed state of the menu button #358

Open
Leuvarden opened this issue Jan 20, 2020 · 4 comments
Open

JAWS doesn't announce collapsed state of the menu button #358

Leuvarden opened this issue Jan 20, 2020 · 4 comments
Assignees

Comments

@Leuvarden
Copy link

Summary

JAWS doesn't announce expanded/collapsed form buttons with aria-expanded and aria-haspopup=true

Example:

  1. With JAWS on, go to https://www.w3.org/TR/wai-aria-practices-1.1/examples/menubar/menubar-2/menubar-2.html
  2. Use Left and Right arrows to navigate through the menu buttons in the menubar. JAWS announces menu buttons as "sub menu" and does not announces its collapsed/expanded state

Expected result

According to JAWS Aria support, aria-expanded is read by JAWS (https://freedomscientific.github.io/VFO-standards-support/aria.html) Although when aria-expanded is added to the element with role=button and aria-haspopup=true, expanded/collapsed state is not announced.

JAWS version and build number

JAWS 18.0.5038 and JAWS 2018.1811.30

Operating System and version

Windows 10 Enterprise

Browser and version:

Chrome 79.0, Firefox 72.0

@JAWS-test
Copy link

JAWS-test commented Jan 21, 2020

The problem also occurs with JAWS 2019 and JAWS 2020 in Chrome and Firefox. Here, the status "expanded" and "collapsed" is only output when opening and closing submenus, even if they are automatically closed when navigating through the main menu items. This leads for example to misleading output when navigating from "Text Align" to "Size": "sub menu collapsed Size sub menu 4 of 4" (The "sub menu collapsed" refers to the closing of the submenu of "Text Align").

The problem occurs not only with role=menuitem. aria-expanded is also not output for a <button> with aria-haspopup, because these buttons are interpreted as a menu (see w3c/core-aam#51 and #211).

@frex65
Copy link

frex65 commented Apr 14, 2020

The test case example doesn't demonstrate the issue that's being described, since each of the elements in its top menubar is a <a> element with a menuitem role, rather than a button as specified in the issue. The menuitem role is not one of the seven roles to which the aria-expanded state can be applied. Please can you provide an example that illustrates the problem?

@JAWS-test
Copy link

The menuitem role is not one of the seven roles to which the aria-expanded state can be applied.

aria-expanded is allowed for menuitem: https://www.w3.org/TR/wai-aria-1.2/#menuitem

@stevefaulkner
Copy link
Contributor

@JAWS-test you are correct that ARIA 1.2 allows aria-expanded on menuitem, but it is not yet a W3C recommendation, ARIA 1.1 is a W3C recommendation, in which the menuitem role does not allow aria-expanded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants