New issue
Advanced search Search tips

Issue 668322 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 668313
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug
Team-Accessibility

Blocking:
issue 671375



Sign in to add a comment

MD Settings: subpages should reset tab position when opening and closing

Project Member Reported by michae...@chromium.org, Nov 24 2016

Issue description

Version: 57.0.2930.0

Main page should restore the tab position after closing a subpage:

1. chrome://md-settings
2. Tab to the "Customize fonts" arrow and hit Enter
3. Go back by tapping the in-page back arrow (or using keyboard focus)
4. Press Tab

Expected: The row below "Customize fonts" (Page zoom) is focused
Actual: The next section is focused (Search engine dropdown)

Note that this works as expected if you use the browsing back button (or Alt+Left), assuming you don't tab around inside of the subpage.


Also, it's minor, but perhaps subpages should reset the tab position to the beginning when re-opening them:

1. chrome://md-settings
2. Tab to the "Customize fonts" arrow and hit Enter
3. Tab to the "Serif font" dropdown menu
4. Alt+Left to go back
5. Alt+Right to go forward again
6. Press Tab

Expected: Tab focuses the back arrow first
Actual: Tab focuses the "next" item ("Sans-serif font" dropdown menu)

As a user, I shouldn't have to understand how our DOM works in order to know where tab focus is going to be. The fact that we're re-using the subpage element shouldn't matter.

It's a slightly bigger deal on pages with lists, like the "Edit dictionary" subpage, where I might have focused a particular list item's "delete" button. I don't expect that list item's "delete" button to still be focused when I return.
 

Comment 1 by dbeam@chromium.org, Dec 12 2016

Blocking: 671375
Cc: -hcarmona@chromium.org
Components: UI>Accessibility
Labels: -Pri-3 Pri-2
Owner: hcarmona@chromium.org
Status: Assigned (was: Untriaged)
i'm not sure I agree with the original bug's intent, but I'm assigning this bug to hcarmona@ to play with this and ensure it has a sane behavior (and justify and implement his findings)
Labels: Hotlist-MD-Settings-PageA11y
Labels: NewComponent-Accessibility-Browser

Comment 4 by dbeam@chromium.org, Mar 17 2017

Mergedinto: 668313
Status: Duplicate (was: Assigned)

Sign in to add a comment