Skip to content
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

update td, th, tr allowances when within a table/grid/treegrid #372

Closed
scottaohara opened this issue Mar 27, 2021 · 8 comments
Closed

update td, th, tr allowances when within a table/grid/treegrid #372

scottaohara opened this issue Mar 27, 2021 · 8 comments
Assignees
Labels
Bug Something isn't working engine Issues in the accessibility-checker-engine component priority-2 (med) question Further information is requested Ready for QA SME Discuss with subject matter experts Standards user-reported Issues identified outside of the core team

Comments

@scottaohara
Copy link

Per ARIA in HTML when used within a role=table, grid, treegrid the td, tr, and th elements should not be allowed any explicitly set role, as that would break the a11y mappings of the table, grid or treegrid.
td in role=table
td in role=grid
td in role=treegrid

tr in role=table
tr in role=grid
tr in role=treegrid

th in role=table
th in role=grid
th in role=treegrid

expectations:

  • if a <td>'s ancestor table element has role=table, grid or treegrid - then no allowed role.
  • if a <th>'s ancestor table element has role=table, grid or treegrid - then no allowed role.
  • if a <tr>'s ancestor table element has role=table, grid or treegrid - then no allowed role.
  • if any use of cell, gridcell, row, rowheader, columnheader are found on these elements - then those should produce warnings as being unnecessary

if a td, tr, or th are used within a table with no set role, thus it should be an implicit role=table (regardless of what browser heuristics may do) - then no allowed role
td within a table testcase
th within a table testcase
tr within a table testcase

If td, tr, or th are used within a table where it's role is overwritten by a role not mentioned above (e.g., role=none, article, etc), then these elements can continue to allow any role. the checker already meets this expectation

@scottaohara scottaohara added the Bug Something isn't working label Mar 27, 2021
@tombrunet tombrunet added the engine Issues in the accessibility-checker-engine component label Apr 21, 2021
Copy link

Jun 1, 2021

As of June 1

  • general rule description (SME & Dev)
  • testcases written (Dev)
  • rule developed (Dev)
  • message written (SME)
  • help written (SME)

@tombrunet
Copy link
Member

@carmacleod @philljenkins We created a new rule for this one, but then we updated the allowed ARIA roles, so we end up with two errors. Which error do you think we should remove?
image

Note that the first one even triggers when the role is redundant (e.g., cell on a td) whereas the second will not trigger when redundant. The second seems more consistent with the note that this case should be a warning.

@tombrunet tombrunet added question Further information is requested SME Discuss with subject matter experts labels Dec 16, 2021
@scottaohara
Copy link
Author

As an FYI, we have received some feedback that allowing explicit declaring of implicit roles on tables and their children should be reduced to a warning, or not reported. e.g., table role=grid > tr > td role=gridcell this is specifically due to some browsers still dropping table semantics due to CSS styling.

I don't know if this helps or hinders the decision here, but as this popped up in my github notifications, I wanted to let you know that we were going to clarify this in an upcoming update to these rules.

@carmacleod
Copy link
Contributor

@tombrunet I think we should remove the first rule and keep the 2nd. We don't want to trigger on explicit declaring of implicit roles, although we should discuss whether those should be "needs review".

@aliunwala
Copy link
Contributor

Triage:
This is as simple as removing a rule from the ruleset. We will have SME's take a look at this to confirm which we want to deprecate and pass it to dev.

@shunguoy
Copy link
Contributor

shunguoy commented Mar 7, 2022

#721 covers updated ARIA attributes but doesn't cover users explicitly specifying a role that is implicitly available. The second case needs to be considered in a different rule.

@shunguoy
Copy link
Contributor

close as fixed per #789

@ErickRenteria
Copy link
Contributor

Validated

@philljenkins philljenkins added Standards user-reported Issues identified outside of the core team labels Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working engine Issues in the accessibility-checker-engine component priority-2 (med) question Further information is requested Ready for QA SME Discuss with subject matter experts Standards user-reported Issues identified outside of the core team
Projects
None yet
Development

No branches or pull requests

8 participants