Most accessibility audits read like a Lighthouse export with the score copy-pasted into a Word document. Federal procurement evaluators see through that immediately. Our WCAG 2.1 AA audits are written for a procurement-officer reader: scope statement, success-criterion matrix, representative manual tests, accessible-PDF assessment, and a remediation timeline with dates.
**Automated layer:** axe-core, Lighthouse accessibility, WAVE, plus a manual reproducibility check on every flagged issue.
**Manual layer:** Keyboard-only navigation walkthrough, screen-reader testing (NVDA + VoiceOver baseline), focus management, skip-link verification, ARIA-correctness check, accessible name computation per WAI-ARIA 1.2.
**Forms layer:** Label associations, error handling, error-to-field linking, autocomplete attributes, accessible inline validation.
**PDF layer:** Tagged-structure check, reading order, alt text on images, table headers, form-field accessibility, language tag.
**Media layer:** Captions, transcripts, audio descriptions where required, autoplay/animation behaviour vs WCAG 2.2.1.
**Code layer:** Semantic HTML, heading hierarchy, landmark structure, lang attributes (especially for bilingual EN/FR pages).
We deliver the audit in three files:
1. **Executive summary PDF (accessibly tagged)** — 2-page summary you can share with procurement evaluators or internal sponsors.
2. **Conformance matrix spreadsheet** — every WCAG 2.1 success criterion at A and AA, with status (pass / fail / partial / not applicable), evidence link, and remediation effort estimate (hours).
3. **Detailed findings document** — for each failure: screenshot, code excerpt, success-criterion citation, plain-language impact statement, and recommended fix.
All three deliverables are themselves accessibility-tagged — important when the evaluator is testing whether you actually live the standard.
An audit that doesn't ship with a remediation path is half the deliverable. We follow every audit with a fixed-fee remediation engagement quote, scoped against the conformance matrix. Typical remediation is 60-180 hours for a 30-50 page corporate site; we work with your dev team or implement directly.
We re-test every remediated item against the original failure conditions and update the conformance matrix. The final deliverable is a passing matrix and an updated published accessibility statement on your site — both useful artifacts for the next RFP technical response.
1-2 weeks for a 30-50 page site, depending on PDF and form complexity. We can deliver an interim findings memo in 5 business days if you have an active RFP timeline.
CAD $7,500 - $14,500 for a typical corporate site. Sites over 100 pages or with extensive PDF libraries quote higher.
Either. We deliver remediation as a separate fixed-fee engagement, or we hand the conformance matrix to your dev team and re-test.
Yes — both languages tested. Language-attribute correctness across EN/FR transitions is one of the most common SWA failure modes we find.