What is meant by WCAG-oriented accessibility conformity?
The term “WCAG-oriented accessibility conformity” refers to software, websites, digital platforms and documents that are designed in accordance with internationally recognized digital accessibility requirements. The objective is to make digital content and applications accessible and usable for as many people as possible, including people with visual, hearing, motor, cognitive or speech-related impairments.
In many countries, the Web Content Accessibility Guidelines (WCAG) form the central basis for digital accessibility. They define requirements for digital content to be perceivable, operable, understandable and robust. In practice, conformity at Level AA is often used as the relevant target level, as it is referenced in many legal, public-sector and organizational accessibility requirements.
Depending on the country, sector or procurement context, different legal or normative frameworks may apply. In Germany, BITV 2.0 and the European standard EN 301 549 are particularly relevant. In many European contexts, including the United Kingdom public sector, EN 301 549 is also an important reference standard. In the United States, accessibility requirements are often associated with Section 508 and ADA-related regulations. In Australia, public bodies and organizations also commonly refer to WCAG-based accessibility requirements. Despite different names and scopes, these frameworks pursue the same core objective: making digital information, software functions and online services accessible to all user groups.
Typical software functions in the area of “WCAG-oriented accessibility conformity”:
- Keyboard operability: All essential software functions can be operated without a mouse using the keyboard.
- Screen reader compatibility: Content, navigation elements and controls are accessible to screen readers and are semantically structured.
- Sufficient color contrast: Text, icons and important interface elements provide adequate contrast against the background.
- Scalability of text and content: Content remains readable, understandable and functional when enlarged, for example up to 200%.
- Alternative text for images: Non-text content such as images, icons, graphics or buttons includes meaningful alternative text.
- Captions and transcripts: Audio and video content can be made more accessible through captions, transcripts or comparable alternatives.
- Clear form guidance: Input fields, mandatory fields, error messages and correction hints are clearly described and logically structured.
- Visible focus indicators: The keyboard focus clearly shows where the user is currently positioned, for example on links, buttons or form fields.
- Consistent navigation: Menus, page structures and interaction patterns are understandable, consistent and predictable.
- Accessible document output: Generated documents, such as PDF files, are structured, tag-based and usable with assistive technologies.
- Accessibility testing: The software supports tests, documentation or interfaces to accessibility testing tools in order to check compliance with relevant accessibility requirements.
Examples of “WCAG-oriented accessibility conformity”:
- A public administration application provides online forms that can be fully used with a keyboard and screen reader.
- A learning platform offers captions and transcripts for training videos and online courses.
- An e-commerce application uses high-contrast colors, clear navigation structures and alternative text for product images.
- A document management system generates accessible PDF documents with correct heading structure, reading order and tagging.
- A business software solution supports regular accessibility checks to document conformity with relevant WCAG, EN 301 549, BITV, Section 508 or comparable requirements.