There is no way to trigger the layout table rule to raise anything
See original GitHub issueExpectation: a layout table with a caption should raise an issue
Actual: no issues raised
Motivation: rules should work as advertised
axe-core version: 3.3.2
axe extension: 4.0.0
Table markup used to try to generate the issue
<table role="presentation">
<caption>presentation caption</caption>
<tr><td>hello</td></tr>
</table>
I also noticed that there are no integration tests for this rule.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Database Triggers
A constraint applies to existing data in the table and any statement that manipulates the table. Triggers constrain what transactions can do. A...
Read more >Restrict data input by using validation rules - Microsoft Support
Test existing data against a new validation rule · Open the table that you want to test in Design View. · Click Yes...
Read more >Grid layout and accessibility - CSS: Cascading Style Sheets
A grid layout should mean we do not need to change our document source in order to get the layout that we want....
Read more >Chapter 3. Data, Tables, and Database Design - O'Reilly
) is easy. Just open the table in Design View, click in the field's Default Value property, and type in the default value....
Read more >Table Layouts - W3C
Rows, columns, row groups, column groups, and cells may have borders drawn around them (there are two border models in CSS 2.1). Authors...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is intentional, it was done to close this false positive: https://github.com/dequelabs/axe-core/issues/561
I agree with these guys that this shouldn’t be a WCAG failure. Putting role=“presentation” on a table is a trick people use to force AT to ignore it, even if that table has markup like th / captions / scope=“”.
I think there’s a decent case to be made that this should be failed as part of a best practice. People shouldn’t write tables like that, but if you have a table that you need to fix, this is a valid way of doing it. Failing this under the existing rules would be a false positive.
Nope, we deprecated the rule so no testing needed.