You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The content under the heading "Tricky screen reader navigation" makes assertions about how screen readers read this table, but those assertions are based on an invalid pattern.
I never understood what the headers attribute is useful for in simple tables: the association between th and td is always given automatically, and I never experienced any issues with screen readers. As soon as tables get more complicated and therefore a headers attribute seems necessary, I usually discourage to create tables with such messy data anyway.
Looking at this page:
https://www.accessibility-developer-guide.com/examples/tables/spanning-rows-cols/
It shows
<th>
s that span but does not include the requiredid
andheaders
attribute in the associated<th>
s or<td>
s.Eg:
The content under the heading "Tricky screen reader navigation" makes assertions about how screen readers read this table, but those assertions are based on an invalid pattern.
Correct code might look like this:
I have an example here:
https://adrianroselli.com/2017/11/hey-its-still-ok-to-use-tables.html#WCAGSpanning
Which is based on this WCAG example:
https://www.w3.org/TR/WCAG20-TECHS/H43.html
The text was updated successfully, but these errors were encountered: