Answer with evidence rather than a statement of commitment. Attach a current ACR and say which product version it covers, when it was tested, who tested it and how. If you don’t have one yet, say so, name who is doing the evaluation and give the date it will be ready. A blank answer can’t help.
Key Takeaway
Most vendors don’t publish an ACR (Accessibility Conformance Report) a buyer can read without asking. Of 107 SaaS vendors Harbor checked, 30 did. A current report with specific remarks, recent dates and a named evaluator sets your response apart.
What You’ll Typically See
Accessibility questions in enterprise RFPs generally fall into a few categories:
- “Provide your current VPAT/ACR.”
- “Describe your product’s conformance with WCAG 2.1 AA.”
- “What is your accessibility testing methodology?”
- “Describe your accessibility roadmap and remediation process.”
- “Do you have a dedicated accessibility team or use a third-party evaluator?”
The underlying question is always the same: will this product work for the people who use it, and can you show how you know?
Responding When You Have an ACR
If you already have a current ACR, this is straightforward: attach it. A few things that strengthen your response:
- Note when the evaluation was performed and which product version it covers.
- Mention the evaluator’s credentials (DHS Trusted Tester and IAAP certifications signal demonstrated expertise).
- If your ACR was independently verified, say so. It distinguishes your report from self-assessments.
- Include a brief note about your maintenance plan (how often you re-evaluate).
What a reviewer checks once the report arrives, and the follow-up questions, demos and testing that usually come next, are covered in how buyers review your ACR.
Responding When You Don’t Have One
The worst response is silence or a vague statement like “we are committed to accessibility.” Procurement teams see through that immediately.
A stronger response acknowledges the gap and shows a concrete plan:
- State that an evaluation is in progress or scheduled, who is doing it, and when it will be complete.
- Describe what you’ve done so far (automated scanning, internal testing, known remediations).
- Commit to delivering the completed ACR by a specific date.
Procurement runs on an evaluation window. Ask how long this one is. If you can deliver a credible ACR inside it, you’re still in the running. Whether the report has to come from an outside evaluator is set by the RFP’s own terms, not by any general rule, and does a VPAT have to come from a third party covers what ITI and federal buyers say about it.
Turning It Into a Differentiator
A report that shows its work puts you ahead of vendors whose ACR is missing, automated only, undated or empty in the remarks column. Specific remarks, recent dates and a named evaluator signal:
- You treated the requirement as real work.
- Your product has been evaluated by someone with actual expertise.
- You re-evaluate it when the product changes.
Common Mistakes
| Mistake | Why It Hurts |
|---|---|
| Submitting an automated-only report | A scanner can decide about six of the 55 WCAG 2.2 A and AA criteria on its own, and reviewers know the rest went untested. |
| Submitting an outdated ACR | If it covers a previous product version, it documents something the buyer can’t buy. Section508.gov notes an updated ACR may be required whenever the product changes. When to update it is covered in how often to update a VPAT. |
| Vague commitment language | “We are committed to accessibility” without evidence is a non-answer. Procurement teams score on specifics. |
| Ignoring the question | Leaving it blank or responding “N/A” can be an automatic disqualification depending on how the RFP is scored. |
Common Questions
- How do I answer accessibility questions in an RFP?
- Attach a current Accessibility Conformance Report (ACR) and state the product version it covers, when the testing was done, who did it and how. Answer each question with specifics from that report rather than a general commitment to accessibility. If you have no report yet, name who is doing the evaluation and the date it will be ready.
- What if we do not have a VPAT for an RFP?
- Say so plainly, describe the testing done so far, name who is doing the evaluation, and commit to a delivery date inside the buyer’s evaluation window. A dated plan gives the reviewer something to score. A blank field or “N/A” can count against you, depending on how the RFP is scored.
- What accessibility questions are in an RFP?
- They usually fall into a few groups: provide your current VPAT or ACR, describe your conformance with a named WCAG version and level, describe your testing methodology, describe your accessibility roadmap and how you fix issues, and say whether you have an accessibility team or use a third-party evaluator.
- Does an RFP require a third-party accessibility evaluation?
- Only if its own terms say so. ITI, which publishes the VPAT, says a third-party review is not required, and that a vendor answering a government or other solicitation should follow its directions, which may call for a third-party audit or review. If the RFP is unclear, ask the issuer before you answer.
- Should we mark every row Supports in our ACR to score better?
- No. Section508.gov tells federal buyers to verify vendor conformance claims with their own testing whenever possible, so every Supports needs to hold up when a buyer checks it. Its FAQ also says a product that does not meet every Section 508 standard is still considered for purchase.