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

Issue 777066 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 778489
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

[a11y Assessment - NTP] Search box not in tab order, not listed as an edit field

Project Member Reported by leberly@chromium.org, Oct 21 2017

Issue description

Google Chrome	64.0.3245.2 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 1607 Build 14393.1770
NVDA 2017.3
JAWS 2018.1710.36 private beta 

# Launch JAWS and Chrome
# Open New Tab Page, focus is in the omnibar
# Press tab, focus goes to voice search button and not the search box
# Press e, says "There are no edit boxes on this page." 

# Close JAWS, launch NVDA
# Open New Tab Page, focus is in the omnibar
# Press tab, focus goes to voice search button and not the search box
# Press e, no edit boxes on this page

Double checked in stable, same behavior 
Google Chrome	61.0.3163.100 (Official Build) (64-bit) (cohort: Stable)
 

Comment 1 by treib@chromium.org, Nov 3 2017

Cc: treib@chromium.org sfiera@chromium.org
Components: UI>Browser>NewTabPage
This is related to bug 778489, i.e. the "search box" on the NTP not being an actual search box.
However, I don't see why it couldn't be keyboard-focusable. I find it very confusing that keyboard focus just skips over it, independent of any screen reader. Maybe if it's focusable, maybe it'll also automatically be recognized as an "edit box" by the screen readers?
Labels: Needs-Feedback

Comment 3 by treib@chromium.org, Nov 29 2017

Labels: -Needs-Feedback
Mergedinto: 778489
Status: Duplicate (was: Available)
Labels: win-a11y

Sign in to add a comment