DQM and Experience Optimization
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

DQM Checkpoints and Standards

Checkpoints - All data tables should correctly define header rows and column headers

Why is this important?

A table organizes grouped data in a way that makes this data easily perceivable. When users read the table, they can quickly look up the axis the data value belongs to. To allow assistive technology users to make that connection, table header rows or columns need to be defined in the markup of the page. 

For the basic functionality, <th> elements need to be present in every <table> element. Table header rows and columns can be specified in multiple ways, for example by using the scope attribute on simpler tables or by using the header and id attributes on more complex ones.

How can I resolve this issue?

Review the table being flagged as an issue.

If there is no row or column headers listed in the table, identify how this can be added and create this marking the row or column with the <th> tag.

If there is a column or row or column header ensure that the header is encoded with a table header <th> tag instead of a table data <td> tag

What topics do this checkpoint affect?

  • Accessibility (WCAG 2 Level A, 1.3.1)

Can you explain how this checkpoint works?

The checkpoint examines the entire HTML source code of a page and reports if within <table> elements no table headers <th> is found.

References

Version history
Revision #:
5 of 5
Last update:
3 weeks ago
Updated by:
 
Looking for more?
Ask in Discussions
Developers

Peer-to-peer support  and answers on developing CMS templates, modifying privacy scripts or building integrations.

Digital Experience Management

Find answers and ask questions on content management, personalization and targeting.

Digital Quality Management

Find answers and ask questions on WCAG and SEO quality management.

Digital Governance

Find answers and ask questions on consent and monitoring solutions.