A clean score is not a working site
If you have run a scanner before, you know the feeling. Green ticks, a high number, done. Then someone using a screen reader emails to say they could not get past the menu.
The scanner was not lying. It stopped where it had to.
A machine can see that an image has alt text.
It cannot say whether the alt text is any use.
It can see a button exists.
It cannot say whether a keyboard user can reach it, or what a screen reader calls it.
WCAG 2.2 Level AA has 55 requirements. The engine behind this scan can decide 10 of them on its own. The other 45 are judgement calls. A score that covers the 10 is a score for 10 of 55, whatever number it prints.
My own site, audited, failures included
The best example I can show you is my own site, because I am not going to hide the failures.
On 31 August 2026 the scanner ran over alexandra-ciobanu.co.uk. On 3 September I checked the other 45 requirements by hand. Result: 26 meet, 9 fail, 1 needs review, 19 do not apply.
1.Logical focus orderLocks people outO.09 · 2.4.3 A · PersonTier 1
On desktop, several tab stops land on links that are not visible, most likely the mobile menu items still in the tab order at desktop width. Tested at 1280px. Hidden navigation needs removing from the tab order when it is not on screen, using display: none or the inert attribute rather than moving it off screen.
That's a focus order failure, the tab sequence includes things that aren't on the page.
No selector recorded
Three of the failures. A carousel that a screen reader never announces, so the listener hears one slide and has no idea there are more. A mobile menu, hidden on desktop, that still sits in the tab order, so keyboard focus lands on links nobody can see. Form fields with a placeholder and no label, so the moment you start typing, the field stops telling you what it is for.
The scanner found the first one. A person found the other two.
Read the full audit of my site
What the free scan does
Enter a page address. The scanner loads the page at desktop and phone widths, runs the engine over it, and writes up what it found. Each of the 55 requirements gets one of four results: meets, fails, needs review, or not applicable. Next to every result it says how that result was reached, so you can see which ones a machine decided and which ones it could not.
Every report has its own link, and anyone with the link can open it. Enter your email and I will send you a copy and the link. Either way, the scan is deleted 30 days after it runs.
What the audit adds
The audit covers the same 55 requirements. The difference is the 45 a machine cannot decide. I check those by hand, on your live page, following the W3C's WCAG-EM method, the one a formal evaluation uses.
In practice that means walking the page with a keyboard only. Reading it with a screen reader. Zooming to 200% and to 400% and watching what breaks. Reading every heading, label and link out of context. Then writing down, requirement by requirement, what I checked and what I found, with the fixes I would make first at the top.
Who is checking: I am Alexandra Ciobanu. I spent nearly a decade at Amazon, where I built the monthly accessibility audit system used across three organisations. I design and build sites myself, so the fix list is written by someone who has to live with fix lists.
- £1,500one page
- 5working days
- 55requirements
What you get:
- One page, every requirement, with a named auditor and a date
- Each result marked with the method used to reach it
- A fix list in order, worst first
- A re-check date one year on
- A live, accessible report, plus a PDF copy
What you do not get is a certificate. The report says what was checked and how. It does not say your site is compliant, because no honest audit of one page can.
£1,500 for one page, agreed before I start, delivered within 5 working days. More than one page: I quote those separately, and the price per page drops for every page after the first.
How each result is reached
| Method | Decides | Decided by |
|---|---|---|
| Automated engine at desktop and phone widths | 10 of 55 | Machine |
| Keyboard-only walk through the page | Focus, order, traps, visible focus | Person |
| Screen reader read-through | Names, roles, announcements, reading order | Person |
| Zoom to 200% and 400% | Reflow, clipping, text size | Person |
| Reading by hand | Alt text, labels, link text, headings, consistency | Person |