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

Issue 779286 link

Starred by 1 user
Status: ExternalDependency
Owner:
█ ramyan@chromium.org
OOO Jan 14 - 25
Cc:
█ sfiera@chromium.org
█ adriennetran@google.com
treib@chromium.org
█ ramyan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
ntp
Team-Accessibility

Blocking:
issue 920004



Sign in to add a comment

[A11y Assessment - NTP One Google bar] Google apps region not treated as submenu

Project Member Reported by leberly@chromium.org, Oct 28 2017 
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

# Launch AT software and Chrome, open NTP
# Navigate to the Google bar > Apps icon
# Press space to collapse the submenu
# Use the up/down directional buttons or the tab button to navigate through the list
# At the end, you are popped out of the list to the "More" button at the bottom of the submenu
# Press the down arrow/tab one more time 
Expected: focus order loops back to the top of the dialog
Actual: focus moves onto the notification button on the Google bar on the base page, not respecting the convention that the focus should stay within the sub menu while it is collapsed

Comment 1 by treib@chromium.org, Nov 3 2017

Cc: treib@chromium.org sfiera@chromium.org
Components: UI>Browser>NewTabPage
On the local NTP, this behaves a bit differently: The arrow keys don't work for navigating within the apps menu (only tab works), and the "more" button doesn't seem to be keyboard-focusable at all. When tabbing beyond the apps menu, then the focus moves to the Chrome omnibox, and then back into the apps menu. I believe that part is working as intended now.

So, I think the only remaining issue is that "more" isn't focusable. That's an issue with the OneGoogleBar, which isn't owned by Chrome. I'll file an internal bug.

Comment 2 by treib@chromium.org, Nov 3 2017 

Hm, actually, I'm seeing the same behavior on the remote (i.e. default) NTP: The arrow keys don't work for navigation (only reordering), tabbing does loop as it should, and the "more" button isn't tabbable.

Do the screen readers mess with the tab order or something? If so, I'm not sure there's anything we can do about it.

Comment 3 by treib@chromium.org, Nov 3 2017 

b/68840064

Comment 4 by mastiz@chromium.org, Nov 7 2017

Labels: zine-triaged

Comment 5 by treib@chromium.org, Nov 29 2017

Status: ExternalDependency (was: Available)

Comment 6 by leberly@chromium.org, Dec 14 2017

Labels: win-a11y

Comment 7 by lpalmaro@chromium.org, Dec 15 2017

Labels: ntp

Comment 8 by dmazz...@chromium.org, Dec 15 2017

Labels: -Pri-2 Pri-3

Comment 9 by leberly@chromium.org, Dec 15 2017

Labels: Pri-2
Setting to p2 since this was found during our assessment

Comment 10 by yyushkina@chromium.org, Jul 10

Cc: adriennetran@google.com

Comment 11 by kmilka@chromium.org, Aug 8

Labels: NTPOGB

Comment 12 by ramyan@chromium.org, Sep 12

Owner: ramyan@chromium.org
Status: Assigned (was: ExternalDependency)

Comment 13 by ramyan@chromium.org, Sep 12

Status: ExternalDependency (was: Assigned)

Comment 14 by ramyan@chromium.org, Nov 14

Labels: KR-GAR4 O-Robust-NTP

Comment 15 by kristip...@chromium.org, Jan 8

Blocking: 920004

Comment 16 Deleted

Comment 17 Deleted

►

Sign in to add a comment