Table accessibility issues

There are a few issues with the aria roles on the current table implementation:

• role="grid" should be an attribute on the table element instead of the inner grid
• all table rows (including the header row) should have role="row" even if they don’t have event handlers like onRowClick

See aria documentation for more details. Elements with role="grid" require descendants with role="row", and elements with role="rowheader" require an ancestor with role="row" which requires an ancestor with role="grid".

[thiemeljiri]

Is there a way how to not add these attributes? You have it wrong and even if that was implemented correctly it’s not always what you want, which is our case.

Role grid must be sued only when it’s a data grid with implemented keyboard navigation. Using such roles without implementing the rest hurts the accessibility.

I strongly suggest removal of the role grid and I would like to know the motivation behind adding it. This is how to use it properly and believe me, that’s not what you wan’t in many cases. https://www.w3.org/TR/wai-aria-practices/examples/grid/dataGrids.html https://www.w3.org/TR/wai-aria-practices/examples/grid/dataGrids.html

[jchen527]

Re: your comment about Grid having no role=“row” children, I believe elements with role=“grid” do require descendants with role=“row” or role=“rowgroup” because they are “Required Owned Elements”. I’ve been using the Accessibility Developer Tools chrome extension and the audit complains when there is only an element with role=“grid”.

Thanks for the quick review and role="rowgroup" change!