Gymshark
Not commissioned by or affiliated with Gymshark Limited.
-
Keyboard + NVDA Navigation Audit
-
DOM to Accessibility Tree Cross-Reference Audit
M. Abdullah Shah
Accessibility Consultant for WCAG 2.2, ADA, Section 508 and EAA Compliance
Every audit begins with a person, not a script. I test websites by hand, using a keyboard and NVDA screen reader, then back every finding with evidence a developer can act on the same day. Businesses in the United States, United Kingdom, and European Union use these audits to find what automated scanners miss, before a customer or a lawsuit finds it first.
Request a Quote View Completed Audits
0
Reports Published
0
Companies Audited
0
Findings Documented
Accessibility statistics
1.3B
People worldwide live with a significant disability
World Health Organization, 2023
98%
Of the top 1 million homepages have detectable WCAG failures
WebAIM Million, 2024
30–40%
Of real accessibility issues are caught by automated tools alone
Industry-observed baseline, applied in every audit below
services we offer
How I Can Help
Web Accessibility Testing. Manual-first WCAG 2.2 audits combining keyboard testing, NVDA screen reader testing, and DOM and accessibility tree inspection, with evidence attached to every finding.
Pricing runs $30 to $60 per hour depending on testing depth. See the pricing tiers below for exactly what each level includes.
pricing
Web Accessibility Testing
Hourly pricing, scaled to testing depth — not page count. A quote is scoped after a short intake on site size, number of templates, and which flows matter most (checkout, forms, authentication, and similar).
Baseline Check
Quick health check for a small site or pre-launch sanity pass
$30/hr
- Automated scan (axe-core + Lighthouse)
- Manual keyboard-navigation spot check on key pages and flows
- Colour contrast spot check (CCA)
- Prioritised summary findings list
Most Requested
Manual + Screen Reader Audit
Standard WCAG 2.2 AA audit for e-commerce/DTC and SaaS sites
$45/hr
- Everything in Baseline Check
- Full manual keyboard navigation across the site or flows
- Full NVDA screen reader testing
- ANDI inspection of accessible names, roles & landmarks
- Site-wide contrast analysis
- Chrome DevTools DOM / accessibility-tree spot inspection
- Full VIO-numbered finding report with WCAG mapping and developer remediation guide
- Screen-recording evidence per finding
Comprehensive Audit
Complex, multi-template platforms needing a guided fix roadmap
$60/hr
- Everything in Manual + Screen Reader Audit
- Full DOM/ARIA accessibility-tree inspection across every template and component
- Extended NVDA testing across dynamic states and interactive components
- Conceptual, cause-mapped remediation guidance for every finding
- Prioritised remediation roadmap
- One live walkthrough call with your development team
testing methodology
How Every Audit Is Run
Every audit uses the same core process, run by hand against WCAG 2.2 Level AA. Automated tools catch roughly 30–40% of real accessibility issues. The other 60–70% only surfaces through hands-on testing — which is why every audit runs the same seven phases, without exception.
01
Keyboard navigation
Every interactive element reached and activated using Tab, Shift+Tab, Enter, Space, and Arrow keys, with each tab stop verified for real functionality.
WCAG 2.2 SC 2.1.1 · 2.1.2 · 2.4.3 · 2.4.7 · 2.4.11
Deliverable: keyboard reproduction steps per finding
02
Screen reader testing
NVDA across every interactive element, including dynamic content and complex components.
WCAG 2.2 SC 1.3.1 · 4.1.2 · 4.1.3
Deliverable: verbatim announcement transcript per finding
03
ANDI inspection
Accessible name, role, and landmark verification against what NVDA actually announces, catching mismatches between visual labelling and what assistive technology exposes.
WCAG 2.2 SC 1.3.1 · 4.1.2 · 2.4.6
Deliverable: name/role/landmark mismatch report
04
DOM & accessibility tree
Chrome DevTools inspection to find the root cause of a failure — not just the symptom a scanner flags.
WCAG 2.2 SC 1.3.1 · 4.1.2
Deliverable: element selector and attribute-level diagnosis
05
Automated scanning
Axe-core and Google Lighthouse across all key pages, with every automated result manually verified to eliminate false positives.
Baseline coverage — supplementary to Phases 01–04, never a substitute
Deliverable: rule ID, impact level, and element selector
06
Contrast analysis
Contrast ratio measured against WCAG 2.2 AA thresholds across text, UI components, and focus indicators.
WCAG 2.2 SC 1.4.3 · 1.4.11 · 2.4.11
Deliverable: measured ratio, required ratio, and hex values
07
Evidence collection
Screen recordings and annotated screenshots for every finding, so developers see exactly what was tested, not just a written description.
Applies to all findings from Phases 01–06
Deliverable: labelled evidence appendix, one entry per finding
report structure
Every report follows the same structure
Every report follows the same structure: a legal disclaimer first, plain English findings next, and full evidence at the end. Each report states the audit date and the WCAG version applied: WCAG 2.2 AA, the W3C Recommendation published October 2023.
Report structure
- Legal Disclaimer — always first, before any findings
- Executive Summary — for the business owner, plain English
- Findings Summary Table — WCAG criterion and pages affected
- Individual Finding Sections — one per failure
- Evidence Appendix — labelled screenshots and recordings
- Remediation Summary (optional) — priority and effort estimate
Each finding includes
- Finding name and ID
- What was observed — stated factually, in the first person
- A plain English explanation of the issue
- The WCAG standard referenced by criterion number, name, and level
- The user groups affected
- A WCAG specialist note
- A developer remediation guide with illustrative, conceptual code covering possible causes — not copy-paste fixes
- Evidence in the form of an annotated screenshot or recording
portfolio
Independent Practice Audits
The audits below are independent practice work completed on public websites. None were commissioned by, requested by, or affiliated with the brands named below; they exist to demonstrate real methodology, not client work. Every report opens right here — no download, no leaving the page.
Quince
Not commissioned by or affiliated with Quince.
-
DOM to Accessibility Tree Cross-Reference Audit
-
WCAG 2.2 Practice Audit (Keyboard + NVDA)
Cut Clothing
Not commissioned by or affiliated with Cut Clothing.
-
Automated Scan Audit
-
DevTools Console Findings
-
Keyboard and Screen Reader Audit
sample materials
See the report format in full
Two real reports, shown in full, to demonstrate depth and structure before you commission an audit.
Quince — WCAG 2.2 Practice Audit
Cut Clothing — Console Findings
faq
Questions worth answering upfront
How is this different from an automated accessibility scanner?
Automated tools like axe-core and Lighthouse catch an estimated 30 to 40 percent of real accessibility issues. Every audit starts with a scan, then moves to manual keyboard and NVDA screen reader testing to find what the scan cannot see: broken reading order, unclear focus, and content that looks fine but does not actually work for someone using assistive technology.
What happens after I request a quote?
Send the website URL, approximate page count, and target jurisdiction. A clear scope and fixed price quote follow within 24 hours, based on the testing depth the site actually needs.
Do you provide legal advice or guarantee ADA compliance?
No. Findings and reports are informational and reflect independent professional testing, not legal advice. For legal guidance on compliance obligations or litigation risk, consult a qualified attorney.
Which regions and standards do you test against?
WCAG 2.2 Level AA as the baseline standard, with reporting mapped to jurisdiction-specific frameworks on request: ADA and Section 508 for the United States, and EAA and EN 301 549 for the European Union.
certifications
Credentials
-
DHS Trusted Tester Certification, Section 508
-
Section 508 Accessibility Training
-
CPACC Certification
principles
What governs every audit
Depth of methodology, not years in the field, is the differentiator here. These rules apply to every report, without exception.
01
Manual-first, always
Automated scans supplement testing. They never replace it, and no report is delivered on scan output alone.
02
Findings, not verdicts
Every observation describes what was tested and what happened — never a legal conclusion about compliance status.
03
Independent work is labelled as such
Practice audits are disclosed as unsolicited and independent on every page they appear — no ambiguity about the relationship.
04
Point-in-time, stated plainly
Every report states its audit date and WCAG version applied. Sites change; a report reflects the state tested, not a permanent status.
05
Code is illustrative, not guaranteed
Remediation examples show a probable approach. Every guide states plainly that implementation must be adapted and tested by your team.
06
Evidence over assertion
Every finding is backed by a labelled screenshot or recording — not just a written description of what was found.
about
Who I Am
I'm M. Abdullah Shah, an accessibility consultant based in Pakistan, working with e-commerce, SaaS, and hospitality businesses across the US, UK, and EU. I'm currently completing the CPACC certification through IAAP and the DHS Trusted Tester program.
contact
Get a Fixed Price Quote
Send your website URL, approximate page count, and target jurisdiction. A clear scope and fixed price quote follow within 24 hours.
abdullahshah.a11y@gmail.com