Issue metadata
Sign in to add a comment
|
[A11y Assessment - Launcher] Issues using the search field with ChromeVox |
||||||||||||||||||||||
Issue descriptionOS: Chrome Tested on Canary (61) but experienced in previous versions Issues occurring in the launcher when you type a search term or url into the text entry field with ChromeVox enabled. I type letters but then I don't hear anything about how many results have appeared that match the search I've entered. Instead, I just hear the first option that appears verbalized. E.g. if I type in "chr", two things appear -- chrome remote desktop and chrome. But I just hear "chrome remote desktop" instead of "two results found" or something like that. From there, I can't use ChromeVox navigation to get to the results (Search+R). I can only use the arrow keys alone to get there, which again, is really not intuitive for screen reader users since they are not used to doing this to navigate Chrome OS and would therefore not know to do this.
,
Sep 21
On 71, still able to reproduce most of this (except for using Search + Right to navigate through the launcher, as that has now been fixed). As I type letters into the search box, I don't hear how many results are displayed. Since I don't hear anything about results, my inclination would be to press Enter to then get to the search results, but instead, enter just takes me to one of my first apps that matches the result and opens that app. This is a confusing experience. We need to announce how many results are showing, and then append/say "press Search + Right to explore" or something like that so the user knows what to do here. @Alex can you help to find an owner please?
,
Sep 21
Replying inline and adding UX because I think solving this will require UX input. "As I type letters into the search box, I don't hear how many results are displayed." -- wont this be disruptive? IIRC chromevox announces each key press. Won't this sort of spam users when they are typing into the searchbox? We load results as the query is typed. "Since I don't hear anything about results, my inclination would be to press Enter to then get to the search results, but instead, enter just takes me to one of my first apps that matches the result and opens that app. This is a confusing experience." -- The first result is highlighted, so are you saying that the highlight is not clear enough, so it's not obvious that hitting enter launches that app? Or do we need to explicitly make sure that users know that search results are being displayed somehow? UX might have ideas. "We need to announce how many results are showing, and then append/say "press Search + Right to explore" or something like that so the user knows what to do here." -- I thought the paradigm in general was that ChromeVox users know to hit search+right to explore. Is that necessary? Can we just say "results loaded" when some results load? Or should this be apart of the alert you mentioned above?
,
Oct 9
Can we prioritize this for M-72?
,
Dec 3
yoink
,
Dec 5
This is still a P-1, but because this is more of an umbrella/root bug with a lot of work implied, moving it to M-73. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Jul 23Status: Untriaged (was: Available)