An accessibility services contract should cover scope, deliverables, the WCAG standard being applied, pricing and payment terms, timeline, confidentiality, intellectual property, liability limits, and termination. The contract names what is being audited or remediated, which version of WCAG applies (2.1 AA or 2.2 AA), how issues are reported, and what happens after delivery. Both parties should be able to read the contract and agree on exactly what is being purchased, when it will arrive, and what each side is responsible for.
| Contract Section | What It Should Define |
|---|---|
| Scope of Work | Pages, screens, flows, environments, and assistive technologies covered |
| Standard Applied | WCAG 2.1 AA or WCAG 2.2 AA, plus any regulatory framework (ADA, Section 508, EN 301 549) |
| Deliverables | Audit report, ACR, remediation guidance, validation, or training materials |
| Pricing and Payment | Fixed fee or hourly, deposit, invoicing schedule, late payment terms |
| Timeline | Start date, milestones, delivery date, revision windows |
| Confidentiality | NDA terms, data handling, how findings can be shared |
| Liability | Limits on damages, indemnification, no guarantee of legal outcomes |
| Termination | Notice period, fees owed for partial work, return of materials |
Why the Scope Section Matters Most
Scope is where most accessibility contracts succeed or fall apart. A vague scope leads to disputes over what was promised. A precise scope sets expectations for both sides.
The scope should list specific URLs, app screens, or user flows. It should state the environments covered: desktop, mobile web, native iOS, native Android. It should name the assistive technologies that will be used during evaluation, such as NVDA, JAWS, VoiceOver, and TalkBack.
If the project covers a website with 500 pages, the contract should not say “the website.” It should say which pages or which templates the auditor will evaluate, and how representative pages were selected.
Which WCAG Standard Does the Contract Reference?
The contract should name the exact standard. WCAG 2.1 AA remains the most widely requested standard in 2026, but WCAG 2.2 AA is increasingly required for newer procurement requests and government work.
If the project supports ADA compliance, Section 508, or EAA compliance, the contract should say so. Each regulatory framework references WCAG slightly differently, and the contract needs to map the work to the right framework.
A VPAT or ACR engagement should specify the VPAT edition: WCAG, Section 508, EN 301 549, or INT. The WCAG edition is the most common default.
Deliverables Should Be Named and Described
“Audit” by itself is not a deliverable. The contract should describe what the audit report contains: issue list, WCAG criterion mapped to each issue, severity rating, location, remediation guidance, and screenshots or code snippets where useful.
If the engagement includes remediation support, the contract should clarify whether the vendor writes code fixes, advises the client’s developers, or reviews fixes after the client implements them. These are three different services with three different price points.
Validation should be its own line item. After remediation, the auditor returns to confirm issues were addressed. Without validation, the client has no documented evidence that fixes worked.
Pricing, Payment, and Revision Terms
Fixed-fee pricing is standard for accessibility audits and VPAT services. Hourly billing is more common for consulting and remediation. The contract should state which model applies and what triggers additional fees.
Common payment structures include 50 percent deposit and 50 percent on delivery, or net 30 invoicing after delivery. Late payment terms should be defined.
Revisions deserve their own clause. If the client requests changes to the report after delivery, how many rounds are included? What counts as a revision versus a new scope item? Clarity here prevents friction at the end of the project.
Confidentiality, IP, and Liability
Accessibility audits often touch unreleased products, internal flows, and proprietary code. The contract should include a confidentiality clause or a separate NDA. Data handling and report distribution rules belong here too.
Intellectual property terms should clarify who owns the audit report. In most cases, the client owns the deliverable once payment is complete, and the vendor retains rights to its methodology and templates.
Liability clauses should cap damages at the contract value and clearly state that the audit does not guarantee any legal outcome. An audit identifies issues against WCAG. It does not promise immunity from lawsuits or regulatory action.
Termination and What Happens If the Project Stops
Either party may need to exit the contract. The termination clause should define notice periods, fees owed for partial work, and what materials are returned or destroyed.
If the client cancels mid-audit, the contract should specify whether the deposit is refundable and what portion of the work product is delivered. If the vendor cannot complete the work, the contract should state how the client is made whole.
Frequently Asked Questions
Should the contract guarantee WCAG conformance after remediation?
No reputable vendor guarantees conformance. The contract should state that the vendor will identify issues and provide remediation guidance against the chosen WCAG standard. Conformance depends on the client implementing fixes correctly and maintaining the site over time.
How long should an accessibility services contract last?
Most single-engagement audits run 4 to 8 weeks from kickoff to delivery. Ongoing retainers for monitoring, training, or remediation support typically run 6 to 12 months with renewal terms built in.
Does the contract need to mention specific assistive technologies?
Yes when it adds clarity. Naming the screen readers and browsers used during evaluation tells the client what was actually evaluated and gives the audit report defensible methodology.
What if the vendor uses scans instead of a manual evaluation?
The contract should make the methodology explicit. Scans only flag approximately 25 percent of issues and cannot determine WCAG conformance. If a vendor proposes a scan-based deliverable as an audit, that is a red flag, and the contract should be rewritten to reflect what is actually being delivered.
A clean accessibility services contract reads like a description of the work, not a sales document. Both sides should finish reading it knowing exactly what will be delivered, when, for how much, and what happens if anything changes.
Looking for accessibility professionals to work with? Contact through the Accessibility Base directory to find vendors who can scope and deliver the work.