New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 731077 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

Mnemonics not exposed to accessibility in Chrome menus

Project Member Reported by ja...@nvaccess.org, Jun 8 2017

Issue description

Chrome Version: 61.0.3122.0 (Official Build) canary(64-bit)
OS: Windows 10 Version 1703 (OS Build 16199.1000) 64-bit

What steps will reproduce the problem?

(1) Start Chrome and the NVDA screen reader.
(2) Press alt+f to open the Chrome menu.
(3) Press down arrow until you reach "History".

What is the expected result?
NVDA should say "History  sub menu  h"

What happens instead?
NVDA says only "History  sub menu"

The Mnemonic (the underlined letter which can be used to activate/move to the menu item while the menu is visible) is not exposed to accessibility. In Windows, it should be exposed via IAccessible::accKeyboardShortcut. At present, this returns null.

Impact: This means these Mnemonics are not discoverable to screen reader users, which hurts efficiency in learning and usage.
 
Components: UI>Browser>Core
Looking at that menu, no item item that is expansible (with the ">" arrow symbol) shows a mnemonic.

So this seems to be a result of some UI constraints.

Comment 2 by ja...@nvaccess.org, Jun 13 2017

It's worth noting that non-expandable items don't expose mnemonics to accessibility either. A good example is Settings, which can be activated by pressing "s". This is also true for New tab (t), New window (n), New incognito window (i), etc. However, I didn't mention these originally because these also have accelerators (e.g. control+t) and I didn't want to confuse things.
Labels: triage-nektar
Cc: nek...@chromium.org
Owner: ----
Status: Available (was: Untriaged)
Labels: -triage-nektar

Comment 6 by nek...@chromium.org, Aug 23 2017

Cc: -nek...@chromium.org
Owner: nek...@chromium.org
Status: Started (was: Available)
Patch uploaded.

Project Member

Comment 7 by bugdroid1@chromium.org, Aug 23 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0b7e862dfaeab93fd993efe40ec173ce37f41953

commit 0b7e862dfaeab93fd993efe40ec173ce37f41953
Author: Nektarios Paisios <nektar@chromium.org>
Date: Wed Aug 23 20:11:53 2017

Exposed menu accelerator keys to accessibility.

This is a top request from one of our accessibility partners.
R=sky@chromium.org, dmazzoni@chromium.org
TESTED=Manually with Chrome on Windows and the NVDA / Jaws screen readers by browsing the main menu

Bug:  731077 
Change-Id: Id1c0fb24827ce0ed012ce0844d63ae6ae31e9ac3
Reviewed-on: https://chromium-review.googlesource.com/629102
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#496782}
[modify] https://crrev.com/0b7e862dfaeab93fd993efe40ec173ce37f41953/ui/views/controls/menu/menu_item_view.cc

Comment 8 by nek...@chromium.org, Aug 23 2017

Status: Fixed (was: Started)

Sign in to add a comment