If your form contains items arranged
in a table layout, you must identify headings for each row and column.
This involves placing read-only fields with appropriate accessibility messages
at the start of every data column and row.
Accessibility regulations typically
require that row and data columns be identified for data tables. The goal
of this requirement is to ensure that screen reader users can correctly
Although XFDL does not support a true
table item, it is easy to arrange individual fields and other items in
a grid-like pattern, thereby replicating the functionality of a table.
In such cases, you should provide row and column headings with accessibility
messages that the screen readers can read aloud. You should also include
similar accessibility information for each cell, so that users always know
their current position within the table.
XForms forms do support
The following diagram shows a table
that enables users to select items for purchase. The table consists of
four columns and five rows.
Note that every row and column is identified
by a unique heading. Each heading consists of a read-only field and an
accessibility message. The accessibility message should identify the item
as a heading and whether it is a column or row. It is also helpful to number
each column or row. The following code shows the accessibility message
for the "Unit Price" column heading:
Heading 3 of 4</acclabel
When the focus is on the "Unit
Price" heading, the screen readers announce "Column heading 3
of 4. Editable text. Unit Price."
To help users with visual disabilities
be aware of their current position within the table, you should include
the column name and row number in the acclabel item for each cell. For
example, the following code creates a accessibility message for the cell
in the third row of the first column:
Row 3. Type the quantity of the
product you would
like to order.
Exceptions to this practice
Currently there are no exceptions to
Back to: Accessible