translate
  1. Functional Accessibility Requirements
  2. 10. Non-web documents
  3. 10.2: Document success criteria
  4. 10.2.38: Name, role, value

10.2.38: Name, role, value

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.38.

Table 10.38: Document success criterion: Name, role, value
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification.

NOTE 2: For document formats that support interoperability with assistive technology, standard user interface components often meet this success criterion when used according to the general design and accessibility guidance for the document format.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 4.1.2 Name, Role, Value replacing the original WCAG 2.0 note with: "This success criterion is primarily for software developers who develop or use custom user interface components. For example, standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification." and with the addition of note 2 above.

Testing methods

Type of compliance Inspection
Pre-conditions
  1. The ICT is a non-web document.
Procedure
  1. Check that the document does not fail the Success Criterion in Table 10.38.
Result Pass: Check 1 is true
Fail: Check 1 is false

There is currently no content classified with this term.