10.2: Document success criteria

Note: The success criteria set out in this clause are intended to harmonize with the Working Group Note [i.26] produced by theĀ W3C's WCAG2 ICT Task Force.

Testing methods

Type of complianceInspection and measurement
  1.  Documents are provided to the user.
  1. (Conformance Level). Check that each document satisfies all the document success criteria listed in table 1 of the present document, or a conforming alternate version is provided.
  2. (Conformance Level) Check that, for each conforming alternate version of a document, the requirements outlined in the definition for conforming alternate versions (http://www.w3.org/TR/WCAG20/#conforming-alternate-versiondef) are met.
  3. (Full pages). Check, for each document, that no part of the document is excluded when applying check 1.
  4. (Complete processes). Check, for each document, that if it is one of a series of documents presenting a process (i.e. a sequence of steps that need to be completed in order to accomplish an activity), then all documents in the process meet checks 1 to 9.
  5. (Only Accessibility-Supported Ways of Using Technologies). Check, for each document, that only accessibility-supported (http://www.w3.org/TR/WCAG20/#accessibility-supporteddef) ways of using technologies are relied upon to satisfy the success criteria.
  6. (Only Accessibility-Supported Ways of Using Technologies). Check, for each document, that where information or functionality is provided in a way that is not accessibility supported (http://www.w3.org/TR/WCAG20/#accessibility-supporteddef), it is also available in a way that is accessibility supported.
  7. (Non-Interference). Check, for each document, that if technologies are used in a way that is not accessibility supported (http://www.w3.org/TR/WCAG20/#accessibility-supporteddef), 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 document.
  8. (Non-Interference). Check, for each document, that the document 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
  9. (Non-Interference). Check, for each document, that the following success criteria apply to all content in the document, including content that is not otherwise relied upon to meet conformance, because failure to meet them could interfere with any use of the document:
    • 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.

Result Pass: Checks 1 to 9 are true
Fail: Any check is false

NOTE 1: Various techniques can be used to demonstrate that WCAG 2.0 Success Criteria are met. A set of techniques for WCAG 2.0 that can be used for this purpose provided is by W3C at: http://www.w3.org/TR/WCAG20-TECHS/.

NOTE 2: Where it is not manageable to check every document that is provided to the user, then an appropriate methodology can be used to assess the overall conformance of the web content. A methodology for evaluating the conformance of websites to WCAG 2.0 is under development by W3C and is available at: http://www.w3.org/TR/WCAG-EM/.

NOTE 3: The WCAG 2.0 name for the conformance requirement is placed, in brackets, immediately after the check number in the table above.

NOTE 4: For check 1 it should be noted that 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 5: For check 3, for the purpose of determining conformance, alternatives to part of a document's content are considered part of the document when the alternatives can be obtained directly from the document, e.g. a long description or an alternative presentation of a video.

NOTE 6: For check 3, authors of documents that cannot conform due to content outside of the author's control may consider a Statement of Partial Conformance (http://www.w3.org/TR/WCAG20/#conformance-partial).

NOTE 7: For check 4, an example is where an online store has a series of documents that are used to select and purchase products. All documents in the series from start to finish (checkout) conform in order for any document that is part of the process to conform.

NOTE 8: For checks 5 and 6, see the definition for accessibility support (http://www.w3.org/TR/WCAG20/#accessibility-supporteddef) and "Understanding accessibility support" (http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-support-head) for further information.

NOTE 9: For checks 7, 8 and 9, if a document cannot conform (for example, a conformance test document or an example document), it cannot be included in the scope of conformance or in a conformance claim.

NOTE 10: For more information, including examples related to all checks, see "Understanding Conformance Requirements" (http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-conformance-requirements-head).

Requirement details

Reference number: 10.2

Related requirements

Related functional statements

No functional statements are associated with this technical requirement

Related technical requirements

No related technical requirements are associated with this technical requirement