Issue metadata
Sign in to add a comment
|
[A11y Assessment - NTP] Issues with the notifications UI and VoiceOver |
||||||||||||||||||||||||||
Issue descriptionChrome Version: 56.0.2924.87 OS: Mac What steps will reproduce the problem? (1) Enable VoiceOver (2) Open a NTP (3) Use Option Ctrl Right to navigate through the NTP, and once you reach the notifications button, press enter or space to open it. Then try to navigate through that UI with VoiceOver. When I use VoiceOver to open the notifications center, I can't access the close buttons for the notifications using the screen reader. I can get to them using just tab, but I get no spoken feedback about what the button is, or the fact that it's a button. We need to ensure these buttons are accessible to VoiceOver (and all screen readers). Also, when I use VoiceOver to access the notifications button, then press space to expand the UI, I can't easily enter it with keyboard and VoiceOver. The focus doesn't behave right. Once it's expanded, if I press Option Ctrl Right to move linearly, I should be brought into that UI. Instead, I move to the next icon on the top of the NTP. I eventually reach the notifications UI if I overshoot it and then navigate backwards linearly, which is odd. At that time, it just says "frame 0" as the title of the UI, when it should really say "notifications popup" or something like that.
,
Feb 26 2017
,
Feb 27 2017
,
Feb 28 2017
Marc, are you the right person to take a look at this?
,
Feb 28 2017
This is about the small "bell" button in the top right, next to the account picture? If so, that is part of the One Google Bar. Is this really Mac-only, or just not tested anywhere else yet?
,
Feb 28 2017
#5: the audit was done on Mac, so it just hasn't been tested anywhere else.
,
Mar 6 2017
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 1 2017
mac triage: Any updates on this bug?
,
Aug 23 2017
Marc, would M63 be doable for this one? If not, maybe we should reduce the priority on this one.
,
Aug 23 2017
We won't fix this on the remote NTP, so it depends on how the local NTP plans work out. This is actually part of the One Google Bar rather than the NTP itself. The local NTP uses a newer version of the bar than the remote NTP, so I'm hoping this will just go away with the local NTP launch. lpalmaro, could you enable the following two flags in Chrome 62 or later (i.e. Dev channel or Canary), and test this again? chrome://flags/#use-google-local-ntp chrome://flags/#one-google-bar-on-local-ntp
,
Sep 13 2017
Assigning to lpalmaro for checking on the local ntp.
,
Oct 25 2017
Zine triage: reducing priority to reflect reality, as this has slipped multiple milestones.
,
Oct 28 2017
The behavior is different on the windows side depending on the software used. Please consider merging these two issues or keeping them separate if desired. https://bugs.chromium.org/p/chromium/issues/detail?id=779284
,
Nov 29 2017
,
Jan 17 2018
|
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by lpalmaro@chromium.org
, Feb 26 2017