Overview

Tables can be useful for organizing form layouts, but they require special handling to work properly with assistive technology. This lesson covers when tables work well for forms, how to prepare them correctly, and how to ensure form fields within tables are accessible.

Core Concepts

When Tables Work for Forms

Earlier in the module, we talked about linearizing tables that have inconsistent row structures. However, some tables can work quite well for forms if they're structured consistently. A table with a predictable pattern, where every row has the same number of cells and the same relationship between labels and fields, can be left as a proper table structure.

The key is consistency. If your table has three columns in every row (a label column, a form field column, and perhaps an instructions column), screen reader users can navigate it predictably. They'll understand the pattern and know what to expect as they move from row to row. However, if some rows have two cells, others have three, and others have been merged in complex ways, you're better off linearizing the table entirely.

Preparing Tables for Form Fields

When you keep a table as a proper table structure, you need to define the header relationships. Typically, you'll mark the first column as headers (if it contains field labels) or the first row as headers (if you're using a horizontal layout). This tells screen readers which cells provide context for the data cells.

After adding form fields to table cells, you'll need to clean up any empty paragraph tags that Word created during the export process. These empty tags can clutter the structure and confuse screen readers. You'll also need to position each form field tag within the appropriate table cell tag in the tags tree, just like you positioned form fields elsewhere in the document.

The video below explores how to work with tables in forms, including when to keep table structure, how to define headers, and how to position form fields within table cells.

Working with Forms in Tables (9 mins)

Check Your Understanding:

Your form uses a table layout where some rows have three cells, some have two cells, and some have one merged cell. What should you do with this table?

A. Keep it as a table and define header relationships for the cells

Incorrect.
Tables with inconsistent row structures create unpredictable navigation for screen reader users. This table should be linearized to remove the table structure while preserving the visual layout.

B. Linearize the table to remove the structure while maintaining the visual layout

Correct!
When tables have inconsistent row structures (varying numbers of cells per row), they should be linearized. This removes the table tags while preserving the visual appearance, creating a predictable experience for screen reader users.

C. Remove the table entirely and rebuild the layout without using tables

Incorrect.
You don't need to remove the table from the Word document. You can linearize it in the PDF to remove the table structure tags while keeping the visual layout intact.

D. Tables should never be used for forms, regardless of their structure

Incorrect.
Tables can work well for forms if they have consistent structure, every row has the same number of cells with predictable relationships. Only inconsistent tables need to be linearized.

Additional Resources

Tables Concepts - W3C tutorial on creating accessible tables
Editing Document Structure with Content Tags - Adobe's guide to working with table tags in PDFs
Creating Accessible Tables - WebAIM's comprehensive guide to accessible data tables

Click Next to advance to the next lesson or return to the Module Overview.