New issue
Advanced search Search tips

Issue 709575 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 1
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

[MD Settings] Issues with main menu panel keyboard navigation

Project Member Reported by lpalmaro@chromium.org, Apr 7 2017

Issue description

OS: Mac
Version: 59.0.3063.0

I'm seeing some strange behavior in the side menu. When I navigate there with VoiceOver and press enter, the first time I navigated it worked smoothly. Then I pressed escape and it closed the side panel. That said, once I pressed escape, my focus went out of the web content area completely -- it went back to the change person menu in Chrome. 

However, when I went back to the side panel for the second and third time, I couldn't seem to get escape to work to get out of it, so I'm basically stuck there. 

It seems that when I click on the menu button with the mouse, I can press escape and it works to close it. But when I navigate with keyboard there, escape doesn't work. 


Noted by dbeam@: 
this behavior changed earlier this week and team is refining it further.

Right now: we're going to focus a wrapper around all the cards invisibly whenever the sidenav closes.

We're going to add a specific exception in the future: if you use keyboard to navigate to ≡ Settings menu and open the sidenav with Enter, we'll return focus to the ≡ when it closes.



 
FYI, related bugs:
 issue 708960  (fixed now, existed when this bug was originally reported)
 issue 709359  (candidate fix exists, will send for review shortly).

Comment 2 by dbeam@chromium.org, Apr 7 2017

Cc: -dpa...@chromium.org
Owner: dpa...@chromium.org
Status: Started (was: Available)
Components: UI>Settings
Labels: Needs-Feedback
Owner: lpalmaro@chromium.org
Status: Assigned (was: Started)
It is unclear to me whether there are any actionable items left in this bug. Re-assigning back to the reporter.

@lpamaro: Could you please try latest version and see if you are still seeing any issues?
Status: WontFix (was: Assigned)
This bug has not been updated in a year, so I am going to assume this is no longer relevant (also because there was a recent a11y review as part of MD Refresh).

Sign in to add a comment