A WCAG 2.2 AA audit of one property. Findings your engineering team can act on.
One-and-a-half to three weeks. Findings cite WCAG SC, page, element, and component file:line. Signed under principal-engineer attestation. Designed for an ADA demand letter, a vendor RFP, or a marketing-site refresh regression.
$10,000–$25,000 One-and-a-half to three weeks · T&M with cap
A schematic of a single property — pages stacked vertically — with WCAG 2.2 SC tags pinned to specific elements and component file:line citations on the right margin. Reads as "findings your engineering team can act on, not a checklist scored from a screenshot." Architectural, minimal.Counsel needs evidence. Your engineering team needs file:line. The market sells PDFs.
An ADA demand letter landed, or a vendor RFP just asked for your accessibility posture, or your marketing site refreshed and the design team has a feeling something regressed. Counsel needs evidence. Your engineering team needs file:line. Procurement needs a credible signature. The market is full of accessibility PDFs that satisfy none of those.
Most “accessibility audits” available today are an axe-core dump dressed up in a PDF. The findings don’t cite component file:line. The remediation roadmap is “fix the axe-core findings.” The signature, if there is one, is from a firm whose engineers never opened your codebase. axe-core is a useful tool — we run it as part of the engagement — but a tool report is not an audit. An audit is engineering judgment applied to your specific surface, with the tools as one input among several.
A1 is the engineering audit for one property. We read your code, walk every page or template, capture assistive-tech evidence on actual NVDA / JAWS / VoiceOver / TalkBack interaction, rate findings by severity, and deliver a remediation roadmap your engineering team can act on without translating it. The report is signed under principal-engineer attestation through Clarity House LLC. Counsel-defensible, procurement-defensible, engineer-actionable.
What you get
-
WCAG 2.2 AA findings report
Every finding cites the specific WCAG 2.2 success criterion, the page or template, the element, and — where the property is built on a known component library — the component file:line. Engineering can act, not "fix it somewhere."
-
Severity-rated remediation roadmap
Findings ranked by severity (blocker / serious / moderate / cosmetic) and ordered for sequenced remediation. Each finding sized in engineering effort, with the fix described concretely. Slottable directly into a sprint.
-
Assistive-tech matrix evidence
Screen-reader, keyboard-only, and zoom evidence captured against the property under test. NVDA / JAWS / VoiceOver / TalkBack as scoped. Not a screenshot of axe-core; recordings and transcripts of actual interaction.
-
Executive summary
One page, plain language, calibrated to the buying moment — counsel-readable for a demand-letter response, procurement-readable for an RFP, audit-committee-readable for a board.
-
Signed audit report
Signed under principal-engineer attestation through Clarity House LLC. The document your counterparty receives.
-
60-minute findings walkthrough
Engineering, design, and (where present) counsel attend; we walk every finding with the BST principal who did the work. Questions answered, follow-up scope identified.
How it works
-
Kickoff & Access
Day 0–1Deliverable Signed contract, scope locked, access provisioned
Contract signed, prerequisites confirmed, scope locked. Templates enumerated, locales confirmed, assistive-tech matrix scoped. We do not begin technical work until access and scope are written down.
-
Audit pass
Days 2–8Deliverable WCAG 2.2 AA findings against the scoped templates
Every page or template walked against WCAG 2.2 AA, with assistive-tech evidence captured. axe-core and Pa11y are part of the toolchain; they are not the audit. The audit is engineering judgment applied to your specific surface.
-
Severity & roadmap
Days 9–11Deliverable Severity-rated findings, remediation roadmap, executive summary draft
Findings rated and sequenced. Roadmap drafted with engineering effort sized per finding. Executive summary calibrated to the buying moment. Internal QA pass before the report goes out.
-
Walkthrough & delivery
Days 12–15Deliverable Walkthrough call + signed report
Walkthrough with engineering, design, and (where present) counsel. Revisions incorporated. Signed report delivered under principal-engineer attestation.
Pricing
Engagement model Time & materials with not-to-exceed cap
Compact tier (single small property, ≤ 25 unique templates, single locale, marketing or simple app surface) lands at $10K–$15K / 1.5–2 weeks. Standard tier (≤ 60 unique templates, transactional flows, single locale) lands at $15K–$20K / 2–2.5 weeks. Complex tier (multi-flow app, multi-locale, embedded AI features, or design-system-shipped consumer) lands at $20K–$25K / 2.5–3 weeks. Time-and-materials with a not-to-exceed cap. If we land early, you pay for hours worked. PHI-touching patient-portal surfaces are scoped under G1, not A1.
Anchor pricing reflects typical engagement ranges. Actual fees are scoped per engagement under time-and-materials with a not-to-exceed cap. Pricing shown does not constitute a binding offer.
Frequently asked questions
How long does this take?
What does this cost?
How is this different from axe-core or a tool-only audit?
- focus-management bugs
- screen-reader announcement gaps
- keyboard-trap regressions
- semantic-structure misuse
- cognitive-load issues
Will the report stand up under counsel review?
Will you sign a VPAT 2.5 / ACR off this audit?
Do you do AAA?
Can BST do the remediation work too?
What if my surface is a patient portal?
Often combined with
-
VPAT 2.5 / ACR Production (B1)
A1 produces the audit evidence; B1 produces the signed conformance artifact your procurement counterparty accepts. Most-common mid-market entry combination.
-
Healthcare AI Compliance Review
When the property in scope is a patient portal or other PHI-touching healthcare surface. WCAG audit here, HIPAA / BAA / SaMD lens there.
Ready to find what an engineering audit actually surfaces?
One-and-a-half to three weeks. Findings cite component file:line. Signed under principal-engineer attestation. NDA before any access.