Failure PatternDecision layer

The WCAG Repair Certificate Trap: Why Agencies Sell Compliance They Cannot Defend

Symptom: Client forwards a demand letter citing 40+ violations that the monthly WCAG Repair scan never flagged, because axe-core only catches automated-testable issues and the agency sold the certificate as proof of full ADA compliance. Root cause: WCAG Repair detects only automated-testable issues such as missing alt text, color contrast, ARIA errors, and keyboard navigation flags. Manual checks like meaningful link text, cognitive load, and screen reader flow fall outside axe-core's scope, so the certificate overstates coverage when agencies treat it as a complete audit.

By InnovaAI ResearchPublished

Security Tools
How do you recognize it?
  • •Client forwards a demand letter citing 40+ violations that the monthly WCAG Repair scan never flagged, because axe-core only catches automated-testable issues and the agency sold the certificate as proof of full ADA compliance.
  • •Agency account managers quote the $8.99 Accessibility Guide as a standalone deliverable, then discover the copy-paste fixes reference WordPress, Shopify, and React patterns that do not match the client's custom CMS.
  • •Retainer clients on the $399/mo SMB Starter plan receive the same issue list month after month because nobody implemented the priority fixes, and the progress report shows zero movement.
  • •Sales team promises Section 508 and EAA compliance sign-off based on the downloadable certificate, but the certificate only documents what the automated scan tested, not manual keyboard or screen reader verification.
  • •Free-tier scans hit the 10-page limit mid-audit on multi-template sites, so the agency delivers a partial report and the client's developer finds violations on page 11 during their own review.
Why does it happen?
  • •WCAG Repair detects only automated-testable issues such as missing alt text, color contrast, ARIA errors, and keyboard navigation flags. Manual checks like meaningful link text, cognitive load, and screen reader flow fall outside axe-core's scope, so the certificate overstates coverage when agencies treat it as a complete audit.
  • •The pricing ladder encourages volume selling: $8.99 for a single remediation guide, $29 for a Complete Site Audit, and $399/mo for the SMB Starter retainer. Agencies stack these into compliance promises without budgeting the manual QA hours that ADA, Section 508, and EAA defense actually requires.
  • •Platform-specific fix instructions assume common stacks. When a client runs a bespoke front end, the AI-generated code snippets need translation work that the $8.99 guide price does not cover, and delivery teams absorb the gap.
  • •Monthly rescans surface the same unresolved violations because the retainer scope covers scanning and reporting, not code deployment. Without a remediation clause in the contract, the agency bills for monitoring while the client's legal exposure stays flat.
How do you fix it?
  • •Pull the audit certificate and badge from the client dashboard and add a written scope note listing which WCAG 2.1 and 2.2 AA criteria were machine-tested versus which require manual review, then price the manual pass as a separate line item.
  • •Re-run the scan on every unique page template rather than the 10-page free sample, and upgrade to the paid tier that supports up to 100 pages so the report covers the client's actual surface area.
  • •Open the AI remediation guide, filter fixes by priority ranking, and convert the top items into a tracked implementation checklist with owner and due date before the next monthly rescan.
  • •Move clients from one-off $8.99 and $29 purchases onto the $399/mo SMB Starter retainer only after confirming the client's developer or the agency's own delivery team will ship the fixes each cycle.
Open the WCAG Repair courseWCAG Repair decision recordBrowse the Academy

More on WCAG Repair

More for Security Tools