Accessibility audit report: from identified issues to a clear remediation plan
Find out where accessibility barriers occur on your website, in your mobile app and across complete user journeys. Wawsome combines automated checks with manual testing by experts and turns the results into a report with prioritized issues, technical recommendations and implementation steps.
- Hybrid testing
- Accessibility experts
- Page and journey analysis
- Actionable recommendations
See what the report includes before you define the audit scope. See the report structure
A scan result shows you part of the problem. An audit shows you what needs to change.
The audit examines both individual elements and the ability to complete tasks from start to finish.
Example 1
A form can have a seemingly correct structure yet be impossible to complete using only a keyboard.
Example 2
A login error may not be announced by the screen reader.
Example 3
A payment can fail when the user switches between the website and the mobile app.
What is a digital accessibility audit and why do you need it?
A digital accessibility audit is a structured evaluation of selected pages, components, documents, applications and interactions to identify barriers that may prevent people with disabilities from using digital services. The audit can map technical findings to WCAG criteria and applicable requirements, within the limits of the agreed scope.
Without a verifiable diagnosis, teams may invest in changes with little impact, while the issues that block login, purchase or use of the service remain unresolved. The report creates a common basis for prioritization, budget, responsibilities and progress monitoring.
Looking for a specific type of testing? See all our accessibility audit and testing services.
For users
Identify real obstacles in navigation, form completion, authentication and transactions.
For teams
Turn observations into tickets and recommendations that design, QA and development teams can understand and plan.
For the business
Prioritize the journeys that matter most for conversion, self-service and customer relationships.
Audit methodology: automation, human analysis and end-to-end experience testing
Define the scope
Together, we define the platforms, user profiles, test environments, critical functionality, usage scenarios and technical references, including the relevant WCAG criteria. We explicitly document what is and isn't included in the sample.
Automated testing
We use automated tools to flag issues that can be detected by rules, such as certain structural errors, label associations and contrast aspects. Experts analyze and interpret the results to avoid unjustified conclusions.
You can try this part yourself with the free Wawsome Accessibility Checker.
Manual testing
Experts check keyboard use, focus order and visibility, screen reader behavior, forms, error messages, interactive elements and dynamic states in the scenarios included in the audit.
Journey testing
We check whether a user can complete a task from start to finish, including transitions between pages, sessions, devices and applications, under the agreed test conditions.
Synthesis and reporting
We validate the findings, consolidate recurring issues and document the evidence, impact, severity, estimated remediation complexity and recommendations, so you can build an action plan.
What do experts check during an accessibility audit?
Pages and components
What we check: Semantic structure, navigation, buttons, modals, menus, forms, displayed data and the behavior of elements in different states.
Deliverable: An inventory of issues at page or component level.
User journeys
What we check: Registration, login, account recovery, search, purchase, payment, requests and contracting processes.
Deliverable: Issues reported at the exact points where the user gets blocked.
Web and mobile platforms
What we check: Websites, web applications, authenticated portals and iOS/Android mobile apps, on the agreed versions and devices.
Deliverable: Findings separated by platform and by test scenario.
Assistive technologies
What we check: Interaction in agreed scenarios with screen readers, keyboard navigation and relevant accessibility settings.
Deliverable: Evidence of how the experience actually works for users.
Documents and interfaces
What we check: PDF documents or other files included in the scope, their structure, reading order, forms and interactive elements.
Deliverable: Remediation recommendations for the selected documents.
Technical conformance
What we check: Mapping observations to the relevant WCAG criteria and, if requested, to applicable EN 301 549 requirements.
Deliverable: A findings matrix with references to the technical criteria.
One customer process. Several applications. One audit of the entire experience.
Illustrative example: a customer starts the contracting process on the website, continues with identity verification on their phone and completes the process in a mobile app. The audit checks whether the user can navigate, understand the instructions, switch devices, enter and validate data and complete the process without accessibility barriers.
Website
Filling in the application and starting the contracting process. We check forms, messages, navigation, progress and the accessibility of the transition to the next step.
Checkpoint: transition to the next step
Phone / identity verification
Switching to the mobile device, opening the instructions and completing identity verification through the permitted flows.
Possible blocker: switching devices
Mobile app
Returning after validation, understanding the status of the process and completing the action in the app.
Checkpoint: process status is clear
In the report, we identify not only where the errors are, but also at what point the journey breaks, which users may be affected and what the remediation options are. For platforms operated by third parties, testing depends on the access and agreements available.
What does the Wawsome accessibility audit report include?
Finding #07Illustrative example
Location
Contracting flow, step 3: “Continue” button
Steps to reproduce
Fill in the form using only the keyboard, then press Tab to reach “Continue”.
Observed result
The button cannot be reached or activated with the keyboard.
Expected behavior
The button receives visible focus and can be activated with Enter or Space.
WCAG criterion
2.1.1 Keyboard (Level A)
Severity and impact
Critical Blocks completion of the contracting flow for keyboard and screen reader users.
Remediation complexity
Low
Recommended solution
Use a native button element, or add keyboard support and a visible focus style.
Executive summary
The essential issues, the level of risk resulting from the sample and the main priorities for management.
Benefit: Management understands where intervention is needed.
Scope and test conditions
Platforms, pages, journeys, user types, devices, versions, assistive technologies and the standards used.
Benefit: Transparency about limits and reproducibility.
Issue inventory
For each finding: identifier, location, steps to reproduce, observed result and expected behavior.
Benefit: Teams can investigate and reproduce every issue.
Technical criteria
Mapping to the relevant WCAG criteria and, where applicable, to other technical requirements.
Benefit: A basis for technical review and conformance analysis.
Severity
A classification of technical seriousness and accessibility consequences, on a documented scale.
Benefit: Separates blocking issues from those with limited effect.
Impact
A reasoned estimate of the impact on users and on critical journeys, separate from the simple number of occurrences.
Benefit: Prioritization based on the effect on experience and operations.
Remediation complexity
An indicative estimate of effort (low, medium or high), later validated by the development team.
Benefit: Realistic planning of resources and dependencies.
Recommended solutions
Remediation directions at interface, content, code and behavior level, plus acceptance criteria where agreed.
Benefit: The move from diagnosis to implementation.
Remediation roadmap
Sequencing of initiatives, dependencies, proposed responsibilities and implementation order.
Benefit: A basis for backlog, budget and progress monitoring.
Limitations and re-evaluation
Aspects not covered, assumptions, results to be verified later and the recommended steps for retesting.
Benefit: Avoids a false impression of complete coverage.
What do we fix first? Prioritization by severity, impact and complexity.
Severity
How serious is the barrier from an accessibility point of view? An issue can make an action impossible, make it significantly harder or affect only part of the experience.
- Critical
- High
- Moderate
- Low
Impact
How important is the affected function and what are the consequences for the user? For example, an error in an essential login journey has a different impact than one on a rarely visited page.
Complexity
How much effort might the fix require: content, a component adjustment, an architecture change or a dependency on external vendors? The final estimate belongs to the team that implements it.
Recommended approach: barriers that block essential processes are addressed urgently; fixes with broad impact are then grouped together, and complex changes are planned according to their dependencies. Expert judgment is never replaced by an opaque formula.
| Low complexity | High complexity | |
|---|---|---|
| High impact | Fix first | Plan around dependencies |
| Low impact | Group with related fixes | Schedule and re-evaluate |
Prioritization exampleIllustrative example
Barrier
A “Continue” button in the contracting process that can’t be used with the keyboard.
Impact
Users cannot finish the journey, even though the issue appears only once.
Decision
High priority, because of its effect on completing the flow.
From report to execution: what happens after the audit?
Sessions with developers
We go through the findings together with your development, design and QA teams. We explain the issues, discuss solution options, clarify dependencies and, where relevant, the acceptance criteria for retesting.
Remediation roadmap
We build a roadmap for implementing the recommendations, based on the audit priorities, your operational goals and your team’s capacity. The roadmap can be revised as solutions are implemented.
Accessibility statement
Based on the available results, known limitations and the information provided by your organization, we can prepare a draft accessibility statement, subject to approval by its owner. The statement can be updated as progress is made and according to applicable obligations.
An accessibility statement is not a certification.
Re-audit
After implementation, we retest the agreed issues to verify whether the identified barriers have been fixed and whether regressions appear in critical journeys. The results are documented and can feed into the next iteration of the roadmap.
Between audits, the Wawsome Accessibility Monitor can flag new issues as your content changes.
Support during checks by authorities
On request and within the contracted services, our specialists can provide technical support during checks by authorities: explaining the methodology, the findings, the remediation steps and the evidence of the efforts made.
This support does not replace legal representation and does not guarantee the authority’s conclusions.
One report for multiple decisions: product, development, compliance and management
CTOs and development teams
Reproducible issues, technical recommendations, dependencies and a realistic order of intervention.
Product and UX/UI
The points where the user experience breaks and the interaction patterns that need to be corrected.
Compliance and legal
Documentation of the checks, limitations and progress, to support the analysis of applicable obligations, without claims of automatic certification.
Business and management
A clear picture of the barriers in essential processes and a framework for allocating resources.
Accessibility audits, WCAG and the European Accessibility Act: how are they connected?
EN 301 549
EN 301 549 is a European standard that sets accessibility requirements for ICT products and services in relevant contexts.
European Accessibility Act
The European Accessibility Act and applicable national legislation set obligations for certain categories of products and services.
An audit documents findings within the scope that was tested; on its own, it is not proof that all legal obligations are met. Depending on the technical scope, the evaluation can reference WCAG 2.2 and the W3C WCAG-EM evaluation methodology.
Do you have a website, an app or a complex digital process? We start with what needs to be checked.
You don’t need to know from the start which pages or standards to choose. In a needs-assessment call, we can define the priority journeys, the platforms involved and the format of results you need.
Why discuss your audit with Wawsome experts?
By combining automated testing with manual evaluation and journey analysis, our approach aims to identify barriers and translate them into recommendations for the teams that implement the improvements.
ISO 9001Quality management
ISO 27001Information security
IAAP certificationAccessibility expertise on our team
Sources
- W3C WAI: Evaluating web accessibility overview
- W3C: Website Accessibility Conformance Evaluation Methodology (WCAG-EM)
- W3C WAI: Evaluating conformance and reporting
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- EUR-Lex: Directive (EU) 2019/882, European Accessibility Act
Last updated October 21, 2026
Turn the audit into an action plan for digital accessibility
Tell us what you want to check: a website, a mobile app, an authenticated portal or a process that spans several platforms. A Wawsome expert can help you define the audit approach and the right deliverables.
You don’t need a complete inventory of issues. We can define together what is worth testing.