New issue
Advanced search Search tips

Issue 787516 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

A11Y: Tables are not presented to screen reader users

Project Member Reported by dsexton@chromium.org, Nov 21 2017

Issue description

OS Name: Microsoft Windows 10 Enterprise Version: 10.0.14393 Build 14393
Browsers:
Chrome: 64.0.3273.3 (Official Build) canary (64-bit) (cohort: Clang-64)
Chrome: 62.0.3202.94 (Official Build) (64-bit) (cohort: Stable)
Firefox: 52.4.1 (64-bit)
Screen readers:
NVDA: Version 2017.3
JAWS Professional: Version 2018 (build 1710.42 ILM) 

Chrome Canary, Chrome stable with JAWS and NVDA present the same issue.

Steps to repro:

# With NVDA running: In Chrome Canary visit https://www.alaskaair.com
# Fill in details for a round trip flight from SFO to MSP 12/25/2017 returning 01/08/2018, 1 adult and click 'find flights'
# Press 't' to locate the first table on the search results page

Expected: NVDA should jump to the table containing the search results

Actual: NVDA says " No tables on page"

# With NVDA running: In Firefox visit https://www.alaskaair.com
# Fill in details for a round trip flight from SFO to MSP 12/25/2017 returning 01/08/2018, 1 adult and click 'find flights'
# Press 't' to locate the first table on the search results page

Expected: Works as expected. NVDA jumps to the search results table.

 
We have some heuristics that try to distinguish between a data table and a layout table. We decided this is a layout table, which is wrong - but the content of the table still functions, we just don't annotate it as a table.

The Chrome/Safari heuristic considers it a non-data table if the thead/tbody/tfoot has a role.

Firefox does not... Here is the Firefox code. 
https://dxr.mozilla.org/mozilla-central/source/accessible/html/HTMLTableAccessible.cpp#914 

Regarding this particular rule (role on thead/tbody/tfoot), I'm not sure which heuristic is better. It's possibly easier for us to just change it.

Should we harmonize our heuristics with Firefox? Do we even want any differences, even what we consider improvements?
Labels: win-a11y
Labels: tables
Labels: -Pri-1 Pri-2
Project Member

Comment 6 by sheriffbot@chromium.org, Dec 17

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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