Info and Relationships:
Understanding SC 1.3.1
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
Intent of this Success Criterion
The intent of this Success Criterion is to ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes. For example, the presentation format changes when the content is read by a screen reader or when a user style sheet is substituted for the style sheet provided by the author.
Sighted users perceive structure and relationships through various visual cues — headings are often in a larger, bold font separated from paragraphs by blank lines; list items are preceded by a bullet and perhaps indented; paragraphs are separated by a blank line; items that share a common characteristic are organized into tabular rows and columns; form fields may be positioned as groups that share text labels; a different background color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them; items that share a common characteristic are organized into a table where the relationship of cells sharing the same row or column and the relationship of each cell to its row and/or column header are necessary for understanding; and so on. Having these structures and these relationships programmatically determined or available in text ensures that information important for comprehension will be perceivable to all.
Auditory cues may be used as well. For example, a chime might indicate the beginning of a new section; a change in voice pitch or speech rate may be used to emphasize important information or to indicate quoted text; etc.
When such relationships are perceivable to one set of users, those relationships can be made to be perceivable to all. One method of determining whether or not information has been properly provided to all users is to access the information serially in different modalities.
If links to glossary items are implemented using anchor elements (or the proper link element for the technology in use) and identified using a different font face, a screen reader user will hear that the item is a link when the glossary term is encountered even though they may not receive information about the change in font face. An on-line catalog may indicate prices using a larger font colored red. A screen reader or person who cannot perceive red, still has the information about the price as long as it is preceded by the currency symbol.
Some technologies do not provide a means to programmatically determine some types of information and relationships. In that case then there should be a text description of the information and relationships. For instance, "all required fields are marked with an asterisk (*)". The text description should be near the information it is describing (when the page is linearized), such as in the parent element or in the adjacent element.
There may also be cases where it may be a judgment call as to whether the relationships should be programmatically determined or be presented in text. However, when technologies support programmatic relationships, it is strongly encouraged that information and relationships be programmatically determined rather than described in text.
Note: It is not required that color values be programmatically determined. The information conveyed by color cannot be adequately presented simply by exposing the value. Therefore, Success Criterion 1.4.1 addresses the specific case of color, rather than Success Criterion 1.3.1.
Specific Benefits of Success Criterion 1.3.1:
This Success Criterion helps people with different disabilities by allowing user agents to adapt content according to the needs of individual users.
Users who are blind (using a screen reader) benefit when information conveyed through color is also available in text (including text alternatives for images that use color to convey information).
Users who are deaf-blind using braille (text) refreshable displays may be unable to access color-dependent information.
Examples of Success Criterion 1.3.1
A form with required fields
A form contains several required fields. The labels for the required fields are displayed in red. In addition, at the end of each label is an asterisk character, *. The instructions for completing the form indicate that "all required fields are displayed in red and marked with an asterisk *", followed by an example.
A form that uses color and text to indicate required fields
A form contains both required and optional fields. Instructions at the top of the form explain that required fields are labeled with red text and also with an icon whose text alternative says, "Required." Both the red text and the icon are programmatically associated with the appropriate form fields so that assistive technology users can determine the required fields.
A bus schedule table where the headers for each cell can be programmatically determined
A bus schedule consists of a table with the bus stops listed vertically in the first column and the different buses listed horizontally across the first row. Each cell contains the time when the bus will be at that bus stop. The bus stop and bus cells are identified as headers for their corresponding row or column so that assistive technology can programmatically determine which bus and which bus stop are associated with the time in each cell.
A form where the labels for the checkboxes can be programmatically determined
In a form, the labels for each checkbox can be programmatically determined by assistive technology.
A text document
A simple text document is formatted with double blank lines before titles, asterisks to indicate list items and other standard formatting conventions so that its structure can be programmatically determined.
Related Resources
Resources are for information purposes only, no endorsement implied.
Techniques and Failures for Success Criterion 1.3.1 - Info and Relationships
Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see Understanding Techniques for WCAG Success Criteria, particularly the "Other Techniques" section.
Sufficient Techniques
Instructions: Select the situation below that matches your content. Each situation includes techniques or combinations of techniques that are known and documented to be sufficient for that situation.
Situation A: The technology provides semantic structure to make information and relationships conveyed through presentation programmatically determinable:
ARIA11: Using ARIA landmarks to identify regions of a page (ARIA)
ARIA13: Using aria-labelledby to name regions and landmarks (ARIA)
ARIA16: Using aria-labelledby to provide a name for user interface controls (ARIA)
ARIA17: Using grouping roles to identify related form controls (ARIA)
ARIA20: Using the region role to identify a region of the page (ARIA)
G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special text (HTML)
G117: Using text to convey information that is conveyed by variations in presentation of text
G140: Separating information and structure from presentation to enable different presentations
Making information and relationships conveyed through presentation programmatically determinable using the following techniques:
H51: Using table markup to present tabular information (HTML)
PDF6: Using table elements for table markup in PDF Documents (PDF)
PDF20: Using Adobe Acrobat Pro's Table Editor to repair mistagged tables (PDF)
H39: Using caption elements to associate data table captions with data tables (HTML)
H73: Using the summary attribute of the table element to give an overview of data tables (HTML)
H63: Using the scope attribute to associate header cells and data cells in data tables (HTML)
H43: Using id and headers attributes to associate data cells with header cells in data tables (HTML)
FLASH21: Using the DataGrid component to associate column headers with cells (Flash)
H44: Using label elements to associate text labels with form controls (HTML)
H65: Using the title attribute to identify form controls when the label element cannot be used (HTML)
PDF10: Providing labels for interactive form controls in PDF documents (PDF)
PDF12: Providing name, role, value information for form fields in PDF documents (PDF)
FLASH32: Using auto labeling to associate text labels with form controls (Flash)
FLASH29: Setting the label property for form components (Flash)
FLASH25: Labeling a form control by setting its accessible name (Flash)
H71: Providing a description for groups of form controls using fieldset and legend elements (HTML)
SL20: Relying on Silverlight AutomationPeer Behavior to Set AutomationProperties.Name (Silverlight)
SL26: Using LabeledBy to Associate Labels and Targets in Silverlight (Silverlight)
H85: Using OPTGROUP to group OPTION elements inside a SELECT (HTML)
H48: Using ol, ul and dl for lists or groups of links (HTML)
PDF9: Providing headings by marking content with heading tags in PDF documents (PDF)
SCR21: Using functions of the Document Object Model (DOM) to add content to a page (Scripting)
PDF17: Specifying consistent page numbering for PDF documents (PDF)
Situation B: The technology in use does NOT provide the semantic structure to make the information and relationships conveyed through presentation programmatically determinable:
G117: Using text to convey information that is conveyed by variations in presentation of text
FLASH8: Adding a group name to the accessible name of a form control (Flash)
Making information and relationships conveyed through presentation programmatically determinable or available in text using the following techniques:
Additional Techniques (Advisory) for 1.3.1
Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.
Using CSS rather than tables for page layout (future link)
G162: Positioning labels to maximize predictability of relationships
ARIA2: Identifying a required field with the aria-required property (ARIA)
Providing labels for all form controls that do not have implicit labels (future link)
Common Failures for SC 1.3.1
The following are common mistakes that are considered failures of Success Criterion 1.3.1 by the WCAG Working Group.
Key Terms
- presentation
rendering of the content in a form to be perceived by users
- programmatically determined (programmatically determinable)
determined by software from author-supplied data provided in a way that different user agents, including assistive technologies, can extract and present this information to users in different modalities
Example 1: Determined in a markup language from elements and attributes that are accessed directly by commonly available assistive technology.
Example 2: Determined from technology-specific data structures in a non-markup language and exposed to assistive technology via an accessibility API that is supported by commonly available assistive technology.
- relationships
meaningful associations between distinct pieces of content
- structure