adobe / adobe/aem-core-wcm-components
[Table] Identify layout table
- Dominant language
- Java
- Stars
- 795
- Forks
- 775
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 8
Description
## Feature Request
In French-speaking countries, for accessibility audit we use the RGAA accessibility guidelines.
**Is your feature request related to a problem? Please describe.**
In the criteria 5.3, we test if each layout table (`` only used to display information in cells) has an attribute role="presentation" to success.
This test failed :
- if the table doesn't have the role="presentation"
- if the table has a caption (`` tags)
- if the table has headings (`` tags)
In some of our website, redactors use table to diplay content in column. For those websites, in the Accessibility Audit, we get a fail due to the missing role attribute.
**Describe the solution you'd like**
The simplest solution will be to automatically add the role="presentation" attribute to the `` element when the user choose the "None" option in the Header selector.
On top of that a layout table shouldn't contain any `` tag, so it will be nice to disable this field when "None" is selected in the Header selector.

**Are there alternatives?**
We can also add a checkbox in the table tool to switch between data-table and layout-table.
**Documentation**
- W3C Tables tutorial : https://www.w3.org/WAI/tutorials/tables/
- W3C use of role=presentation : https://www.w3.org/WAI/ARIA/apg/practices/hiding-semantics/
- RAWeb 5.3.1 : https://accessibilite.public.lu/en/raweb1/criteres.html#test-5-3-1 (In english)
- RGAA 5.3.1 : https://accessibilite.numerique.gouv.fr/methode/criteres-et-tests/#5.3.1 (In french)
- WCAG F49 : https://www.w3.org/WAI/WCAG21/Techniques/failures/F49
Contributor guide
Research direction
Start by locating the table component's Header selector and table tool implementation. Verify how the None option currently renders the table, caption, and headings; done means layout tables receive role="presentation" and the caption field is unavailable when None is selected, with the behavior covered by the project's component tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100