Is it advisable to combine and use Scope and Headers/IDs attributes in the same table to improve accessibility for screen readers?
MelodyWebmaster opened this issue · 5 comments
I'm wondering if using scope and headers/id attributes in the same table might conflict in certain situations?
I know some screen readers are not working well with Headers/IDs attributes even it is markup perfectly. There is so much divergence online, and your website example combined both.
https://www.w3.org/WAI/tutorials/tables/multi-level/
The example 2: Table with three headers related to each data cell
Full code for Example “Table with three headers related to each data cell”
| Studio | Apt | Chalet | Villa | |
|---|---|---|---|---|
| Paris | ||||
| 1 bedroom | 11 | 20 | 25 | 23 |
| 2 bedroom | - | 43 | 52 | 32 |
| 3 bedroom | - | 13 | 15 | 40 |
| Rome | ||||
| 1 bedroom | 13 | 21 | 22 | 3 |
| 2 bedroom | - | 23 | 43 | 30 |
| 3 bedroom | - | 16 | 32 | 40 |
You're not likely to get much reply from this GitHub repo. Instead, I invite you to try the WAI Interest Discussion List where issues of digital accessibility are discussed. From there you can get multiple perspectives.
You can join the mailing list and post questions by following the instructions for the Discussion List under:
https://www.w3.org/WAI/about/groups/waiig/#mailinglist
Closing issue as another avenue has been suggested