In Headers attribute specified on a cell refers to cells in the same table element, Inapplicable Example 6 is ambiguous because role="region" requires an accessible name. Without one, browsers treat it as a generic element.
In Inapplicable Example 6
<table role="region">
<td id="self" headers="self">World</td>
</table>
All browsers expose this element as a table:
- Chrome exposes it as a table.
- Safari exposes it as a table.
- Firefox exposes it as a table, but treats its children as generic elements!?
Since this example introduces ambiguity, IMO it should be adjusted. We can either add an aria-label to ensure role="region" is correctly applied or replace it with a role that does not require an accessible name.
In Headers attribute specified on a cell refers to cells in the same table element, Inapplicable Example 6 is ambiguous because role="region" requires an accessible name. Without one, browsers treat it as a generic element.
In Inapplicable Example 6
All browsers expose this element as a table:
Since this example introduces ambiguity, IMO it should be adjusted. We can either add an aria-label to ensure role="region" is correctly applied or replace it with a role that does not require an accessible name.