a11y: voice search button on NTP not recognized as a button by screen readers |
|||||||||||||
Issue description69.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.
,
Aug 3
,
Aug 7
,
Aug 8
,
Aug 10
,
Aug 23
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"
,
Sep 10
,
Sep 18
,
Sep 25
,
Sep 26
,
Nov 7
,
Nov 7
,
Jan 8
,
Jan 10
Remote NTP only |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by leberly@chromium.org
, Aug 3