Simplified Web Accessibility Guide


Question 5: Are tables understandable on various systems?

What does this mean?

As Web developers cannot control how their pages are viewed, tables need to be understandable when viewed in different resolutions or on different systems (e.g., screen readers, Braille displays, or palmtops).

Why does this present a problem?

People using screen readers, palmtops, or other devices, or people viewing only a portion of the page at a time (e.g., when using screen magnification or low-resolution) may have difficulty accessing information from pages with tables. Marking up tables properly provide these technologies with the appropriate information to support navigation in table cells and to access header and other table cell information.

Tables should be used to mark up truly tabular information (data tables) and, when possible, should be avoided to lay out pages (layout tables).

What are the solutions?

Priority 1 1. Identify table headers

Priority 12. Associate data cells with headers

Priority 23. Avoid tables for layout

  TIP     A simple way of viewing a page in linear form is to view it in the Lynx text browser. The Lynx viewer at http://www.delori.com/web/lynxview.html provides a rendering of the page as if the browser were Lynx.

Priority 24. Avoid structural markup for formatting

Priority 35. Provide table summaries

Priority 36. Abbreviate long headers

What is the bottom line?

The bottom line, as stated in WCAG Guideline 5, is ensure tables have necessary markup to be transformed gracefully by assistive devices.