Web Inclusion LabAccessibility audits & accessible documents
Your accessibility report, written by someone who actually uses a screen reader.
Web Inclusion Lab audits websites, apps, and documents against WCAG 2.2, then verifies every finding the way your real users will experience it: by ear, by keyboard, with assistive technology. Automated scanners find a third of the problems. We find the rest.
Tested against WCAG 2.2 AA. Zero axe-core violations. No overlays.
- JAWS
- VoiceOver (macOS + iOS)
- NVDA
- TalkBack
- axe-core
- keyboard only
Services
Three ways to work with us
Fixed scope, plain-language findings, and remediation guidance your developers can act on the same day. No subscriptions to overlay widgets, no 200-page PDFs that nobody reads. Full details on the services page; rates are published openly on the pricing page.
Quick-Scan Review
A focused review of your key pages: automated scanning plus real screen-reader testing of your core flows, so you know exactly where you stand.
You receive
- Prioritized findings report
- Screen-reader walkthrough recording
- Top-ten fix list with code guidance
Full WCAG 2.2 Audit + VPAT/ACR
Comprehensive conformance audit of your site or application, with the formal documentation your enterprise and government buyers ask for.
You receive
- Complete WCAG 2.2 A/AA audit
- VPAT / Accessibility Conformance Report
- Prioritized remediation roadmap
- Re-test of fixed issues included
Accessible Documents
PDF and form remediation that goes beyond passing checkers: we rebuild documents until a blind user can actually read and complete them, then prove it.
You receive
- Tagged, WCAG- and PDF/UA-conformant files
- Fillable forms that work by screen reader
- veraPDF + Acrobat verification evidence
Why us
Blind-led testing is the difference
Many audits stop at automated output or simulated assistive technology. Our founder depends on it.
Findings scanners cannot see
Automated tools catch missing labels. They cannot tell you that your link icon announces twice, your form traps focus, or your "accessible" PDF reads in the wrong order. Daily assistive-technology use catches what simulation misses.
Evidence, not opinion
Every finding cites the WCAG success criterion it violates and ships with a recording of the failure happening on a real screen reader, so your team sees the user impact, not just a rule number.
We build, too
Our recommendations come from engineers who ship production web and iOS code, so the fixes we propose are ones your developers can actually implement.
Process
How an engagement runs
Free consultation
A 30-minute call to understand your product, your compliance deadline, and which pages or documents matter most.
Audit and verify
Automated scans first, then manual keyboard and screen-reader passes over your real user flows. Every finding is reproduced before it is written down.
Findings you can act on
A prioritized report with WCAG citations, impact descriptions, recordings, and concrete fix guidance, walked through together on a call.
Re-test and document
After your fixes land we re-test, update the report, and issue the conformance documentation your buyers and regulators expect.
Results
A recent rebuild, measured
The paratransit form blind riders could not complete
A metro transit agency's application form for its door-to-door service for disabled riders had been professionally remediated by a vendor, yet it failed 29 automated checks and could not be completed with a screen reader at all. The people the form exists for were locked out of it. We rebuilt the document from the ground up: correct structure and reading order, real fillable fields with programmatic labels, and verification at every round.
About
Who you are working with
Web Inclusion Lab is led by Yahya Abdikadir, a blind engineer who has used screen readers every working hour for over a decade: JAWS and NVDA on Windows, VoiceOver on Mac and iPhone. He built and operates a production web platform that holds WCAG 2.2 AA with zero automated violations, ships native iOS code, and has remediated government documents to Section 508 for a state transportation agency.
That combination is the lab's method in miniature: engineering skill to find and fix the problem, and lived assistive-technology experience to know, not guess, when it is truly fixed. More about the lab and what we believe.
Contact
Start with a conversation
Tell us what you are building, what deadline you are under, or which document is causing trouble. You will get a plain answer about scope, fit, and timeline.
Accessibility statement
This site practices what it audits
This website targets WCAG 2.2 AA and is tested with JAWS, NVDA, VoiceOver, and keyboard-only navigation before every release. It uses semantic HTML landmarks, a visible focus indicator, honors your reduced-motion preference, and needs no JavaScript to read or navigate. The only script anywhere is the spam check on our forms, and those forms still describe themselves to assistive technology while it loads.
If anything here does not work with your assistive technology, that is a bug we want to hear about: support@webinclusionlab.com. The full accessibility statement and alternate formats have their own pages.