An accessibility audit should help a team act. The goal is not simply to log issues, but to explain what matters, why it matters, and exactly how to improve it.
To do this, I evaluate digital platforms using an Outcomes-based approach. Having audited dozens of healthcare apps and online services, I structure my reviews around the NHS’s realistic perspective: WCAG 2.2 AA is an aspiration, not an immediate pass/fail cliff edge.
The true purpose of an audit is to honestly assess your current state, outline actionable ways forward, and document that ongoing journey transparently in an accessibility statement. This method shouldn’t be limited to healthcare startups striving for NHS compliance—focusing on real-world outcomes and clear roadmaps is the most practical, sustainable way for any company to build inclusive digital products.
What an accessibility audit is about#
Imagine walking into a massive grocery store where the aisle signs are missing, the music is blaring, and the shelves keep moving. That’s what a poorly designed website feels like for someone who is neurodivergent.
My job is to walk through that digital store, fix the signage, turn down the noise, and organize the layout so anyone can easily find exactly what they need without feeling overwhelmed.
I audit websites and mobile apps to make sure they work for everyone. When it comes to neurodiversity—like ADHD, autism, or dyslexia—we focus on reducing cognitive friction.
I look for things that cause sensory overload or confusion, like distracting animations, walls of unbroken text, or confusing navigation, and provide solutions to make the digital experience calm, clear, and intuitive.
What an audit covers#
To give you a complete picture, I layer automated scans with deep manual testing across these key areas:
- User journeys: WCAG-informed review of key pages, screens, journeys, or task flows.
- Navigation: Deep checks of keyboard access, focus behavior, and navigation logic.
- Mobile interactions: Testing touch targets, gestures, and mobile-specific interaction patterns.
- Forms & errors: Reviewing forms, input validation, and error recovery flows.
- Structure & semantics: Verifying code structure, headings, landmarks, and accessibility semantics.
- Interactive elements: Evaluating link text, buttons, controls, and general interaction clarity.
- Visual readability: Checking color contrast, text zoom, reflow, and responsive behavior.
- Assistive technology: Hands-on screen reader and assistive technology testing.
What you get (The Deliverables)#
You will receive clear, developer-ready materials designed to turn findings into immediate action:
- Prioritised findings: Issues ranked clearly by severity and real-world user impact.
- Plain-English notes: Explanations of how each issue affects real users, completely free of dense jargon.
- Reproduction steps: Clear, repeatable steps (and code examples where helpful) to show exactly how bugs occur.
- Practical fixes: Suggested remediation patterns and concrete code examples to speed up development fixes.
- Smart data separation: Clear distinction between confirmed technical issues and subjective items requiring human judgement.
- Accessibility statement: A transparent, public-facing document outlining your current state and your roadmap forward, establishing WCAG 2.2 AA as your working aspiration.
- Verification support: Direct re-test support after your team implements the fixes.
Larger sites and repeated issues: The Systemic Approach#
For larger websites, apps, and digital estates, chasing every individual bug row one-by-one is expensive and exhausting. A traditional audit might hand your developers a spreadsheet with 5,000 separate errors. That volume is overwhelming, but more importantly, it’s usually an illusion.
Often, those 5,000 errors are just 15 core, framework-level issues echoing across hundreds of pages.
To save your team significant time and budget, I use systemic analysis powered by custom automated tooling. By orchestrating robust testing engines like Playwright and axe-core to handle large-scale dataset extraction, I cut through the noise to find the true source of the problem.
Instead of treating every page as an isolated failure, I map defects back to their shared design patterns, global templates, or underlying framework components. This approach delivers:
- Root-cause remediation: Fix a structural bug or contrast defect once in a shared component file, and instantly resolve hundreds of flagged errors across your entire site.
- Reduced developer friction: Engineering teams get grouped, actionable patterns rather than endless, repetitive support tickets.
- Lower remediation costs: Slashing the sheer volume of individual fixes translates directly to weeks of saved engineering time and budget.
🛠️ Advanced Tooling: Learn more about how I use robust, database-driven infrastructure to compress massive issue lists using the Systemic Accessibility Analyzer.
Recent audit clients#
I have delivered trusted audits across healthcare, fintech, e-commerce, and public services, including:
- M&S
- JamUp
- Asclepius
- ZoomDoc
- Leva Clinic
- Adora
- Dawa Innovations
- MediaLogix
- Coloplast
- DigiSafe
- HealthwaveHub
- IMS Maxims
- TympaHealth
- Infervision
- Acorn Compliance