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

Issue 696233 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-08-18
OS: Mac
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

[A11y Assessment - Omnibox] Can't access the suggested URLs with VoiceOver

Project Member Reported by lpalmaro@chromium.org, Feb 26 2017

Issue description

Chrome Version:  56.0.2924.87
OS: Mac

What steps will reproduce the problem?
(1)Enable VoiceOver
(2) Press Ctrl L to place focus in omnibox
(3) Start typing a url
(4) Observe that suggestions appear visually, but you can't access them with the keyboard + VoiceOver

If I use VoiceOver to type in a URL, I can hear when an autocompletion is available and in the ombibox. However, I cannot actually use the arrow keys to navigate through the list of suggested URLs or results below the omnibox. This is not accessible to a blind user wanting to access the suggestions with a screen reader and keyboard. This does work *only* with keyboard, but not with VoiceOver enabled. 


 
Summary: [A11y Assessment - Omnibox] Can't access the suggested URLs with VoiceOver (was: [A11y Assessment] Can't access the suggested URLs with VoiceOver)
Labels: Pri-1 Type-Bug
Owner: ellyjo...@chromium.org
Status: Assigned (was: Untriaged)
Labels: NewComponent-Accessibility-Compatibility
Labels: NewComponent-Accessibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
NextAction: 2017-08-18
The NextAction date has arrived: 2017-08-18
I looked at what Cocoa's NSTextView does for completions. Their completions are not accessible with voiceover's navigation keys either, only with keyboard keys, and they are read like this:

with input text "def", press f5:
"initely". [down arrow]
"ense. defense, text (2 of 20)." [down arrow]
"iantly. defiantly, text (3 of 20)."

... and so on. Ours are announced *extremely* inconsistently by comparison - we read random fragments of the *previous* completion with no rhyme or reason. Safari's are read like this:

"Google - google.com [huge hex string] image completion selected"
"w, MagnitfyingGlassCompletionList image, column 2, row 5 empty cell completion selected ww.google.com text deleted"

these are pretty clunky too so I don't think we want to look to Safari for an example.

I'm going to work on making our announcements line up with how the system autocomplete works. I'm on the fence about supporting the VO navigation keys for them - neither Safari nor NSTextView support them so probably we shouldn't.

I think our announcements should be like this:
page result: "www.google.com - Google (suggestion k of n)"
search suggestion: "Search Google for foo (suggestion k of n)"

so I'll implement that.
Project Member

Comment 11 by bugdroid1@chromium.org, Nov 7 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2c324c1670d06a25eef4fc58896dfc9d614f7d55

commit 2c324c1670d06a25eef4fc58896dfc9d614f7d55
Author: Elly Fong-Jones <ellyjones@chromium.org>
Date: Tue Nov 07 12:18:21 2017

cocoa: announce omnibox autocompletes

This change:
1) Adds AutocompleteMatchType::ToAccessibilityLabel, which turns a match type
   and match text into a descriptive string for an accessibility label;
2) Adds descriptive string templates for most types of autocomplete match;
3) Has OmniboxViewMac announce when the temporary text changes, instead of just
   when the autocomplete text changes.

Bug:  696233 
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: If1df0e49e212810ad7d3bc49c0b5d262e107f7c7
Reviewed-on: https://chromium-review.googlesource.com/728900
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Rohit Rao (ping after 24h) <rohitrao@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#514452}
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/chrome/browser/ui/cocoa/omnibox/omnibox_view_mac.h
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/chrome/browser/ui/cocoa/omnibox/omnibox_view_mac.mm
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/chrome/browser/ui/views/omnibox/omnibox_view_views.cc
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/chrome/browser/ui/views/omnibox/omnibox_view_views.h
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/components/omnibox/browser/BUILD.gn
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/components/omnibox/browser/autocomplete_match_type.cc
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/components/omnibox/browser/autocomplete_match_type.h
[add] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/components/omnibox/browser/autocomplete_match_type_unittest.cc
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/components/omnibox/browser/omnibox_edit_model.cc
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/components/omnibox/browser/omnibox_edit_unittest.cc
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/components/omnibox/browser/omnibox_view.h
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/components/omnibox_strings.grdp
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/ios/chrome/browser/ui/omnibox/omnibox_view_ios.h
[modify] https://crrev.com/2c324c1670d06a25eef4fc58896dfc9d614f7d55/ios/chrome/browser/ui/omnibox/omnibox_view_ios.mm

Status: Fixed (was: Assigned)
There we go :)

Sign in to add a comment