Opened 11 years ago
Last modified 11 years ago
#12292 confirmed Bug
Accessibility: better support for tables
| Reported by: | Marek Lewandowski | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | Accessibility | Version: | 3.0 |
| Keywords: | Cc: |
Description (last modified by )
We need to bring a better support for the tables.
I've tested JAWS and Narrator and none of them is doing a good job with our tables.
Screen reader notes:
- JAWS - reads each char inside the table as line ending mark, therefore tables content is not available which makes this useless.
- Narrator - it reads the content correctly, but (at least in default configuration) does not notify that user is in the table.
Possible solution:
I belive we should give a try to role=grid for the table.
Change History (3)
comment:1 Changed 11 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 11 years ago by
comment:3 Changed 11 years ago by
| Status: | new → confirmed |
|---|---|
| Version: | → 3.0 |
Note: See
TracTickets for help on using
tickets.
I've just checked NVDA and it's doing an OK job with tables.