translate
  1. Functional Accessibility Requirements
  2. 11. Software
  3. 11.2: Non-Web software success criteria
  4. 11.2.1: Non-Web software success criteria (excluding closed functionality)
  5. 11.2.1.27: Language of software

11.2.1.27: Language of software

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

Table 11.27: Software success criterion: Language of software
The default human language of software can be programmatically determined.

NOTE 1: Where software platforms provide a "locale / language" setting, applications that use that setting and render their interface in that "locale / language" would comply with this success criterion. Applications that do not use the platform "locale / language" setting but instead use an accessibility-supported method for exposing the human language of the software would also comply with this success criterion. Applications implemented in technologies where assistive technologies cannot determine the human language and that do not support the platform "locale / language" setting may not be able to meet this success criterion in that locale / language.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 3.1.1 Language of page, replacing "each web page" with "software" and with the addition of note 1 above.

Testing methods

Type of compliance Inspection
Pre-conditions
  1. The ICT is non-web software that provides a user interface.
  2. The software provides support to assistive technologies for screen reading.
Procedure
  1. Check that the software does not fail the Success Criterion in Table 11.27.
Result Pass: Check 1 is true
Fail: Check 1 is false

There is currently no content classified with this term.