
"There are many semantic HTML tags covered under WCAG SC 1.3.1: Info and Relationships, but in this article, we'll zoom in on one of the most misunderstood, the table. You might be thinking: "Do we really need tables when we already have semantic tags like lists?" It's a valid question. Lists (<ul>, <ol>, <dl>) are fantastic for presenting structured information, but when data grows beyond a simple one-to-one relationship, tables step in as the powerhouse."
"<table> <thead> <tr> <th>Full Name</th> <th>Date of Birth</th> <th>Gender</th> <th>Country</th> <th>Company</th> </tr> </thead> <tbody> <tr> <td>Tom Henry</td> <td>01-Jan-1999</td> <td>Male</td> <td>Australia</td> <td>Google</td> </tr> <tr> <td>Stifen Watson</td> <td>02-Jan-2000</td> <td>Male</td> <td>U.S.</td> <td>TPGi</td> </tr> </tbody> </table> This will look like:"
WCAG SC 1.3.1 covers semantic HTML tags and relationships, and tables are a key semantic element. Lists (<ul>, <ol>, <dl>) work well for simple one-to-one relationships and single-entity details. A description list presents a single person’s details clearly but becomes unwieldy for multiple records. Tables organize multi-row, multi-column datasets into rows and columns, making it easier for all users, including screen reader users, to locate specific information. Proper table structure uses thead, tbody, tr, th, and td elements to convey headers and cell relationships for improved accessibility.
Read at TPGi - a Vispero company
Unable to calculate read time
Collection
[
|
...
]