- 🇨🇦Canada mgifford Ottawa, Ontario
I think that this is tied to https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html
Drupal core uses lots of tables to list entities. These tables have their column headers correctly identified, but not at the row level.
For assistive technology, such as screen readers or speech control, it often helps to have a row-level header specified too. For example, screen readers provides tools for users to get more information about their position in the table, on demand. They can announce the cell coordinates, or the column and row headers. The more columns a table has, the more useful row-level headers are.
In the absence of explicit row-level table headers, some screen readers treat the first <td>
in the row as a header. Unfortunately this is often a checkbox or a drag handle, which isn't the best column to use. We can make the experience more robust for assistive tech if we specify which column should be treated as the row-level header. In most cases, the entity label will be best.
For entity listing tables, treat the entity label as a row level table header (i.e. <th scope="row">
). The pattern is described at Table with an offset column of header cells.
None.
None.
Active
11.0 🔥
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I think that this is tied to https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html