// 19.11.2026
WCAG audit process and report
How an accessibility audit of websites and mobile apps works, why a scanner alone is not enough and what the report should contain.
An accessibility audit answers a simple question: can a blind, low-vision, motor-impaired or cognitively disabled person use your website or app without help from others? Here is how an audit works in practice and what the report should contain.
What is accessibility assessed against?
The basis is the Web Content Accessibility Guidelines (WCAG). Public-sector rules in the EU refer to WCAG 2.1 at level AA, and the European standard EN 301 549, also used for the European Accessibility Act, builds on the same criteria. Audits increasingly include the newer WCAG 2.2 criteria too, such as minimum touch target size and focus visibility.
The audit step by step
- Scope. We pick representative pages and screens: the home page, search, forms and key journeys such as submitting a request or completing a purchase.
- Automated scan. Tools quickly catch issues such as missing alternative text, low contrast or empty links.
- Manual testing. We go through the journeys with the keyboard only, with a screen reader (NVDA, VoiceOver, TalkBack), at 400% zoom and in high-contrast mode.
- Mobile apps. We check element labels for VoiceOver and TalkBack, support for large system text, screen orientation and touch target size.
- Report and walkthrough. We present the results to the team and agree the order of fixes.
- Retest. After the changes are deployed we check that the issues are resolved.
Why a scanner alone is not enough
Automated tools detect roughly a third of WCAG criteria. They cannot judge whether an image description makes sense, whether an error message says what to fix or whether focus moves to the right place when a dialog opens. A site that scores “100” in a scanner can still be unusable with a screen reader. For the same reason we do not recommend overlay widgets: they do not change the site's code and do not deliver compliance.
What the audit report should contain
- a list of issues, each mapped to a specific WCAG criterion,
- where it occurs, with a screenshot or code snippet,
- its priority and impact on users,
- a fix recommendation for developers and designers,
- a summary for decision makers and a proposed order of work,
- information useful for the accessibility statement.
How long does an audit take?
It depends on the size of the service and the number of journeys. A simple information site usually takes a few days; a large portal or a mobile app on two platforms takes from two to several weeks. Most of the time goes into manual testing and writing fix guidance.
Who must comply?
Public sector bodies must make their websites and mobile apps accessible and publish an accessibility statement. Since 28 June 2025 the European Accessibility Act has also covered selected private-sector services, including e-commerce, banking and passenger transport. An audit shows where a service stands and helps plan fixes, but it does not replace legal advice.
An audit is a start, not the finish
Accessibility degrades with every release: a new form, banner or PDF can introduce new issues. After an audit it is worth adding basic accessibility checks to the release process. To check your website or app, see our WCAG audit service or get in touch.
FAQ
Does the audit cover mobile apps?
Yes. We test iOS and Android apps with VoiceOver and TalkBack, as well as the mobile view of websites.
Can you fix the issues after the audit?
Yes. As a software house we fix code, components and interface design, then retest.
Does an audit give a “compliance certificate”?
There is no single official WCAG certificate. The report documents the state of the service on the day of testing and is the basis for fixes and the accessibility statement.
Quote
Describe your project and we will come back with questions and a plan
No commitment. The more detail, the more accurate the first estimate.
- A short description of the goal and users is enough to start
- We reply with clarifying questions and a proposed set of stages
Prefer email? info@flexisoft.pl