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

Issue 887566 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

ChromeVox not alerting the user about how many matches available from auto-suggestions list

Project Member Reported by anakerakanti@chromium.org, Sep 20

Issue description

Chrome Version       : 68.0.3440.118 (Official Build) (64-bit) 
URLs (if applicable) : https://careers.google.com/
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
    Safari: Version 11.1.2 (13605.3.8) :OK
    Firefox: Version 62.0 : OK

STEPS:

1.Navigate to https://careers.google.com/

2.Click on ‘Jobs’ link from top navigation bar.

3.Click on any of the job post title and navigate to ‘Apply’ & click on it then application form will populate.

4.Navigate to School name / Employer name combo box field and start typing text then auto suggestion list will populate underneath that respective field and observe whether ChromeVox gives any hint/clue about how many matches available from auto suggestion list.

5.Try to navigate through list items from auto suggestion list using the arrow keys and observe whether ChromeVox is reading the list item names while navigating through the auto suggestion list.

ACTUAL RESULT(S):
ChromeVox is not giving any verbal feedback about how many matches are available from auto suggestion list. VoiceOver and JAWS is giving this feedback as ” <number> matches available”. Eg: 5 matches available.

EXPECTED RESULT(S):
ChromeVox should give the verbal feedback about how many matches are available from auto suggestion list like JAWS and VoiceOver.
 
ChromeVox not alerting the user about how many matches available.mov
25.4 MB Download
Status: WontFix (was: Unconfirmed)
Hi,
Thanks for submitting this. I see that this issue is fixed in a newer version of Chrome. I’m resolving this bug now since the fix will be coming to you soon. If you have further questions or concerns, please feel free to reopen this bug or open a new one and I’ll be happy to look into it further.
Thanks,
Leo

Sign in to add a comment