←  All terms
A
Accessibility

Accessibility Audit

An accessibility audit systematically checks a website for barriers and evaluates it against recognized standards such as WCAG.

An accessibility audit systematically checks a website for barriers and evaluates it against recognized standards such as WCAG. Implementation should favor native web standards and combine automated checks with keyboard and assistive-technology testing. The concept is closely related to WCAG and EN 301 549.

Read more

WCAG

EN 301 549

Lighthouse

Quality Assurance

FAQ

Accessibility Audit

When should an accessibility audit be repeated?
An audit belongs before a relaunch and should be repeated after major changes to design, components, or content models. A one-time review goes stale as soon as new content and features ship. Automated checks in quality assurance add continuous protection against regressions.
How does an accessibility audit differ from a Lighthouse test?
Lighthouse is a quick automated check with limited depth, whereas an audit evaluates pages systematically and adds manual testing. A high Lighthouse score therefore does not prove accessibility. It works as an early-warning tool during development, not as evidence of compliance.
What does an accessibility audit process typically look like?
The scope and evaluation standard come first, for example WCAG 2.2 at level AA. Representative pages and key user journeys are then tested both automatically and manually. The outcome is a report with prioritized findings that serves as the basis for remediation.
Are automated tools enough for an accessibility audit?
No, automated tools detect only a portion of barriers, such as missing alt attributes or insufficient contrast. Whether alternative text is meaningful or the focus order is logical only shows up in manual testing with a keyboard and screen reader. A reliable audit combines both approaches.