Table header cell has assigned cells- changes in response to the Task Force feedback
A couple of changes to Table header cell has assigned cells. All in response to the Task Force feedback.
Key points
- Changed the assumptions section and Failed example 1 in response to
I'm not convinced that tables without td should be treated as failures of this rule. Failed Example 1 visually conveys a table header cell with no data cells in its column. I don't think this meets the assumption of this rule: This rule assumes that table header cells have a relationship conveyed through presentation with other cells within the same table.
- Changed Passed example 5 in response to
Per the guidline these are the 2 techniques to associate headers with data cells, some of the passed examples don't do that. H63: Using the scope attribute to associate header cells and data cells in data tables H43: Using id and headers attributes to associate data cells with header cells in data tables
- Changed Failed Example 3 as per
The description of failed example 3 uses "table element" but it might be more appropriate to use "semantic role of grid" instead.
- Edited the applicability section in response to
- The applicability does not establish that the header is part of a table. Just because there is a table ancestor, doesn't mean it is part of that table. There could be any number of ancestors between the header cell and the table.
- The part about the table being included in the accessibility tree seems unnecessary. This may be my lack of imagination, but I can't come up with a way to take the table out of the accessibility tree, without either changing the role, or also taking the header cell out of the tree. That requirement seems unnecessary.
- Edited expectation as per #1517
Closes issue #1545 and #1517
Need for Final Call: 2 weeks
In #1552 Kasper is giving an example of mixed HTML/ARIA table where HTML parsing is throwing away the ARIA bit due to incorrect HTML 😕
Hey @Jym77, I also said during the last TF call that I'm unhappy with this rule as is and would prefer to scope it to HTML tables. I've been trying to find any type of information of how the "assignment" process looks like for ARIA only stuff but since there is no spec for it, that has not been possible.
I'm not sure if this should be put forward to the CG in the next meeting before any commit or not?
CG call: Restrict the rule to HTML tables
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.
:white_check_mark: ajanec01
:x: dependabot[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.
This is a very old PR and some of the issues are no longer applicable. It will also be difficult to follow all comments and I rebased the branch so a lot of other files got added to the review. Closing this PR and will open a new one.