Issue metadata
Sign in to add a comment
|
Chrome mis-announces the number of tabs in an ARIA tablist if the tabs aren't direct children of the tablist
Reported by
fst...@gmail.com,
Oct 31 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36 Steps to reproduce the problem: 1. Start Chrome 2. Go to https://codepen.io/fstorr/full/PJVYKp/ or see attached file 3. Start either JAWS 18 or NVDA 2017.3 4. Navigate through the tablists and listen to the different announcements What is the expected behavior? A screen reader should announce the number of tabs in a tablist, the index of the currently-focused tab, and whether it's selected. Chrome 62 and Chrome Canary 64 on macOS 10.3 do this. What went wrong? For tablists where the elements with role=tab are not direct children of the element with the role of tablist, screen readers announce "tab 1 of 1" for each tab instead of, for example, "tab 1 of 3" for a tablist with three tabs. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 62.0.3202.75 Channel: stable OS Version: Windows 10 Enterprise Flash Version: Each example in the reference CodePen works as expected, so this is a problem with Chrome on Windows.
,
Oct 31 2017
,
Nov 1 2017
,
Nov 3 2017
,
Nov 6 2017
Able to reproduce the issue on reported version 62.0.3202.75, latest stable 64.0.3260.0 and latest Canary 64.0.3260.0 using windows 10 but the behaviour is different from M-50 ie., The screen reader announce only the tab names from M-50(Fry tab, Blender tab and leela tab). As the reported issue is seen from M-60(60.0.3112.113), considering this issue as Non-Regression and marking it as Untriaged.
,
Dec 9 2017
Very well-researched and explained bug. I was able to easily confirm this issue in Chrome on Windows. I welcome more bugs of such high quality.
,
Dec 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Oct 31 2017