A form may pass basic automated checks while still being difficult to complete with a screen reader. A checkout may look correct but trap keyboard focus. A customer area may be invisible to a public crawler. Expert testing examines the experience behind the scan.
Understand what blocks users, not just which rules have been flagged or which WCAG criteria haven't been met.
Discover barriers across pages, components, applications and real user tasks.
Receive documented issues with affected locations, user impact and recommended next steps, based on the agreed audit scope.
Give design, engineering and compliance teams a shared basis for prioritizing remediation.
From public websites to logged-in dashboards, mobile applications and downloadable documents, choose focused testing or a broader expert assessment. The right scope depends on your digital product, risks and priorities.
Websites
What we do: Experts review a representative scope of website pages and interactions against applicable WCAG success criteria, combining automated checks with manual inspection.
What you get: A findings report organized by page, issue, applicable criteria, severity and recommended remediation.
Why it matters: Understand the accessibility baseline and prioritize website improvements.
What we do: Specialists inspect keyboard operation, focus order, semantic structure, forms, error handling, text alternatives and dynamic content that software cannot fully interpret.
What you get: A manual test log with reproducible findings, evidence and code/design guidance.
Why it matters: Catch contextual barriers that automated scanners miss.
What we do: Using approved test accounts and a secure agreed test environment, the team checks customer portals, dashboards, checkout accounts and role-based pages that public crawlers cannot access.
What you get: An inventory of tested authenticated states, detected issues, evidence and recommended fixes.
Why it matters: Uncover barriers in high-value experiences visible only after login.
What we do: Assess route updates, asynchronous validation, notifications, live regions, overlays and state changes in dynamic web applications.
What you get: Interaction-state matrix with focus, announcement and keyboard defects.
Why it matters: Catch accessibility failures in highly interactive applications.
What we do: Map observed issues against the agreed technical reference such as WCAG 2.2, relevant EN 301 549 provisions and applicable sector/regional obligations, without substituting legal advice.
What you get: Criteria-mapped gap register, assumptions and documented exclusions.
Why it matters: Help stakeholders understand evidence gaps and plan next steps for compliance work.
Example: an automated scan and a manual audit on the same online shop.
Checks one page at a time
4 issues found on 1 page
Places an order from start to finish
4 issues that stop a blind customer from ordering
All four checkout problems passed the automated scan.
Automated rules are still worth running. In a study of more than 2,000 audits, Deque found that its automated tests covered 57% of issues by volume (Deque, 2021, opens in a new tab). The rest needs human judgment. Those are often the issues that stop a purchase or a request.
Start with a free scan in the Wawsome Accessibility Checker. Then book a manual audit for the tasks that matter most to your business.
Real journeys
What we do: Test complete tasks such as register, sign in, search, select, book, pay, upload documents or recover an account using keyboard and assistive technology.
What you get: Journey maps, failed steps, impact descriptions and a prioritized list of blockers.
Why it matters: Protect critical conversions and digital self-service completion.
What we do: Participants with relevant lived experience perform agreed realistic tasks, with accessible consent and moderated or unmoderated research protocols.
What you get: Usability observations, task completion evidence, participant feedback and prioritized improvements, with privacy safeguards.
Why it matters: See where real users encounter barriers that compliance checks alone can overlook.
What we do: Test product discovery, variation selection, cart, promotions, checkout, payment errors and order confirmation across agreed assistive scenarios.
What you get: Conversion-journey audit with blocking issues, severity and suggested fixes.
Why it matters: Reduce avoidable purchase friction for shoppers using assistive technology.
What we do: Inspect account creation, login, multifactor prompts, error recovery, CAPTCHA alternatives, consent flows and data-entry forms.
What you get: State-by-state test cases and an ordered remediation backlog.
Why it matters: Help customers complete essential forms and secure actions independently.
What we do: Test agreed browsers/devices with screen readers, keyboard-only navigation, magnification and relevant accessibility settings.
What you get: A compatibility matrix covering scenarios, test conditions, barriers and recommended solutions.
Why it matters: Verify whether experiences work with tools people actually use.
Tab, Shift+Tab, Enter, Space and the arrow keys. We check that every control works and that focus stays visible.
Screen readers on Windows. We listen to what each element announces and in what order.
The screen reader on macOS and iOS, tested with gestures and with a keyboard.
The screen reader on Android, tested on real phones.
Refreshable braille for people who read by touch. We check that text, labels and states come through correctly.
Text at 200% and the page at 400% zoom, down to 320 pixels wide, with no lost content.
Example: VoiceOver reading order, touch target sizes and screen rotation.
Apps & documents
What we do: Review native or hybrid app screens, navigation, gestures, screen-reader announcements, dynamic states and platform accessibility behavior on iOS and/or Android.
What you get: Platform-specific issue reports, annotated evidence and remediation recommendations.
Why it matters: Improve accessibility across mobile experiences and reduce device-specific user friction.
What we do: Inspect reusable UI elements such as modals, dropdowns, date pickers, tabs, carousels, tables, alerts and custom controls across their states.
What you get: A component-level defect log with expected accessible behavior, reproduction steps and recommendations.
Why it matters: Fix repeated accessibility issues at the source rather than page by page.
What we do: Evaluate selected PDFs and office documents for reading order, tag structure, headings, tables, text alternatives, forms and assistive-technology usability.
What you get: A document-by-document findings register and recommended remediation actions.
Why it matters: Make contracts, statements, reports and downloadable materials more usable.
The five parts of the EU model statement for public sector websites and apps.
Design & follow-up
What we do: Review the available audit evidence, service scope, accessibility status, known limitations and contact mechanism to draft or update a relevant accessibility statement.
What you get: A tailored draft accessibility statement, with clearly identified inputs requiring owner/legal approval.
Why it matters: Communicate accessibility information transparently and support relevant disclosure duties.
You can generate and host your statement from the Wawsome dashboard. See the Wawsome accessibility statement as an example.
What we do: Review selected interface designs, content patterns and interaction specifications before development for contrast, hierarchy, focus order, form labeling and accessible states.
What you get: Annotated design review, accessibility acceptance criteria and developer handoff notes.
Why it matters: Prevent costly accessibility issues earlier in the product lifecycle.
What we do: Translate prioritized findings into concrete design, content and code-level approaches in collaborative sessions with the delivery team.
What you get: Remediation recommendations, annotated tickets and agreed Q&A decisions.
Why it matters: Shorten ambiguity between discovery and implementation.
What we do: Recheck agreed issues following fixes and test selected high-risk paths for regressions after releases.
What you get: Verification results marked resolved, partially resolved or still open, with remaining evidence.
Why it matters: Confirm whether remediation worked and detect recurring defects.
What we do: Set an agreed cadence to rescan selected pages, review important releases and escalate newly detected or reintroduced issues.
What you get: Periodic status summaries, trend comparisons and a prioritized follow-up list.
Why it matters: Help maintain accessibility as content and features change.
Illustration, not real data. Open issues drop after the audit and rise three times when new content goes live. Each time, monitoring sends an alert and the team fixes them.
Learn more about the Wawsome Accessibility Monitor.
What we do: Deliver focused reviews or workshops for product, content, QA and engineering teams based on audit findings.
What you get: Team guidance, examples, workflow suggestions and review checklists.
Why it matters: Build capability to prevent repeat issues.
We agree which pages, user roles, devices, flows, standards and deliverables are in scope.
Experts perform the applicable automated, manual and assistive-technology checks; user testing is included only when agreed.
You receive documented barriers, practical recommendations and an explanation of priorities.
We walk through remediation options, ownership and whether retesting or ongoing monitoring is appropriate.
Depending on the agreed scope, findings can include the affected page or component, steps to reproduce, observed versus expected behavior, referenced WCAG criterion, affected user tasks, issue priority and suggested remediation.
WCAG criterion
2.4.3 Focus Order (Level A)
Issue
Keyboard focus moves behind a checkout modal.
Impact
CriticalUsers navigating without a mouse may not be able to complete payment.
How to reproduce
Open the payment dialog with the keyboard, then press Tab.
Suggested next step
Manage focus on dialog open, close and keyboard interaction.
Status
Fixed and retested
Illustrative example of one finding from an audit report.
Testing scope can be mapped to WCAG 2.2 success criteria and relevant EN 301 549 requirements. For organizations subject to the European Accessibility Act and national implementing laws, technical test results can inform compliance planning. An audit alone does not establish legal compliance or guarantee that every issue has been found.
W3C guidance on why tools alone are not enough and how to combine testing methods.
Directive (EU) 2019/882 and the products and services it covers.
Turn findings into a practical engineering backlog with reproducible issues and clear acceptance criteria.
Find friction in product discovery, checkout and account flows that can prevent customers from completing transactions.
Document observed accessibility gaps and maintain clearer evidence for internal assessment and next steps.
Assess product accessibility evidence and prioritize improvements requested during vendor selection.
Tell us what you want to evaluate. We'll help define an appropriate assessment scope, from one critical flow to a broader accessibility audit.
Last updated October 16, 2026
Share the digital experience you want to assess and your most important goal. A Wawsome expert can help shape the right testing scope and explain the next steps.