11.2.1.37: Parsing

Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the success criterion in Table 11.37.

Table 11.37: Software success criterion: Parsing

For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such as browsers. In such cases, conformance to this provision would have no impact on accessibility as it can for web content where it is exposed.

NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to user agents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats.

NOTE 4: Examples of markup used internally for persistence of the software user interface that are never exposed to assistive technology include but are not limited to: XUL, GladeXML, and FXML. In these examples assistive technology only interacts with the user interface of generated software.

NOTE 5: This success criterion is identical to the WCAG 2.0 Success Criterion 4.1.1 Parsing replacing "In content implemented using markup languages" with "For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent" with the addition of notes 2 and 3 above.

Testing methods

Type of complianceInspection
Pre-conditions
  1. The ICT is non-web software that provides a user interface.
  2. The software provides support to at least one assistive technology.
Procedure
  1.  Check that the software does not fail the Success Criterion in Table 11.37.
Result Pass: Check 1 is true
Fail: Check 1 is false

Requirement details

Reference number: 11.2.1.37

Related requirements

Related functional statements

Related technical requirements

No related technical requirements are associated with this technical requirement