At a glance

Industry
B2B software sold to enterprise and public-sector buyers
Product type
SaaS applications and a public website
Service
VPAT testing and ACR services prepared for an RFP
Standard
WCAG 2.1 Level AA
Scope
Multiple applications already in use, a later product release, and the public website
Testing
Desktop and mobile, in Firefox, Edge, Chrome, and Safari, with NVDA, JAWS, VoiceOver, and TalkBack, except where a product did not support a platform
Timeline
A formal RFP with a fixed submission deadline

The challenge

The company had to submit current, test-backed Accessibility Conformance Reports as part of a formal RFP. The solicitation set a fixed deadline, and the vendor did not have those reports ready.

What looked like a one-time paperwork task pointed to a larger gap. Internal teams did not share an accessibility method, and earlier internal reviews had not included formal testing. That made it hard to describe conformance to a buyer with confidence.

The first request covered multiple applications already sold to commercial customers and public agencies. As the work continued, the scope grew to include updated reports for those applications, a new ACR on the VPAT 2.5 INT template for a later product release, an evaluation of the public website, and planning involving legal, product, and other internal stakeholders.

The vendor needed validated testing, reports a procurement team could review by the RFP deadline, practical guidance for engineers, and a roadmap that would cover later releases rather than another one-time document.

Our approach

We ran a manual evaluation against WCAG 2.1 Level AA on the in-scope applications and public website. Testers checked keyboard interaction and followed real user tasks. Testing took place on desktop and mobile in Firefox, Edge, Chrome, and Safari, using NVDA, JAWS, VoiceOver, and TalkBack unless the product did not support a platform.

From those results, we prepared and reviewed Accessibility Conformance Reports on the VPAT 2.5 INT template. The reports were written so the vendor could respond to the RFP and later onboarding requests. When a new release was ready, we updated the documentation to match it. We also drafted an accessibility statement for the public site.

With legal, product, and other internal stakeholders, we built a practical roadmap for later releases. We ranked issues by user impact. The fix notes were written for the engineering team and flagged interface problems that appeared on more than one screen, so work could be scheduled across releases instead of waiting for the next buyer request.

The company later returned for further evaluations, revised ACRs, and advisory support as new requirements appeared.

What we found

  • Form fields were missing labels, or the labels did not make the purpose of the field clear.
  • Error messages were not tied to the fields they referred to.
  • Custom controls such as dropdowns, toggles, and tabs were not announced.
  • Some modals and dialogs could not be closed from the keyboard.
  • Color contrast on buttons was insufficient.

Beyond the specific issues, the evaluation showed that internal reviews were not a sufficient basis for an ACR. Barriers were documented as we tested each workflow, then arranged by user impact and by patterns that recurred in the interface, so engineering work could be scheduled across releases. The public website was included once it became clear that buyer questions would not stop at the applications themselves.

Outcome

The reports were prepared on the VPAT 2.5 INT template. Those reports passed procurement review. Vendor onboarding then proceeded without delays attributed to accessibility documentation. Updated materials were prepared for later product releases, and accessibility review became part of internal planning instead of a task that started only when a customer asked.

The company left with a clearer plan for later releases, keeping the reports current, and answering later buyer reviews of both the applications and the public site.

What this means for SaaS vendors facing an RFP

Enterprise and public-sector RFPs may ask for a current ACR. Guidance on answering accessibility questions in an RFP explains what reviewers may expect to see. A report that is not tied to recent testing may not provide enough evidence for the review, and a gap discovered in the middle of a solicitation can be difficult to close before the deadline.

Vendors that already know another release is coming should treat the first ACR as the start of a cycle: test the flows buyers will use, write the report from that evidence, plan fixes by impact, and update the document when the product changes. Legal and product leaders can share that roadmap so the next review does not begin from scratch.

Work with us on a VPAT for an RFP

If an RFP has asked for a current ACR and your team does not yet have test-backed documentation, we can help you scope the work.

Related pages: VPAT testing and ACR services, software accessibility, and answering accessibility questions in an RFP.

Review sample deliverables

View sample reports to explore our audit and VPAT/ACR reporting formats. Read these separate, anonymized examples directly on our website without a signup.

Explore another accessibility engagement

Section 508 ACR Case Study: Federal Software Vendor Review

EdTech Accessibility Case Study: Audit and VPAT/ACR Documentation

All accessibility case studies

Client names and identifying details have been omitted or generalized to protect confidentiality.