Bracket A · Standard
Single site
Up to 30 page templates · one locale · one brand.
$4,500
- Pay
- 50 / 50 · Net-7
- Timeline
- 21 days
- Guarantee
- WCAG 2.2 AA · open issues = 0
§ 03.03 — Sprint 03 of 06 · open now
WCAG 2.2 AA on your WordPress site — with a defensible statement you can publish.
A senior engineer audits, fixes, and verifies your live site against WCAG 2.2 AA — manual NVDA, VoiceOver, and keyboard passes plus axe-core / pa11y. You leave with a passing rubric, a published accessibility statement, and a Loom walkthrough you can hand to legal or procurement. Fixed from $4,500. EAA-ready by the last day.
- Service
- Accessibility Sprint
- Starts at
- $4,500
- Timeline
- 21 days · fixed
- Standard
- WCAG 2.2 AA · EAA · ADA
- Deliverable
- Pass rubric · statement · Loom
- Status
- ● Open · next start 09 Jun
§ 03.03.A
In 50 words
The Accessibility Sprint is a 21-day, fixed-price retrofit that brings a live WordPress site to WCAG 2.2 AA. Manual NVDA, VoiceOver, and keyboard passes plus axe-core / pa11y. You leave with a published accessibility statement, conformance rubric, and Loom handover. From $4,500. EAA-ready · ADA-aligned.
§ 03.03.B
Why teams book this
The European Accessibility Act went into force 28 Jun 2025. A US enterprise prospect just sent you a procurement questionnaire with twelve a11y checkboxes. Your in-house dev ran axe and got "no violations" — but no one in the company has actually navigated the site with a screen reader. Your CMO wants to publish an accessibility statement and can't, because nothing audits accurately.
Automated tools catch about 40 % of real WCAG issues. The remaining 60 % require human ears, keyboard hands, and explicit knowledge of how assistive tech actually reads your markup. This sprint does both — automated for coverage, manual for trust — and ends with a statement you can publish, an issue list with status flags, and a recorded walkthrough you can show legal or a buyer's procurement desk.
Recent client outcomes
- — ESS Group · 17 a11y issues → 0
- — Quay Mission · WCAG 2.2 AA on launch
- — Cyberhive · A11y score 100 mobile
Live numbers · /benchmark. Theme statement live at /accessibility.
§ 03.03.C
What you get · Day by day
D1Kickoff · 90 minRead-only repo + hosting + analytics access. We pick the eight templates and three user flows audited deeply. Brief signed.
D2 — D4Automated baselineaxe-core · pa11y · Lighthouse a11y · WAVE. Eight templates · three flows. Violations exported, ranked, deduplicated.
D5 — D7Manual keyboard passEvery interactive element reachable, focusable, operable. Focus order documented. Skip links verified. No mouse-only traps.
D8 — D10Manual NVDA passRecorded screen-reader walk-through (Windows · NVDA · latest Firefox). Headings, landmarks, forms, errors, dynamic content.
D11 — D12Manual VoiceOver passSame coverage on macOS Safari + iOS Safari. Mobile rotor navigation verified. Touch targets ≥ 44 px.
D13 — D17RemediationMarkup fixes, ARIA where native isn't enough, contrast adjustments, focus styles, form labels, error patterns, motion controls.
D18Re-test · all fourRepeat axe + pa11y + NVDA + VoiceOver. Diff against D2 baseline. Any P0 / P1 left open is named, not buried.
D19StatementAccessibility statement drafted using the EU template — conformance level, methodology, known limitations, contact channel, last review date.
D20DocumentationEditor runbook: how to keep alt text, headings, links, and forms accessible going forward. Loom · 30 min · section-by-section.
D21Handover · publishStatement published at
/accessibility/. Rubric handed to legal / procurement. Conformance noted on /benchmark.
§ 03.03.D
Sample deliverable
Sample · Rubric + Statement
FIG. 03 — Rubric + statement
EU template · plain language
What's in the package
- ▸ WCAG 2.2 AA pass rubric · all 38 success criteria
- ▸ Manual NVDA recording · screen-reader walkthrough
- ▸ Manual VoiceOver recording · macOS + iOS
- ▸ Keyboard-only navigation walkthrough
- ▸ Axe-core + pa11y + Lighthouse exports
- ▸ Accessibility statement · EU template
- ▸ Editor handover runbook · plain language
- ▸ Loom walkthrough · 30 min
- ▸ Re-test commitment · 12 months from launch
§ 03.03.E
What's out of scope
- × AAA-level conformance (extra scope, separate SOW)
- × Native mobile apps (separate sprint)
- × PDFs and other downloadable documents
- × Third-party embeds (YouTube, Google Maps, etc.)
- × Off-WordPress sites
- × Visual redesign or copywriting
Need a full rebuild? See Launch Sprint. Need just performance? See Performance Rescue. Unsure where the bottleneck is? Start with a 7-day Audit Sprint — its fee credits 1:1 against this build.
§ 03.03.F
Pricing · Three brackets
Bracket B · Multi-locale
Localized
2 — 4 locales · WPML or Polylang. Adds 4 days.
$6,200
- Pay
- 50 / 50 · Net-7
- Timeline
- 25 days
- Guarantee
- Per-locale rubric
Bracket C · Enterprise
Multi-site
WP Multisite or 5+ properties. Bespoke quote.
From $9,800
- Pay
- 40 / 40 / 20
- Timeline
- 30 — 42 days
- Guarantee
- Per-site rubric in SOW
Conformance-tied pricing: WCAG 2.2 AA pass criteria, the eight templates, and the three user flows are written into the SOW on D1. If the D18 re-test leaves any P0 or P1 open against the agreed scope, the back-half invoice is voided. Includes a 12-month re-test commitment — if a new release introduces a regression and we're told within that window, the fix is at cost.
§ 03.03.G
FAQ · Five
Q1
Don't tools like axe-core already test for accessibility?
Tools catch about 40 % of WCAG issues. They don't catch wrong heading order, focus traps, screen-reader-only label problems, dynamic-content announcements, motion-induced regressions, or contrast on text overlays. Manual NVDA + VoiceOver + keyboard passes catch the other 60 %. Buyers who ask for an accessibility statement want both.
Q2
Does this make my site EAA-compliant for the European Accessibility Act?
Yes for the in-scope WCAG-conformance portion. EAA requires WCAG 2.2 AA on consumer-facing services and a published statement — both are deliverables of this sprint. EAA also includes operational and customer-support requirements outside the website (alt-format documents, accessible procurement, ongoing review) — those are your org's responsibility and we'll name them explicitly in the statement.
Q3
Why AA and not AAA?
WCAG 2.2 AA is the legal standard the EAA, ADA Title III, Section 508, and most procurement RFPs reference. AAA is aspirational — some criteria (sign-language interpretation, etc.) don't apply to all content and aren't industry-standard for marketing sites. We can quote AAA for specific criteria on request; the default is AA-with-no-open-issues.
Q4
Can you make my Elementor / Divi / Avada site accessible?
Sometimes — but the structural issues page-builders ship (deep div nesting, autogenerated ARIA, inaccessible widgets) are often unfixable without rebuilding. If your site is on a builder, the D1 kickoff includes a 30-min go / no-go assessment. If we can't hit AA inside the SOW, we name it before the deposit is non-refundable, and you can step up to the Launch Sprint at credit-applied rate.
Q5
What happens after the sprint? Does accessibility decay?
Yes — every new feature, every plugin update, every editor adding a heading-out-of-order can regress conformance. The handover runbook is what stops that: it's plain-language guidance on alt text, heading rhythm, link wording, form labels, motion. Pair with the Care Plan for monthly re-testing if your team ships often.