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

Issue 870729 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Chrome
Pri: 2
Type: Bug
Team-Accessibility

Blocking:
issue 920004



Sign in to add a comment

a11y: voice search button on NTP not recognized as a button by screen readers

Project Member Reported by leberly@chromium.org, Aug 3

Issue description

69.0.3497.23 (Official Build) dev (64-bit) (cohort: Dev)	
JAWS 2018.1807.29 ILM	
NVDA 2018.2.1

Note that the button is labeled properly so screen readers will read the name of the button, this is for other features of this button.

Steps to reproduce:
# Turn on either screen reader
# Open the new tab page
# Press "b" to navigate by button
Expected: voice search button recognized as a button
Actual: not included in button choices

Here is where behavior differs by screen reader:
# Open JAWS and the NTP
# Use tab to navigate to voice search button
# Press enter or space to invoke it
Expected: voice search starts
Actual: nothing happens

This doesn't reproduce with NVDA, the button can be invoked with it. 

 
Components: UI>Browser>NewTabPage
Description: Show this description
Labels: zine-triaged
Cc: adriennetran@google.com yyushkina@chromium.org
Labels: a11y-NTP
Labels: OS-Chrome
Google Chrome	70.0.3524.2 (Official Build) dev (64-bit)
Firmware Version Google_Lulu.6301.136.57

ChromeVox says "Search by Voice Form" instead of "Search by Voice Button"
Cc: -adriennetran@google.com ramyan@chromium.org
Labels: pm-markchang
Labels: Group-New_Tab_Page
Labels: NTPVoice
Labels: KR-GAR4 O-Robust-NTP
Labels: Target-72
Blocking: 920004
Remote NTP only

Sign in to add a comment