New issue
Advanced search Search tips

Issue 779306 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

[A11y Assessment - Extensions] Sub menu items not invoked by space bar

Project Member Reported by leberly@chromium.org, Oct 28 2017

Issue description

Google Chrome 64.0.3251.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 1607 Build 14393.1770
NVDA 2017.3
JAWS 2018.1710.42 private preview release
ZoomText Private Beta -  11.7.11.410

# Open AT software and Chrome that has an existing extension installed
# Put focus in Omnibar using F6 
# Navigate to extension, press space to drop down details
# Use arrow keys to navigate down the list of details
Expected: space will invoke a list item
Actual: space does nothing, Enter required for JAWS, NVDA, and ZoomText  
 
Also applies to the bookmark context menu. To get there, navigate to any bookmark on the bookmark bar then press shift + F10 to open the context menu. Pressing space does nothing. 
Labels: win-a11y
Labels: -Pri-3 Pri-2

Comment 4 by nek...@chromium.org, Dec 15 2017

Labels: toolbar
Owner: leberly@chromium.org
Status: Assigned (was: Available)
For the bookmark context menu, this is working as intended. Native Windows menu items don't normally activate on spacebar - I tested Firefox, Notepad++, and even the NVDA status tray menu - none of them do. Menu items that do seem to be the exception.

As for extensions, each extension has its own popup UI, they don't share anything in common. We can't fix bugs with accessibility of specific extensions, only issues that apply to all extension pop-ups. If you want to file a bug about an extension pop-up, specify the specific extension. Note that individual extensions may create inaccessible pop-ups and there's nothing we can do about that.

To @leberly to close or update the bug.


Status: WontFix (was: Assigned)
Fair enough, closing as WontFix.

Sign in to add a comment