Skip to content

[BUG]: update table rules when a table element takes a role rather than "table" role #2238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shunguoy opened this issue Mar 31, 2025 · 2 comments
Labels
engine Issues in the accessibility-checker-engine component Spec change When specs/versions are updated or change T70

Comments

@shunguoy
Copy link
Contributor

shunguoy commented Mar 31, 2025

Project

accessibility-checker-engine

Browser

No response

Operating system

No response

Description

A <table> element can take any role based on ARIA in HTML spec. When a native <table> element takes a role other than a "table" role, the table is no longer a table anymore, and the requirements for this non-table ARIA role should not follow the native table-element rules, but rather the overriding ARIA role specified by the author rules.

For example, the following violations might be false positives when AIRA role = "non-table":

  • Table has no headers identified, reported by table_headers_exists rule.
  • "An explicit ARIA 'role' is not valid for <tr> element within an ARIA role 'xxx' per the ARIA in HTML specification" by table_aria_descendants rule.

Steps to reproduce

Refer to ACT test case for an example.

@shunguoy shunguoy added engine Issues in the accessibility-checker-engine component Spec change When specs/versions are updated or change labels Mar 31, 2025
@shunguoy shunguoy changed the title [BUG]: update table rules when the table takes a role rather than "table" [BUG]: update table rules when a table element takes a role rather than "table" role Mar 31, 2025
@philljenkins
Copy link
Contributor

@shunguoy I tweaked the description

@shunguoy shunguoy added the T70 label Apr 14, 2025
@shunguoy
Copy link
Contributor Author

Triage: need to revisit: table_ariadescendant, table_caption, table_headers, table_summary
but table_layout, table_scope, table_structure are fine.

No issue was reported from IBM cloud or Carbon, except one from a legacy app using Dojo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine Issues in the accessibility-checker-engine component Spec change When specs/versions are updated or change T70
Projects
None yet
Development

No branches or pull requests

2 participants