[A11y Assessment - Find in Page] Can't access the results number (e.g. (5 of 7) |
||||||||
Issue descriptionChrome Version: 57.0.2955.0 OS: Chrome What steps will reproduce the problem? (1) Enable ChromeVox (2) Press Ctrl F and type text into a page (text that can be found on the page) (3) Try to use ChromeVox to get to the results in the find box. What you need to do here is actually press Tab first to move focus to the previous, next, close button in the find UI. Notice that you can't access the result numbers with Chromevox, e.g. when it visually says "5 of 7", chromevox doesn't read that aloud. I know this isn't a top priority since ChromeVox has its own find in page functionality which is better for screen reader users. But this should still be accessible. What is the expected result?
,
Mar 28 2017
,
Apr 21 2017
,
Oct 24 2017
ChromeOS Version 64.0.3246.0 (Official Build) canary (64-bit) Firmware Version Google_Samus.6300.174.0 I am just reproing this to move from untriaged to available, I still see the same behavior. I followed these steps: (1) Enable ChromeVox, navigate to Wikipedia cat page (2) Press Ctrl F and type text into a page (text that can be found on the page) (3) Try to use ChromeVox to get to the results in the find box. What you need to do here is actually press Tab first to move focus to the previous, next, close button in the find UI. Text '1/839' is not read while tabbing through the Find UI. (That's a lot of cats!) I also tried using search + left and right and the text was not highlighted in that scenario either. Thanks, Laura
,
Oct 28 2017
This is happening on Windows as well with all AT tools. 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 ZoomText Private Beta - 11.7.11.410 When tabbing through the find in page dialog, there is no way for the number found to be read by NVDA, JAWS, nor ZoomText.
,
Oct 28 2017
Special note about JAWS: Pressing CTRL + F will bring up the special JAWS virtual find, not the find-in-page dialog in Chrome. To get that open for testing purposes, you need to bypass ctrl + f using the passthrough keys JAWS + 3 then ctrl + f.
,
Dec 14 2017
,
Dec 15 2017
Setting to p2 since this was found during our assessment
,
Dec 15 2017
,
Feb 4 2018
Note from tester who did the original assesment: I know that ChromeVox has its own find in page which is much better for a screen reader users. That said, the results in the find bug, e.g. "5 of 7" currently can't be accessed by ChromeVox and we should fix that, in case someone does want to use the standard find in page vs. Chromevox's find in page. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by dmazz...@chromium.org
, Mar 27 2017