At a glance
- Industry
- Enterprise software sold to commercial customers and federal buyers
- Product type
- Customer applications, public websites, installed software, and supporting documents
- Service
- Section 508 testing services and an ACR using the VPAT 2.5 template requested for the review
- Standard
- WCAG 2.1 Level AA testing used to support a Section 508 procurement review and ACR
- Scope
- The application under federal review, followed by other sites, applications, installed software, and product documentation
- 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
The challenge
A federal purchaser reviewing one of the vendor’s applications asked for an Accessibility Conformance Report using the VPAT 2.5 template. The company already had some accessibility materials on file, but those materials had not been checked through a formal evaluation. Staff had limited experience running that kind of testing, and product, marketing, and legal teams were not working from the same method.
The gap was not limited to the application in front of the federal reviewer. The same uncertainty applied to public websites, other customer-facing applications, installed software, and product documentation. A single report would answer the immediate request. It would not, by itself, tell the company how to evaluate the next product or answer the next buyer.
The vendor needed an independent assessment, a report a federal reviewer could read against test evidence, guidance its engineers could act on, and a repeatable way to prepare for later procurement and onboarding reviews.
Our approach
We carried out a manual evaluation against WCAG 2.1 Level AA. The digital testing included the WCAG 2.0 Level A and AA criteria incorporated into the Revised Section 508 Standards. Testers worked through real user tasks on each in-scope property and checked keyboard access. We ran that work on desktop and mobile in Firefox, Edge, Chrome, and Safari, using NVDA, JAWS, VoiceOver, and TalkBack except on platforms the product did not support.
Those results became the basis for the Accessibility Conformance Report used in the federal review. In review sessions with the client, we aligned each statement in the ACR with what testing had actually shown, so the document and the audit findings reflected the same evidence.
We also met with product, marketing, and legal stakeholders to walk through how WCAG 2.1 Level AA and the Section 508 procurement request applied to the products. Recommendations were ordered by user impact. When the same issue appeared in multiple templates or screens, we described it at that shared level so the team could correct the pattern rather than address pages one at a time.
What we found
- In data tables and grids, headers were not announced, and cells were read without enough context.
- Charts and dashboards had no text alternative.
- Some filters, menus, and date pickers could not be reached or operated from the keyboard.
- Focus order jumped around as testers moved through the interface.
- Documentation, including PDFs and help content, was untagged.
Beyond the specific issues, the evaluation showed that existing materials could not show a federal reviewer how conformance had been determined. Issues were recorded as we tested each workflow and grouped when the same pattern appeared across templates or public pages, so engineering work could start at the template rather than page by page. Ownership of the work was also unclear until product, marketing, and legal teams had a shared view of the requirements.
Outcome
We completed the ACR for the application under federal review. The work unblocked the procurement review, and the review moved forward. The vendor was able to offer accessibility documentation earlier in a sale instead of assembling it after a request arrived. Audit and ACR support later extended to additional products and releases.
The longer result was a clearer internal process. Requests began to follow a defined path, and product, marketing, and legal stakeholders had a better split of responsibilities. The company had a foundation for evaluating accessibility, answering federal and commercial buyers, and keeping reports current over time. This work later supported additional high-value contracts.
What this means for software vendors selling to government
Federal buyers may require more than an unverified self-assessment when they request an ACR tied to product testing. When an ACR is requested, it should identify what was evaluated, the applicable standards, the evaluation methods, and the evidence supporting its claims. Section 508 procurement guidance is a useful starting point for that conversation.
A report for one application is still only a starting point. Vendors that sell several products or ship frequent releases need a method their teams can repeat. That usually means a shared evaluation process, clear owners inside product, marketing, and legal, and a plan for updating the ACR when the software changes.
Work with us on a Section 508 ACR
If a federal review has asked for current, test-backed documentation, we can help you scope a similar engagement.
Related pages: Section 508 testing services, software accessibility, and Section 508 procurement guidance.
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
VPAT for RFP Case Study: A SaaS ACR on a Deadline
SaaS Accessibility Audit Case Study: A Tested Baseline and a Remediation Roadmap
Client names and identifying details have been omitted or generalized to protect confidentiality.
