Web Accessibility Case Study

See how we turn failing audits into WCAG 2.2 AA results – real web accessibility case studies across WordPress, Shopify, Magento, BigCommerce and mobile apps.

Real projects · Real results

Each web accessibility case study below shows how a real website or app went from a failing audit to WCAG 2.2 AA – the barriers we found, the fixes we made and the final result, across WordPress, Shopify, Magento, BigCommerce and mobile apps.

How we work

What every web accessibility case study covers

Every web accessibility case study here follows the same path: a full audit of your live website or app, a fix for each barrier, and a final test that records the WCAG 2.2 Level AA result.

Platform and scope

Audit, remediation or both – on WordPress, Shopify, Magento, BigCommerce, React or mobile.

Barriers we found

The real problems: keyboard traps, low contrast, missing labels, unclear headings.

Fixes in plain words

Each fix written so your own team can follow and repeat it.

Tools we test with

JAWS, NVDA, VoiceOver, TalkBack, keyboard only, 400% zoom, AXE, Lighthouse, WAVE.

Every web accessibility case study above was tested by hand, because automated tools miss most of the problems real people face. When your legal or procurement team needs papers, we also prepare a VPAT report and a written accessibility statement.

What you receive with every project

Each web accessibility case study ends with the same three documents, whatever the platform. The audit report lists every barrier with the WCAG 2.2 success criterion it fails, where it occurs, who it affects and how to fix it, ordered by severity so your developers start with the blockers. The findings pages show the actual and expected result with the code involved, so nothing has to be guessed.

When a buyer, a university or a government body asks for proof, we prepare the VPAT, properly an Accessibility Conformance Report, in the Section 508, WCAG, EU or INT edition they name, and a public accessibility statement for your site. The counts of barriers found and fixed on each card come straight from these documents, and the final result is the re-test that closes the project. The same report format is used for WordPress, Shopify, Magento, BigCommerce and mobile apps, so a team that has read one case study can read them all, and if you would like to see a sample before you commission anything, ask and we will send one with the client details removed.

Cover page of the sample audit report: the Anblik logo, the title Bank2Trust web application: WCAG 2.2 Level AA audit, rows for the product tested, standard, report date, prepared by and contact, and five tiles reading 151 barriers found, 11 critical, 43 high, 80 medium and 17 low.
The audit report: every barrier with its WCAG 2.2 criterion, severity and fix.
Two barrier cards on a findings page of the sample audit report: a Medium issue, missing accessible name for a data table (WCAG 1.3.1), and a Critical issue, keyboard focus trapped in a hidden chat widget (WCAG 2.1.2), each with the URL, actual and expected result, code and recommendation.
A findings page: the actual and expected result, the code and the recommendation.
Two pages of the sample conformance report: the cover, headed Bank2Trust Accessibility Conformance Report, Revised Section 508 Edition, with the product name, report date, evaluation methods and applicable standards, and a page showing Table 1, Success Criteria Level A, with columns for criteria, conformance level and remarks.
The conformance report, VPAT or ACR, when a buyer asks for one.
See our web accessibility services
Write to us

FAQ

Frequently Asked Questions

What is a web accessibility case study?

A short, honest record of one real project: the barriers found in the audit, the fixes made, and the final WCAG 2.2 Level AA result – so you can judge the work by outcomes, not by claims.

Which platforms do the case studies cover?

WordPress, Shopify, Magento (Adobe Commerce), BigCommerce, React and native iOS and Android apps. For new builds we also offer our WordPress, Shopify and BigCommerce ADA-compliance themes and free WordPress accessibility plugins.

Do you test with real screen readers and keyboards?

Yes. Every project is checked by hand with JAWS, NVDA, VoiceOver and TalkBack, keyboard only, at 400% zoom and in forced-colours mode, against WCAG 2.2 and Section 508.

Can I get a VPAT or accessibility statement?

Yes. When procurement or legal teams need them, we prepare a VPAT report and a written accessibility statement, both mapped to WCAG 2.2 and Section 508.

How do I start my own web accessibility project?

Start with an audit of your live site or app. Explore our web accessibility services or reach us through the contact page – we reply with a clear, priority-based plan.