This document attempts to fill the following gaps in the accessibility publications:
- For Web documents, in W3C, there are several specific examples of how accessible pages must be designed (see, for example How to Meet WCAG (Quickref Reference) (w3.org) (External Link)). Corresponding documents are not available for software.
- Section 11 of EN 301 549 details the requirements concerning software. These requirements are of a general nature. There is no description of how UI elements must be specifically implemented in order to meet the requirements. For desktop software, there is no equivalent to the WAI-ARIA Authoring Practices ( WAI-ARIA Authoring Practices 1.2 (w3.org) (External Link)).
- In the form of WCAG2ICT ( Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) (w3.org) (External Link)) in 2013, W3C published a document describing the way in which the WCAG requirements can be applied to software and documents. This document is outdated, however, and does not contain the requirements of the current WCAG 2.1.
The document is primarily aimed at software developers.
Other roles in the field of software development for which the document may be helpful include
- Design (especially with regard to the requirements of fonts, colors an contrasts and the information in the “presentation” sections for each UI element),
- Editing for the text content of the software and Help,
- Accessibility test,
- Disabled people who use software (to familiarize themselves with common keyboard conventions, for example, refer to the “use of the keyboard” sections for each UI element).
Information about this article
You are welcome to send feedback by email about our handout!