A small New York City dermatology practice bought a one-year subscription to an accessibility overlay product in August 2022 for $490. It renewed in August 2023. According to a class action filed on June 24, 2024, the practice bought in reliance on the vendor's promises about accessibility and ADA compliance. The merits of that case are for a court to decide. The procurement lesson doesn't depend on the outcome.
A low-cost subscription can still become a high-stakes risk decision when a vendor's claims substitute for your own verification. This checklist covers how to evaluate, contract for, and renew accessibility tools without treating a purchase as a transfer of responsibility.
Prerequisites
Before you start, confirm you have:
- A named internal owner for Accessibility Governance, not just a budget holder.
- A current inventory of the digital properties the tool would touch.
- Access to someone who can run Conformance Testing against WCAG 2.1 or WCAG 2.2, in-house or contracted.
- Your legal team's view of which obligations apply: ADA Title III, ADA Title II (and the DOJ Final Rule (2024)), Section 508 of the Rehabilitation Act, or the European Accessibility Act.
The Checklist
1. Define the claim you are actually buying.
Write down every accessibility or compliance statement in the vendor's sales material, website, and proposal. Separate capability claims ("detects missing alternative text") from outcome claims ("makes your site ADA compliant").
Good looks like: A one-page claims register, each entry tagged capability or outcome, with its source and date captured.
2. Treat outcome claims as unverified until proven.
No tool can confer legal compliance. ADA Title III and its case law turn on whether people with disabilities can use your digital experience, not on which product you installed.
Good looks like: Any "guaranteed compliance" language is either removed from the contract path or flagged for legal review before signature.
3. Request an Accessibility Conformance Report.
Ask for a current Accessibility Conformance Report based on the Voluntary Product Accessibility Template, covering the vendor's own interface and, where relevant, the output it produces. Check the WCAG version and edition, the test date, and the evaluation method.
Good looks like: A dated report naming specific WCAG success criteria, with Partial Conformance stated plainly where it exists. A report claiming blanket support with no remarks is a red flag.
4. Ask who tested, and how.
Request the testing methodology: manual versus automated, which Assistive Technology Web Accessibility Specialist used, and whether people with disabilities participated. Automated scanning alone can't establish conformance to many WCAG criteria.
Good looks like: Documented Screen Reader Testing and keyboard-only testing, performed by named evaluators, ideally with credentials such as Web Accessibility Specialist or Certified Professional in Accessibility Core Competencies from the International Association of Accessibility Professionals.
5. Run your own pilot on your own properties.
Vendor demos use vendor content. Deploy the tool on a representative sample of your templates, forms, documents, and checkout or intake flows, then test with and without it.
Good looks like: A written pilot report showing defects found, defects the tool resolved, defects it introduced or left, and the test conditions used.
6. Test for harm, not just benefit.
Check whether the tool interferes with a user's existing Assistive Technology, overrides user settings, or adds markup conflicts such as redundant aria-label, aria-hidden, aria-labelledby, or aria-describedby usage. WAI-ARIA misapplied can make an experience worse.
Good looks like: Test notes confirming that screen reader, magnification, and voice-control users complete core tasks Assistive Technology least as well as they did before installation.
7. Confirm the tool doesn't replace source remediation.
Overlays and runtime fixes sit on top of code you own. Document which defects must still be fixed in design, content, and code, and who is accountable for each.
Good looks like: A remediation backlog that continues to exist and shrink regardless of the tool, with owners and dates.
8. Verify authoring and document coverage.
Many accessibility failures live in PDFs, email, video, and mobile apps. Check whether the tool addresses those, and against which standards (PDF/UA, Closed Captions, Audio Description requirements).
Good looks like: A coverage matrix stating, for each content type, what the tool does, what it doesn't, and what your team handles separately.
9. Write performance measures into the contract.
Define measurable obligations: conformance targets against named WCAG success criteria, defect response times, and the right to audit.
Good looks like: Schedules attaching specific, testable commitments to specific WCAG criteria, not generic language about "improving accessibility."
10. Allocate risk deliberately.
Review warranty, indemnification, limitation of liability, and disclaimers. Ask legal whether any compliance promises survive the fine print.
Good looks like: Counsel's written summary of what the vendor is and isn't contractually standing behind.
11. Add exit and data terms.
Include termination rights tied to failed performance measures, and confirm you can remove the tool cleanly without breaking your site.
Good looks like: A tested removal procedure and a termination clause that doesn't penalize you for a documented performance failure.
12. Schedule a renewal review before the auto-renew date.
Renewal is a decision point, not a default. The practice in this case renewed after its initial one-year term; your process should make renewal an active choice.
Good looks like: A calendar trigger Assistive Technology least 90 days before renewal, a re-run of the pilot tests, an updated Accessibility Conformance Report request, and a signed renewal decision memo.
13. Track outcomes with user-centered evidence.
Collect accessibility complaints, support tickets, and audit findings tied to the tool's coverage areas.
Good looks like: A dashboard reviewed quarterly by the Accessibility Governance owner, with user feedback channels that are themselves accessible.
Common Mistakes
- Buying on price. A low fee signals low financial exposure, not low legal exposure.
- Accepting a badge or statement as proof. A compliance seal isn't Conformance Testing.
- Letting marketing language into your own accessibility statement. If you publish a claim of compliance because the vendor made one, you've adopted it.
- Auto-renewing silently. Product behavior, WCAG versions, and your site all change.
- Skipping disabled-user testing. Scanners miss what real users hit immediately.
Next Steps
Pull every accessibility-related subscription your organization currently holds and run items 1 through 4 against each one this quarter. Flag any with auto-renewal dates inside the next six months. Then assign an owner, build the claims register, and schedule pilot testing for your highest-traffic properties.
The goal isn't to distrust every vendor. It's to ensure that when someone asks why you chose a tool, your answer is a file of evidence, not a sales deck.





