The day we discovered our website was lying to us
On 7 April 2026 we corrected the way ImpactMojo's automatic accessibility tests reported their results. We expected nothing visible to happen. Instead, the correction showed 393 accessibility violations on the 13 pages one of our scanners tests, which had been there since the tests were set up.
Every change we made before that correction had been passing its accessibility tests. Every report said "all green". But the two scanners we use, axe-core and pa11y-ci, had been finding failures all along, and a small mistake in the step that read their results recorded every failure as a pass.
A change of a few characters exposed hundreds of hidden errors. This is the story of what we found, what we fixed, and what we learned about the gap between "technically accessible" and "actually accessible."
What WCAG 2.1 AA actually means
The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA are the W3C standard for web accessibility. Level AA is the target we hold ourselves to. It is the floor: the minimum that lets people with low vision, dyslexia, motor impairments, screen readers, and many other conditions actually use a website. It is also what most government partnerships, UN agencies, and educational institutions require their digital partners to meet. Our own accessibility statement commits to it.
The rules are concrete. Text must have a contrast ratio of at least 4.5:1 against its background, or 3:1 for large text (Success Criterion 1.4.3). Every form field needs a label. Every interactive element needs a name that screen readers can announce. Colour must not be the only thing that sets a link apart from the text around it (1.4.1). Heading levels should not skip, and a link to an #anchor should land on an element that exists. Scanners flag both, although they are best practice more than strict pass-or-fail criteria.
None of this is glamorous. The World Health Organization estimates that 1.3 billion people, 16 percent of the world's population, live with a significant disability. Not every one of them meets barriers on the web, and for those who do, these rules decide whether a website includes them.
From 393 errors to zero, pass by pass
Once the tests reported correctly, we started working through the errors. This was the trajectory, pass by pass, in one working session.
- Pass 1 (393 → 77 errors): One colour change on the dataverse page's "Visit" button, plus colour-token bumps on three other pages. The button was sky-500 with white text, a contrast ratio of 2.77:1, well below the 4.5:1 floor. There were roughly 260 cards on the page, so that single change cleared 271 errors in one shot.
- Pass 2 (77 → 21): Form fields without labels, buttons and search boxes inside pop-up windows with no name a screen reader could announce, and a handful of contrast fixes.
- Pass 3 (21 → 14): The theme switcher's default was inverted. A test browser has no colour preference set, and our pages read that as a request for dark mode, so every test ran against the dark theme. We corrected this on forty-one pages. That left buttons with gradient backgrounds, which the scanner could not read and scored as white text on white. In pass 4 we gave twenty-seven of them a plain background colour as well.
- Pass 4 (14 → 1): Two styling faults. In four stylesheets a rule meant for the dark theme also applied to the light one, so light pages were given dark-theme colours. Separating them removed most of what was left, and the plain background colours from pass 3 had to be moved so that they took effect.
- Pass 5 (1 → 0): A single text colour on a contact button. Done.
Five passes, roughly four hours of focused work, took the count from 393 errors to zero on all thirteen pages our scanner tests.
The five lessons that travel
1. Your tests may be reporting a pass that is false
The deepest bug was in the checking itself. For weeks we had been adding features and shipping pull requests while believing our accessibility tests were passing. The mistake was a few characters long and easy to miss when someone read the code. Telling a team to be more careful would not have caught it. Assuming that a passing test might be wrong, and checking that it fails when it should, would have. We now do that: a deliberate violation is put in front of the tests to confirm they catch it.
2. Most accessibility bugs are caused by a small number of root causes
When you see "393 violations," it sounds like a project. But 271 of those came from one colour on one button class, repeated across roughly 260 cards on a single page. Most of the rest traced to a handful of shared causes: brand colours used as text, unlabelled form fields, an inverted theme default and a selector bug. The work was to find those five patterns, and the 393 followed from them.
Automated scans earn their place by clustering errors so that the patterns show, even though they miss plenty (see below).
3. Brand colours and accessibility are in tension, and it takes design work to resolve it
Our brand uses sky-500 (#0EA5E9) prominently. White text on a sky-500 button gives 2.77:1, and so does sky-500 text on a white background, because the ratio is the same in both directions. Both fail WCAG AA. So do indigo-500 (4.47:1 as text, just under the line), emerald-500 (2.54:1) and amber-500 (2.15:1). These are the default bright choices in almost every modern design system, including Tailwind, Material, and Ant Design.
Keep the brand and define two versions of every brand colour: a "decorative" version (used for backgrounds, borders, focus rings, icons) and a "text" version that is two or three steps darker on the same hue. Sky-500 stays for the gradient backgrounds; sky-800 (#075985) takes over for any sky-coloured text. Indigo-500 stays for fills and borders; indigo-700 (#4338CA) is the indigo text. And so on.
This is design work, and it belongs in your design system before the code is written. Retrofitting it across an existing site is exactly the kind of slow, mechanical work we just spent four hours on.
4. Automated tests miss things, but they miss less than you think
Teams sometimes defend skipping automated tests by saying "automated tests can't catch everything, so we rely on human review." The first half of that sentence is true. It makes a case for adding human review alongside the scans.
Automated tools like axe-core and pa11y find a large share of accessibility issues and miss the rest. In the UK Government Digital Service's 2017 test, single tools found between 17 and 41 percent of the 143 barriers planted on a deliberately inaccessible page, and 29 percent were missed by every tool. Deque's 2021 analysis of more than 13,000 pages found that its axe tools covered 57 percent of issues by volume. They are excellent at colour contrast, missing labels, broken anchor targets, ARIA misuse, heading hierarchy, and structural issues. They are bad at the things humans are good at: whether the page makes sense when read top-to-bottom by a screen reader, whether the keyboard focus order matches the visual order, whether interactive widgets are operable without a mouse, whether form errors are announced when they appear.
You need both. Automated tests catch the high-volume mechanical issues so that human review can focus on the things that require judgement. A team that skips them has the same bugs and finds fewer of them.
5. Most users will never notice the bugs you are fixing
Here is the plain version. Most ImpactMojo users have normal vision, modern devices, and good lighting. They will see no visual difference between sky-500 text and sky-800 text, and they will never know we changed anything. Does that mean the work was unnecessary?
No. The work is for the people who do notice. Older users whose contrast sensitivity has declined. Users with low vision or colour blindness. Users on cracked phone screens or in bright sunlight. Users with screen readers who cannot use a form field that has no label. Users with motor impairments who cannot click a button that has no accessible name. These users were always there. They were just unable to use the parts of our site we never tested.
We work in development education, in a region where many of our users are older, on shared devices, on slower connections, with regional-language screen readers. The accessibility floor is not optional for us. It is what allows the site to reach the audience we say we serve. Our accessibility statement says a platform that cannot be used by people with disabilities is not actually free.
What to do if you are starting from scratch
If you are about to build a website, or you are auditing one for the first time, here is the shortest path we know:
- Pick a contrast checker before you pick a colour palette. The WebAIM Contrast Checker is free and definitive, and applies the WCAG contrast formula. Test every text-on-background combination in your design system before you ship. If you cannot get to 4.5:1 with a brand colour as text, define a darker variant for text use.
- Run axe-core or pa11y on at least your top five pages, on every pull request. Make the test fail the build if a serious violation is introduced. This is one afternoon of CI setup that pays for itself within weeks.
- Verify your CI actually fails when it should. Push a test commit with a deliberately broken contrast ratio. If your build still says green, your test pipeline is lying to you. Fix that first.
- Label every form field. Use a real
<label for="...">element, or anaria-labelattribute, or both. A placeholder is not a label. Your screen-reader users will thank you, and your search-engine ranking will improve. - Make every anchor link point to something that exists. If your jump nav points to
#data-technology, make sure there is an element withid="data-technology"on the page. If the target is rendered by JavaScript, add a static placeholder so it exists at load time. - Test in a screen reader at least once. Mac users can turn on VoiceOver with Cmd+F5. It will be uncomfortable. That is the point: the people who depend on a screen reader cannot switch it off.
The hardest part of accessible web development
The tools are free, the rules are published and the tension between brand and contrast can be settled in a design system. The hardest part is the discipline of treating accessibility as a continuous concern after the first audit is done.
Every new feature can introduce a new violation. Every JavaScript widget that injects content into the page is a potential source of unlabelled inputs, missing names, and unreachable anchors. Every brand colour update can knock a critical text element below the contrast threshold. Without automatic tests that catch these regressions immediately, even the best-intentioned team will gradually drift back into inaccessibility.
What we fixed in April included the tests themselves, which now stop a change carrying a serious violation from going live. The 393 errors had built up over a year. The work now is to keep the tests honest.
"Accessibility is the floor that lets your features reach everyone."
What we shipped, in numbers
- Two faults in our accessibility tests that had been hiding failures were fixed.
- A fault in the theme switcher that put tests into dark mode was fixed on 41 pages and 27 blog posts.
- Four stylesheets that gave the light theme dark-theme colours were corrected.
- Twenty-seven gradient buttons across three pages were given a plain background colour so their contrast could be measured.
- Fourteen form fields, five of them search boxes inside pop-up windows, were given names a screen reader can announce.
- Twenty-three places where a bright brand colour was used for text were changed to a darker shade of the same colour that meets WCAG AA.
- Three tools from other providers (the site tour, UserWay and Google Translate) were left out of the automatic tests, because we cannot change their code.
- When the work finished, all 13 pages tested by one scanner and all 5 tested by the other passed with no serious violations. Today every page on the site is tested each day, in both colour themes.
If you take one thing away from this post
It is that accessibility is a property of your development process. If your process catches violations the moment they are introduced, you stay accessible. If it does not, you drift. There is no in-between, and there is no "we'll get to it later" that actually happens.
Set up the tests. Check that they fail when they should. Then trust them. The roughly one in six of your users who need it will never write you a bug report. They will just stop visiting. The work to keep them is small if you do it continuously, and impossible if you do not.
If you are a development organisation building digital tools for the people you serve, this is the bare minimum, because the people you say you serve deserve to be able to use what you build.
Accessibility in development work goes beyond websites. Our free Disability Inclusion 101 deck covers the wider practice of building programmes that disabled people can actually use.