Skip to content

Digital accessibility

Digital accessibility aims to ensure that people, including those with disabilities, can perceive, understand and use digital products and content

What it means, how it is used and where it comes up, with its related concepts.

What it is and how it works

It covers structure, interaction, alternatives and compatibility with assistive technologies. It should be built in from the design stage and checked through technical evaluation and real use. An automated review detects some issues, but it does not verify the whole experience.

Where we work on it

Experience

Frequently asked questions about Digital accessibility

Does meeting WCAG prove that everyone will be able to complete a task?

Conformance with the Web Content Accessibility Guidelines, or WCAG, certifies that defined criteria are met within the scope evaluated. It does not allow you to assume that anyone will complete any task without difficulty. It is worth combining that evaluation with usability tests that include diverse needs and reviewing the full journey. It also matters to state the version, the level and the parts of the product that were checked.

What should you ask for when commissioning an accessibility evaluation?

An explicit scope, the reference standard and level, the method for selecting pages and processes, and a report that makes it possible to reproduce the issues. It is worth agreeing how keyboard, assistive technologies and complete tasks will be reviewed, as well as the automated checks. The result should distinguish what was evaluated from what was left out and state how to verify the fixes. An overall score without evidence is not enough to act on.

Can an overlay solution replace fixing the product?

It should not be taken as enough without checking which issues it solves and which remain. An added layer can change certain aspects of the interface, but accessibility also depends on structure, content, interaction and journey. It is worth evaluating the result as rigorously as any other solution and fixing issues at their source where appropriate. Installing a tool does not on its own certify conformance or a usable experience.

How do you keep accessibility from being lost when content is updated?

It has to be built into the creation and review process, with responsibilities and checks suited to the type of change. For example, a new image needs a relevant alternative and a video may need subtitles, even if the template is already accessible. It is worth training those who publish and also reviewing modified components. Periodic evaluation helps detect regressions; an earlier review only describes the version that was checked.

Related concepts

References