Case study
A builder's website, from 65.4 to 100
A regional construction company's WordPress site, tested against WCAG 2.2 Level A and AA, fixed at the source, and tested again. The company isn't named here; the numbers are real.
The result
One remediation pass took the site's Accessibility index from 65.4 to 100. Every issue the baseline found was fixed, and the re-test found nothing new.
The site
A typical small-business WordPress site
Nothing unusual, which is the point: most small-business sites are built the same way and break in the same places.
WordPress and a page builder
A custom theme with Elementor templates for the header, footer and pages.
Carousels and galleries
Project photo sliders, a testimonial carousel and a gallery, each from a different plugin.
Two forms
A contact form protected by reCAPTCHA, and a sidebar form from another plugin.
Desktop and phone
Nine pages at two screen sizes, plus five interactive states: the phone menu opened, carousels advanced, form errors shown and a team card flipped.
The baseline
What the first scan found
An index of 65.4: 37 issues (9 critical, 20 serious, 6 moderate and 2 minor), 14 WCAG criteria failing and one partly met. Another 116 alerts needed a person to judge them.
- Controls with no name. The logo links in the header and footer and the carousel arrows and dots read as just "link" or "button" to a screen reader.
- Low contrast. Menu links, buttons, headings and testimonial text too faint to read comfortably.
- Carousels that wouldn't stop. Sliders moved on their own with no way to pause them, and their slides took keyboard focus without doing anything.
- Getting around. No way to skip past the header, headings that didn't describe the page, a hidden link that took focus, and a form that jumped ahead in the tab order.
- Forms. Contact fields with no visible labels or required markers, and nothing telling the browser what personal data each field collects.
- Images and small targets. Photos with no description, and dots and icons too small to tap reliably.
The fix
Fixed at the source, not page by page
Each issue was traced to the template, widget, theme file or plugin setting that caused it, so one change cleared it everywhere it appeared.
- Theme and templates. Names for every link and button, a skip link, a proper heading outline, visible focus, and contrast brought up to at least 4.5 to 1.
- Carousels. Pause controls, arrows and dots that announce what they do, and slides that no longer take focus.
- Forms. Visible labels, required markers, the right autocomplete hints, and errors a screen reader announces.
- Content. Each of 58 project photos got its own description, approved by the owner, and a public accessibility statement went up with links from every footer.
No overlay widget, no toolbar: the pages themselves were corrected.
The proof
How we know it worked
Re-scanned
The same pages, sizes and states, with the same pinned engine versions, so the before and after compare like for like.
Compared
The before-and-after report lists all 37 issues as fixed, none remaining and none new.
Re-tested by a person
Keyboard, zoom and reflow re-checked, and every page heard through NVDA, a screen reader. The 116 alerts were each fixed or checked by hand.
Checked live
After the fixes went to the live site, a scan of the live pages matched the test copy. A WAVE check then raised a few more items, such as photos sharing one description; those were fixed too, and Audsey now checks for them.
See the deliverables
The report and the fix sheet, anonymized
These are this project's real documents, with the company, people, places and clients replaced by made-up names.
- Before-and-after report (PDF, 37 pages, 0.9 MB): what the owner and their managers read. Index, criteria, issues fixed and how everything was tested.
- Developer fix sheet (PDF, 51 pages, 1.4 MB): the work list from the baseline. Each issue in priority order, where it comes from in WordPress, the fix, every affected element and how to confirm it.
An Accessibility index of 100 means every WCAG criterion we tested was met on these pages on the date tested. It isn't a compliance percentage, a certification or a legal opinion.
What would your baseline show?
Tell us about your site and we'll show you what a first report would cover.