Accessibility testing services
Accessibility testing checks whether people with disabilities can use your product: somebody navigating by keyboard alone, somebody listening to a screen reader, somebody who cannot tell two colours apart. We test against WCAG 2.2 AA, which also covers 2.1 AA, the level EN 301 549 and the European Accessibility Act reference. People and assistive technology do the parts a checker cannot, and we give you the documents a buyer or a regulator will ask for.
We are an independent testing company. We have tested other people's software since 2018, we did not write yours, and we have no reason to call a failure a pass. 50+ engineers, in Cluj-Napoca, Romania.
Two weeks, free if you are not happy with what we deliver. We invoice from week three.
Who this is for
- You sell into the EU. The European Accessibility Act has applied since 28 June 2025, and many digital products and services sold to consumers in the EU now have to meet it. You need to know where yours stands.
- A customer or a tender is asking for a VPAT. Public sector and large enterprise buyers often want an accessibility conformance report before they sign. You need one that says what is true.
- You ran an automated checker and it gave you a score. You are not sure what the score means, or whether a screen reader user could actually get through your checkout.
- You are about to redesign. It is far cheaper to test the new design system once than to fix every page built on it afterwards.
- You need an accessibility specialist for a few weeks, not a hire. A specialist can join your account for a fortnight without us recruiting for it.
What we test, and how
We start with the journeys that matter: sign-up, log-in, search, checkout, the forms people have to complete. Testing every page of a large site to the same depth costs a lot and tells you the same thing many times. Testing the journeys properly tells you whether a person can do what they came to do.
Then three layers:
Automated checks. Scanners find the mechanical problems fast: missing text alternatives, contrast failures, form fields with no label, broken heading structure. They are worth running, and they cannot tell you whether the page makes sense to somebody who cannot see it. Auditi, the tool we built, does this mechanical half and keeps the findings in one place.
Keyboard and focus. Every journey done without a mouse. Can you reach every control, is it obvious where you are, and does focus go somewhere sensible when a dialog opens and closes?
Screen readers. The journeys done again, listening. Are buttons announced as what they do, do errors get read out when a form fails, does a dynamic update tell anyone that something changed?
Every finding is mapped to the WCAG success criterion it fails and its conformance level, with where it happens and how to reproduce it.
What you get at the end
- A findings report your developers can work from. Each issue with its WCAG criterion, severity, location, how to reproduce it, and a fix at code level.
- An order to fix things in. The failures that stop someone completing a journey come first, cosmetic ones last.
- A VPAT. The accessibility conformance report procurement teams ask for, filled in from what we actually found rather than from what the product is supposed to do.
- A way to keep it fixed. Automated accessibility checks added to your pipeline where it makes sense, so a regression is caught in the pull request rather than in the next audit.
When an engagement ends, you keep the reports, the documentation and the tooling configuration.
What it costs
$25 to $45 an hour.
The rate moves with the seniority of the engineer, how long you commit for, and the mix of manual, automation and specialist work. Accessibility auditing sits in the specialist part of that mix. Longer commitments move down the range. Auditi comes with the engagement, with no separate licence cost.
We start the same way on every engagement. Two weeks, free if you are not happy with what we deliver. We invoice from week three.
When we are not the right answer
We would rather say this here than on the third call.
If you want a legal opinion. We tell you where your product fails WCAG and how to fix it. Whether that meets a particular law in a particular country is a question for your lawyer, and we will not pretend otherwise.
Where the contract requires staff on site, or nationals only. We are in Romania and work remotely, so that is a straight no.
If you want a certificate that says you are compliant. There is no such certificate for WCAG, and a report that promises one is not worth having. We will give you an honest account of where you stand.
Why us
We are independent. We did not design or build your product, so we have no reason to mark our own work as passing.
We built our own tooling for it. Auditi audits against WCAG, and also GDPR and FDA requirements. We built it because the off-the-shelf versions did not keep up with us, and it comes with the engagement.
Four ISO certificates, all current to 05.12.2027: ISO 9001:2015, ISO/IEC 27001:2022, ISO 13485:2016 and ISO 14001:2015. 13485 matters if your product is medical: device manufacturers' own quality systems have to account for who tests their software. We send the certificates with their scope statement.
A NATO procurement agreement. The NATO NCIA Basic Ordering Agreement, NCAGE 1JGAL. A signed ordering agreement, not a certification and not a clearance.
4.9 on Clutch, from more than 65 reviews. Written by clients, not by us.
Common questions
Which version of WCAG do you test against?
WCAG 2.2 AA, which also covers 2.1 AA, the level EN 301 549 and the European Accessibility Act reference. If your contract names something else, tell us on the first call.
Can an automated tool do this on its own?
No. It finds the mechanical problems and misses whether the product works for a person using a keyboard or a screen reader. We use both.
Do you produce a VPAT?
Yes. It is written from the findings, so it describes the product as it is.
Can you check our fixes?
Yes. Retests are billed at the same hourly rate as any other testing time.
How long does it take?
About two weeks to have an engineer working on your product. The audit itself depends on how many journeys are in scope; we agree that with you on the first call.
How do you handle our data?
NDAs, and the handling is covered by our ISO 27001 management system. For a regulated product, ask for the scope statement rather than the certificate.
Talk to us
Tell us what the product is, who buys it and what deadline you are facing. We will tell you which journeys we would test first, and if an automated checker and a few fixes would get you where you need to be, we will tell you that instead.