Guide
Procurement checklist for accessible web work
A good RFP asks for evidence, not promises. Use this list to write requirements and to score the responses you receive.
Requirements to include
- Target standard: WCAG 2.1 Level AA, with the scope of pages, templates, and PDFs stated
- Written methodology, including automated tools, manual testing, and assistive technologies used
- Named testers and their accessibility qualifications
- An Accessibility Conformance Report in VPAT 2.x format for each product or site
- Remediation deliverables with retesting and a verification report
- Training for your staff, and a post-launch support or monitoring option
- Insurance certificates, W-9, and references from public clients
- Data handling terms, including how credentials and site access are protected
Red flags
- Claims of "100% compliant" or "ADA certified"
- Pricing that does not reference a page inventory
- An overlay widget presented as the whole solution
- No test evidence, or no assistive technology testing
- Reluctance to name the WCAG version they test against
Scoring guide
| Criterion | Weight |
|---|---|
| Method and evidence quality | 30% |
| Relevant public-sector experience and references | 25% |
| Deliverables, including ACR and verification records | 20% |
| Price, on a like-for-like scope | 15% |
| Timeline and capacity | 10% |
Need a quick automated baseline before you write the RFP? The free Title II Snapshot reads up to 10 public pages, and our published audit prices help with a budget line. Our current audit is automated only, with no assistive technology testing, so it would not meet an RFP that requires that testing.
General guidance only. Your procurement rules and counsel take precedence.