Build It Right, Not Fix It Later
I don't run audits and hand you a report. I support you to build accessibility into your development process—AI-augmented methodology, automated scanning in CI/CD, and the knowledge to maintain it yourself.
You learn to build accessible products. I make sure you're doing it right.
The Old Way vs The New Way
Traditional accessibility consulting is backwards. Build, audit, panic, fix. There's a better way.
Build first, audit later, scramble to fix
Accessibility baked into the development process from day one
Pay for an audit report, then figure out how to fix it
I support you to implement correctly as you build
Manual testing by expensive consultants
AI-augmented checks catch issues before they ship
One-time audit, then it degrades with every update
Automated scans in CI/CD catch regressions continuously
Accessibility as a separate workstream
Accessibility as part of how you code
The Methodology
Accessibility built into how you work, not bolted on at the end.
Setup & Integration
We integrate accessibility tooling into your development environment and CI/CD pipeline. Automated scans run on every commit.
- +axe-core / Pa11y in CI/CD pipeline
- +Pre-commit hooks for basic checks
- +IDE extensions for real-time feedback
- +WCAG success criteria as acceptance tests
AI-Augmented Development
Your AI coding assistants are prompted to prioritise accessibility. Every component, every interaction, every piece of content.
- +AI prompts weighted for WCAG compliance
- +Semantic HTML by default
- +ARIA patterns applied correctly
- +Alt text that actually describes content
Contextual Review
AI catches what scanners miss. Meaningful alt text, logical tab order, plain language, context-appropriate labels.
- +Vision models evaluate image descriptions
- +Content assessed for cognitive accessibility
- +Interaction patterns reviewed for usability
- +Context-aware labelling (not just "Submit")
Real User Testing
Automated tools and AI catch a lot, but real validation comes from people with disabilities using your product with actual assistive technology.
- +Screen reader users navigating real flows
- +Keyboard-only users completing tasks
- +Users with cognitive disabilities reviewing clarity
- +Feedback loops that inform development
Ongoing Support
I support your team to maintain accessibility as the product evolves. You build the capability, not dependency on me.
- +Team training on accessibility patterns
- +Review support when you need it
- +Pattern library with accessible components
- +Process refinement as you learn
What AI Catches That Scanners Miss
Traditional scanners check if things exist. AI evaluates if they're actually good.
Content Quality
- +Alt text that actually describes the image, not just 'image of...'
- +Plain language assessment - is this readable?
- +Heading hierarchy that makes sense
- +Link text that describes the destination
Interaction Logic
- +Tab order matches visual layout
- +Focus management in modals and dynamic content
- +Keyboard shortcuts don't conflict
- +Form error messages are clear and helpful
Context Awareness
- +'Submit' becomes 'Submit Application'
- +Icon-only buttons get meaningful labels
- +Status messages announced appropriately
- +Time limits flagged for review
Automated Scanning Still Matters
Scanners catch the obvious stuff reliably and continuously. They run in CI/CD on every commit, catching regressions before they ship.
The combination is powerful: scanners for the mechanical checks, AI for the contextual assessment, and your growing expertise to make good decisions.
What Scanners Catch
- +Missing alt text (existence, not quality)
- +Color contrast ratios
- +Missing form labels
- +Invalid ARIA attributes
- +Heading hierarchy gaps
- +Missing document language
- +Keyboard focusability
- +Basic landmark structure
Inclusive User Testing
The final validation is real people with disabilities using your product. I help you design and establish this as part of your process.
Why It Matters
Automated scans catch code issues. AI catches contextual issues. But neither can tell you if a screen reader user can actually complete your checkout flow, or if someone with cognitive disabilities understands your error messages.
Real user testing with people who rely on assistive technology daily reveals what tools cannot.
Setting Up Your Process
- +Identifying the right testers for your product
- +Designing test protocols that work for different disabilities
- +Creating feedback mechanisms that capture real issues
- +Integrating findings back into your development cycle
- +Designing innovations where standard approaches don't fit
How I Work
I'm a qualified Access Consultant, autistic, and my son has complex disabilities. This isn't abstract for me—it's personal.
But I'm not here to run audits. I'm here to support you to build accessibility into your process so you don't need audits. I work alongside your team, review your approach, refine your AI prompts, and help you build the capability.
The goal is your independence. You learn to build accessible products.
What You Get
Not a report that sits in a drawer. A process that works.
CI/CD Integration
Automated accessibility checks running on every commit. Regressions caught before they ship.
AI Prompt Templates
Prompts for your AI coding assistants that prioritise accessibility in every component they generate.
Pattern Library
Accessible component patterns your team can reuse. Modals, forms, navigation, all done right.
Team Training
Your developers learn accessibility as they build. Knowledge that stays with your team.
Review Support
I'm available when you need a second opinion or hit a tricky pattern. Support, not dependency.
WCAG Documentation
If you need formal compliance documentation for procurement, we can produce that based on your actual process.
Ready to Build Accessibility In?
Whether you're starting a new project or want to improve your existing process, let's talk about how to make accessibility part of how you work.