Closed Bug 913314 Opened 11 years ago Closed 9 years ago

Tables with CSS display property set to block do not get represented as tables to assistive technology

Categories

(Core :: Disability Access APIs, defect)

22 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1005271

People

(Reporter: dylan, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36

Steps to reproduce:

When creating responsive tables, it is useful to be able to set the display property for a table to "block" so that they can be flowed nicely


Actual results:

When you do this, the table is no longer represented as a table to the assistive technology (AT) and so tables header association and table navigation does not work in the AT. Also the headers in the thead element are not picked up reliably so you actually have to set the thead element to display:none so that it does not get in the way and then replicate the header information in each cell.


Expected results:

All table elements should be represented as table elements regardless of what their display property is set to. For more information see http://unobfuscated.blogspot.com/2013/07/responsive-accessible-data-tables.html and http://www.accessibleculture.org/articles/2011/08/responsive-data-tables-and-screen-reader-accessibility/
Component: Untriaged → Layout: Tables
Product: Firefox → Core
Drew, for future reference this is about how a11y exposes tables, not their CSS layout....
Component: Layout: Tables → Disability Access APIs
*bows and scrapes*
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.