11.2: Non-Web software success criteria

Requirements in clause 11.2 apply to software:

  • that is not a web page;
  • not embedded in web pages nor used in the rendering or functioning of the page.

Clause 9 provides requirements for software that is in web pages or that is embedded in web pages and that is used in the rendering or that is intended to be rendered together with the web page in which it is embedded.

Clause 11.2.1 contains the software requirements for the functionality of software that provides a user interface and that is not closed functionality.

Clause 11.2.2 contains the software requirements for the closed functionality of software that provides a user interface.

The success criteria set out in clause 11.2 are intended to harmonize with the W3C Working Group Note [i.26] produced by the W3C's WCAG2ICT Task Force (http://www.w3.org/WAI/GL/WCAG2ICT-TF/).

Notes

  1. The intent of clause 11.2 is that it applies to non-web software.

  2. Software that provides a user interface includes its own content. Some examples of content in software include the controls and text displayed in a menu bar of a graphical user interface application, images that appear in a toolbar, prompts spoken in an auditory user interface, other user interaction controls, and other text, graphics or material that is not loaded from outside the software.

Testing methods

Type of complianceInspection and measurement
Pre-conditions
  1.  Software that provides a user interface is provided to the user.
Procedure
  1. (Conformance Level). Check that the non-closed functionality of the software satisfies all the software success criteria listed in table 3 of the present document, or a Level AA conforming alternate version is provided.
  2. (Conformance Level). Check that, for each conforming alternate version of a software, 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 that no part of the software is excluded when applying check 1.
  4. (Only Accessibility-Supported Ways of Using Technologies). Check that only accessibility-supported (http://www.w3.org/TR/WCAG20/#accessibility-supporteddef) ways of using technologies are relied upon to satisfy the success criteria.
  5. (Only Accessibility-Supported Ways of Using Technologies). Check 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.
  6. (Non-Interference). Check 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 software.
  7. (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.
  8. Check that, under the applicability conditions listed in column 2 of table 4 of the present document, the closed functionality of the software meets the closed functionality requirement listed in column 3 of table 4.
Result Pass: Checks 1 to 8 are true
Fail: Any check is false

 

Requirement details

Reference number: 11.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