We were told our site must meet WCAG, but we don't know where to start
We test against WCAG 2.2 level AA, the level most laws and tenders refer to. Every issue in the report has a description, a location, a severity and a fix.
WCAG 2.2 accessibility audit: a site everyone can actually use
We test your site the way people with visual, hearing, motor and cognitive disabilities use it. You get a report that says what is broken, how serious it is and how to fix it.
Quote and schedule after your brief
Who it's for
- Companies selling in the EU, UK, US, Canada or Australia that need to meet accessibility rules
- Online stores and services with booking, payment or sign-up
- Site owners who received a complaint, a legal letter or a procurement requirement
- Teams building a new site who want accessibility designed in from the start
Problems we solve
A free scanner shows green, yet we still get complaints
Automated tools catch only part of the problems. We find the rest by hand: key flows with a keyboard only, with a screen reader and with browser zoom.
Our developer says "we'll fix it" but doesn't know what exactly
We write tickets developers can act on: the element, an example of correct markup and a criterion to verify the fix. We can implement the fixes or hand them to your team.
We worry it will break again with the next release
We add a short accessibility checklist for new pages and components, to be used by your designer, developer and content editor.
What's included
- Automated scans with axe, Lighthouse and WAVE
- Manual keyboard testing: tab order, visible focus, no keyboard traps
- Screen reader checks with NVDA and VoiceOver on key pages
- Checks for colour contrast, target size, zoom up to four times and reflow without loss of content
- Form review: labels, error messages, autocomplete, accessible CAPTCHA alternatives
- Video and audio review: captions, transcripts, playback controls
- Checks for the criteria new in WCAG 2.2: target size, dragging alternatives, consistent help, redundant entry
- Report with severity for each issue and rough effort to fix
- Draft accessibility statement for your site
- Re-test after fixes, if included in your package
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Express
A landing page or small site with up to 5 page types
- Automated scan plus manual review of key pages
- Keyboard and screen reader testing
- Prioritized report
- 30-minute call to walk through results
02
Standard
A corporate site, store or web app with forms and payment
- All key flows: search, cart, checkout, sign-up
- Desktop and mobile testing
- Detailed report with developer-ready tickets
- Draft accessibility statement
- Re-test after fixes
03
Audit and remediation
Teams without an in-house developer, or those who want one vendor to close the issue
- Everything in Standard
- Fixes for critical and serious issues in code and design
- Accessibility checklist for your team
- Final test and updated report
- Staged payment: audit first, then fixes
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
Automated pass
We run scanners across every page type and collect the obvious issues: contrast, missing labels, markup errors.
Manual testing
We walk through your main flows with a keyboard, a screen reader and zoom. This is where we find what scanners miss.
Report and walkthrough
You get the report and we explain it on a call. Together we decide what to fix first.
Fixes and re-test
We fix the issues ourselves or review your developer's work. Then we re-test and update the report.
Scope and limits
- We don't issue a legal certificate of compliance or guarantee protection from complaints or lawsuits. That is a question for your lawyer; we provide the technical evidence
- We don't promise full AAA conformance. The default target is level AA
- We don't replace testing with real users with disabilities. We can recommend it, but it is a separate paid service
FAQ
What is WCAG 2.2 and is it mandatory?
WCAG (Web Content Accessibility Guidelines) is the international standard for web accessibility. Whether it is mandatory depends on your market and sector. The EU, UK, US, Canada and Australia all have rules or procurement requirements that refer to it. Check your exact obligations with a lawyer.
Why is a manual audit better than an automated scanner?
Scanners find formal errors fast but don't understand meaning. They won't tell you that the tab order is confusing or that an error message is never announced. We combine both approaches.
What do you need from us?
The site URL and, for restricted areas, a test account. For a store or service, test data to go through checkout without a real payment. It also helps to know which markets you sell in.
Will you fix the issues too?
Yes, in the Audit and remediation package. In the other two we hand tickets to your team and can review the result. Your accounts, files and code stay yours under the agreed terms.
Will an accessible site bring more customers?
We don't promise a specific increase. But clear forms, visible focus and readable text help every visitor, including people on phones or in bright light. Such a site is also easier to connect to a CRM and automations.
How do you estimate the cost?
We prepare a quote after reviewing your brief and requirements. A first stage can cover: automated scan plus manual review of key pages; Keyboard and screen reader testing. Scope, payment and schedule are agreed before work starts.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.