Plus UI Design · Practical guides

Review a table for accessibility

A visual table needs clear relationships and usable controls, not just attractive borders.

Describe the data

Use a caption or nearby heading to explain what the table contains. Use header cells for headings and data cells for values. A simple table normally needs column headers with scope="col"; more complex multi-level headers require an explicit relationship review.

Make actions understandable

If every row contains an “Edit” action, give each action a name that identifies its row, such as “Edit Atlas.” Keep focus visible and use actual buttons or links for actions. Do not rely on a row’s background color alone to explain its state.

Check the completed application

Review keyboard order, screen-reader announcements, contrast and zoom in the application that uses the exported markup. A code export is a starting point; the surrounding UI and any interactive behavior determine the final experience.