Data tables are
- a good way for presenting information in a grid and to have columns or rows that show the meaning of the information in the grid.
- Someone that cannot see the table cannot make these visual associations, so proper markup must be used to make a programmatic association between elements within the table.
- Users of screen readers can then navigate through data tables one cell at a time, and they will hear the column and row headers spoken to them (Similar to the restructured order for mobile).
- With the current implementation only headers in the first row are foreseen by the editor (see screenshot).
Typical data table - Desktop view
Typical data table - Desktop view

Mobile view
Mobile view

What to check for
What to check for
- A table must have a title or a caption or both. This text should clearly indicate what the table is about.
- Headings in first row (horizontal line) should indicating column titles.
- Table has no merged cells
From an accessibility perspective, merged cells in tables should be avoided. On the one hand, these cells are never displayed correctly in a mobile view and it is impossible for screen readers to interpret them correctly. - Avoid blank cells when possible
If data is missing or unavailable, use an appropriate placeholder or indicator, such as- "N/A" for not applicable
- "Unknown" if the information is uncertain
- Add descriptive context for blank cells
For more complex tables, consider adding notes or captions explaining why certain cells are blank. For example, "Cells with a N/A indicate data was not collected."
System provides good defaults
This label indicates that the system provides already good defaults and that editors can rely upon them.
Editor fine tune
This label indicates that a fine tuning is necessary and that the proposed checkpoints need manual verification.
Reference for publisher

Defining headers for a new table in AEM

Editor view in AEM showing where to select cell type "header"