Need Help With Accessibility?

  • Accessibility Audits
  • Accessible Web Design
  • Accessible Documentation
  • AODA and Customer Service Standard

For any or all of these Accessibility requirements use our Contact form.

1.3.1: Info and Relationships: (A)

Note: To find more information on items such as G14: for example, visit the "Understanding"link at the bottom of each Guideline

Information, structure,and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A

Sufficient Techniques for 1.3.1 – Info and Relationships

Situation A: The technology provides semantic structure to make information
and relationships conveyed through presentation programmatically determinable:

  • 1.G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special text (HTML)
  • 2.G117: Using text to convey information that is conveyed by variations in presentation of text
  • 3.G140: Separating information and structure from presentation to enable different presentations
  • 4.Making information and relationships conveyed through presentation programmatically determinable using the following techniques:
  • G138: Using semantic markup whenever color cues are used
  • H51: Using table markup to present tabular information (HTML)
  • 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)
  • 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)
  • H71: Providing a description for groups of form controls using fieldset and legend elements (HTML)
  • H85: Using OPTGROUP to group OPTION elements inside a SELECT (HTML)
  • H48: Using ol, ul and dl for lists (HTML)
  • H42: Using h1-h6 to identify headings (HTML)
  • SCR21: Using functions of the Document Object Model (DOM) to add content to a page (Scripting)

Situation B: The technology in use does NOT provide the semantic structure to make the information and relationships conveyed through presentation programmatically determinable:

  • 1.G117: Using text to convey information that is conveyed by variations in presentation of text
  • 2.Making information and relationships conveyed through presentation programmatically determinable or available in text using the following techniques:
  • T1: Using standard text formatting conventions for paragraphs (TXT)
  • T2: Using standard text formatting conventions for lists (TXT)
  • T3: Using standard text formatting conventions for headings (TXT)

Advisory Techniques for 1.3.1 – Info and Relationships

  • C22: Using CSS to control visual presentation of text (CSS)
  • Using CSS rather than tables for page layout
  • G162: Positioning labels to maximize predictability of relationships
  • ARIA1: Using Accessible Rich Internet Application describedby property to provide a descriptive, programmatically determined label
    (ARIA)
  • ARIA4: Using Accessible Rich Internet Applications to programmatically identify form fields as required (ARIA)
  • Providing labels for all form controls that do not have implicit labels
  • G141: Organizing a page using headings

Failures for SC 1.3.1 – Info and Relationships

  • F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text
  • F17: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML
  • F33: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content
  • F34: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to format tables in plain text content
  • F42: Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable
  • F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content
  • F46: Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables
  • F48: Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information
  • F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML
  • F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text
  • F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable
  • F87: Failure of 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the ‘content’ property in CSS

http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html

Conformance

See http://www.w3.org/TR/WCAG20/ for more detail.

This section lists requirements for conformance to WCAG 2.0. It also gives information about how to make conformance claims, which are optional. Finally, it describes what it means to be accessibility supported, since only accessibility-supported ways of using technologies can be relied upon for conformance.

Understanding Conformance includes further explanation of the accessibility-supported concept.

Conformance Requirements

In order for a Web page to conform to WCAG 2.0, all of the following conformance requirements must be satisfied:

1. Conformance Level:

One of the following levels of conformance is met in full.

  • Level A: For Level A conformance (the minimum level of conformance), the Web page satisfies all the Level A Success Criteria, or a conforming alternate version is provided.
  • Level AA: For Level AA conformance, the Web page satisfies all the Level A and Level AA Success Criteria, or a Level AA conforming alternate version is provided.
  • Level AAA: For Level AAA conformance, the Web page satisfies all the Level A, Level AA and Level AAA Success Criteria, or a Level AAA conforming alternate version is provided.

Note 1: Although conformance can only be achieved at the stated levels, authors are encouraged to report (in their claim) any progress toward meeting success criteria from all levels beyond the achieved level of conformance.

Note 2: It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content.

2. Full pages:

Conformance (and conformance level) is for full Web page(s) only, and cannot be achieved if part of a Web page is excluded.

Note 1: For the purpose of determining conformance, alternatives to part of a page's content are considered part of the page when the alternatives can be obtained directly from the page, e.g., a long description or an alternative presentation of a video.

Note 2: Authors of Web pages that cannot conform due to content outside of the author's control may consider a Statement of Partial Conformance.

3. Complete processes:

When a Web page is one of a series of Web pages presenting a process (i.e., a sequence of steps that need to be completed in order to accomplish an activity), all Web pages in the process conform at the specified level or better. (Conformance is not possible at a particular level if any page in the process does not conform at that level or better.)

Example: An online store has a series of pages that are used to select and purchase products. All pages in the series from start to finish (checkout) conform in order for any page that is part of the process to conform.

4. Only Accessibility-Supported Ways of Using Technologies:

Only accessibility-supported ways of using technologies are relied upon to satisfy the success criteria. Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is accessibility supported. (See Understanding accessibility support.)

5. Non-Interference:

If technologies are used in a way that is not accessibility supported, or if they are used in a non-conforming way, then they do not block the ability of users to access the rest of the page. In addition, the Web page as a whole continues to meet the conformance requirements under each of the following conditions:

  • 1.when any technology that is not relied upon is turned on in a user agent,
  • 2.when any technology that is not relied upon is turned off in a user agent, and
  • 3.when any technology that is not relied upon is not supported by a user agent

In addition, the following success criteria apply to all content on the page, including content that is not otherwise relied upon to meet conformance, because failure to meet them could interfere with any use of the page:

  • 1.4.2 - Audio Control,
  • 2.1.2 - No Keyboard Trap,
  • 2.3.1 - Three Flashes or Below Threshold, and
  • 2.2.2 - Pause, Stop, Hide.

Note: If a page cannot conform (for example, a conformance test page or an example page), it cannot be included in the scope of conformance or in a conformance claim.

For more information, including examples, see Understanding Conformance Requirements.

Conformance Claims (Optional)

Conformance is defined only for Web pages. However, a conformance claim may be made to cover one page, a series of pages, or multiple related Web pages.

Required Components of a Conformance Claim

Conformance claims are not required. Authors can conform to WCAG 2.0 without making a claim. However, if a conformance claim is made, then the conformance claim must include the following information:

  • 1. Date of the claim
  • 2. Guidelines title, version and URI "Web Content Accessibility Guidelines 2.0 at http://www.w3.org/TR/2008/REC-WCAG20-20081211/"
  • 3. Conformance level satisfied: (Level A, AA or AAA)
  • 4. A concise description of the Web pages, such as a list of URIs for which the claim is made, including whether subdomains are included in the claim.Note 1: The Web pages may be described by list or by an expression that describes all of the URIs included in the claim. Note 2: Web-based products that do not have a URI prior to installation on the customer's Web site may have a statement that the product would conform when installed.
  • 5.A list of the Web content technologies relied upon.

Note: If a conformance logo is used, it would constitute a claim and must be accompanied by the required components of a conformance claim listed above.

Optional Components of a Conformance Claim

In addition to the required components of a conformance claim above, consider providing additional information to assist users. Recommended additional information includes:

  • A list of success criteria beyond the level of conformance claimed that have been met. This information should be provided in a form that users can use, preferably machine-readable metadata.
  • A list of the specific technologies that are "used but not relied upon."
  • A list of user agents, including assistive technologies that were used to test the content.
  • Information about any additional steps taken that go beyond the success criteria to enhance accessibility.
  • A machine-readable metadata version of the list of specific technologies that are relied upon.
  • A machine-readable metadata version of the conformance claim.

Note 1: Refer to Understanding Conformance Claims for more information and example conformance claims.

Note 2: Refer to Understanding Metadata for more information about the use of metadata in conformance claims.

Statement of Partial Conformance - Third Party Content

Sometimes, Web pages are created that will later have additional content added to them. For example, an email program, a blog, an article that allows users to add comments, or applications supporting user-contributed content. Another example would be a page, such as a portal or news site, composed of content aggregated from multiple contributors, or sites that automatically insert content from other sources over time, such as when advertisements are inserted dynamically.

In these cases, it is not possible to know at the time of original posting what the uncontrolled content of the pages will be. It is important to note that the uncontrolled content can affect the accessibility of the controlled content as well. Two options are available:

  • 1.A determination of conformance can be made based on best knowledge. If a page of this type is monitored and repaired (non-conforming content is removed or brought into conformance) within two business days, then a determination or claim of conformance can be made since, except for errors in externally contributed content which are corrected or removed when encountered, the page conforms. No conformance claim can be made if it is not possible to monitor or correct non-conforming content; OR
  • 2.A "statement of partial conformance" may be made that the page does not conform, but could conform if certain parts were removed. The form of that statement would be, "This page does not conform, but would conform to WCAG 2.0 at level X if the following parts from uncontrolled sources were removed." In addition, the following would also be true of uncontrolled content that is described in the statement of partial conformance:
    • a.It is not content that is under the author's control.
    • b.It is described in a way that users can identify (e.g., they cannot be described as "all parts that we do not control" unless they are clearly marked as such.)

Statement of Partial Conformance - Language

A "statement of partial conformance due to language" may be made when the page does not conform, but would conform if accessibility support existed for (all of) the language(s) used on the page. The form of that statement would be, "This page does not conform, but would conform to WCAG 2.0 at level X if accessibility support existed for the following language(s):"