New issue
Advanced search Search tips

Issue 777051 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 791757
Owner: ----
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

[A11y Assessment - Tabstrip] Tabstrip titles not read by JAWS

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 

What steps will reproduce the problem?
(1) Enable JAWS, open Chrome
(2) use ctrl + t to create at least one new tab and one
(3) Use ctrl + 1, ctrl + 2, etc. to select tabs 

What is the expected result? Title of the tab is read

What happens instead? Title of the tab is NOT read, just the number is spoken

NVDA reads the title of each tab whereas JAWS does not. 
 
Labels: win-a11y
Possibly related, possible dupe of  bug 791757 
Status: Started (was: Available)
Labels: tabstrip
Labels: -Pri-2 Pri-1
Blockedon: 791757
Labels: a11y-testers
Is this the same as 791757?
Mergedinto: 791757
Status: Duplicate (was: Started)
Blockedon: -791757
Project Member

Comment 9 by bugdroid1@chromium.org, Jan 22 2018

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

commit 3700a46c532af05ed573ee417e2437c398352fcb
Author: Aaron Leventhal <aleventhal@chromium.org>
Date: Mon Jan 22 16:30:58 2018

Remove spurious focus event in UI during tab switching

Do not advance focus to the IconLabelBubbleView when switching tabs as
this causes screen readers to read the contents of that view, and in the
case of JAWS, causes it to also not read the new focus within the tab.

The spurious focus event was caused by the following line:
SetFocusBehavior(FocusBehavior::NEVER);
This resulted in a call to View::AdvanceFocusIfNecessary().

This CL cleans up the code path that occurs when we are emptying the
content area prior to attaching new content, including only the
necessary lines of code that would have run, need to run and
are not harmful to accessibility.

Bug:  791757 , 777051 
Change-Id: I81cfd39710e0bb0beaeb8a571ce3b899e9b71d7e
Reviewed-on: https://chromium-review.googlesource.com/868475
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#530878}
[modify] https://crrev.com/3700a46c532af05ed573ee417e2437c398352fcb/chrome/browser/ui/views/frame/browser_view.cc
[modify] https://crrev.com/3700a46c532af05ed573ee417e2437c398352fcb/chrome/browser/ui/views/frame/browser_view_focus_uitest.cc

Labels: -a11y-testers

Sign in to add a comment