Issue metadata
Sign in to add a comment
|
Accessibility is broken for google.com in Canary
Reported by
laura.ca...@ft.com,
Dec 8 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2945.3 Safari/537.36 Example URL: www.google.com Steps to reproduce the problem: 1. google something 2. hit tab 3. hit down-arrow What is the expected behavior? a blue chevron should appear next to the first search result. Hitting down-arrow again should move focus to the next search result What went wrong? pressing down arrow does nothing. Attached a video of the behavior in chrome 54 where it works properly, followed by Canary where it does not Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? Yes 54.0.2840.98 (64-bit) Does this work in other browsers? Yes Chrome version: 57.0.2945.3 Channel: canary OS Version: OS X 10.12.0 Flash Version: Shockwave Flash 24.0 r0
,
Dec 9 2016
,
Dec 9 2016
,
Dec 29 2016
This bug is now reproducible in the stable release of Chrome too, not just Canary anymore, as of version 55. So this vital accessibility feature of google search might as well not exist when using Chrome. It works in Safari and Firefox and pretty much everywhere else.
,
Jan 1 2017
Restoring the browser settings fixed it. Prior to doing that, with all extensions and experiments off it was still reproducible, both in canary and stable Settings: Locale: en-GB User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2966.0 Safari/537.36 Google Chrome: 57.0.2966.0canary Startup type: Open the New Tab page Homepage is the New Tab page: Yes Show Home button: No Default search engine: www.google.co.uk Extensions: Web Store, Google Drive, YouTube, Bookmark Manager, Feedback, CryptoTokenExtension, Cloud Print, Chrome PDF Viewer, Google Network Speech, Google Hangouts, Chrome Web Store Payments, Gmail, Chrome Media Router (Canary)
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Sep 7
,
Sep 7
From what I understand, after the bug reporter reset their browser settings, the issue is not reproducible any more. Closing. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by erikc...@chromium.org
, Dec 9 2016Components: UI>Accessibility
Labels: M-55 Hotlist-Accessibility