VA Software Accessibility Claims: The Compliance Statement and the Product People Can Use

VA software Section 508 accessibility claims turn on whether a vendor’s statement about meeting the Rehabilitation Act’s accessibility requirements matched the product the Department of Veterans Affairs bought. If you tested the software, developed it or supported its users, you may know which defects the company had already recorded when it supplied its declaration. That comparison connects your technical knowledge to the promises behind a government IT purchase.

What Accessibility Meant in the VA Purchase

Accessibility means people with disabilities can access and use information in ways comparable to people without disabilities. The Department of Veterans Affairs must account for accessibility in the technology it develops, buys, maintains and uses, serving employees as well as veterans and other members of the public. The inspector general’s earlier audit identifies Web Content Accessibility Guidelines 2.0 as the standard for covered web and nonweb content and software.

That asks a different question from whether software performs its promised functions. A system can perform a business function while an accessibility barrier prevents someone from using it. The purchase has to account for the person using assistive technology, too.

What the Procurement File Was Supposed to Show

The process described in the VA inspector general’s July 2025 audit began before the purchase. Officials were supposed to identify whether they were buying covered technology, consider applicable exceptions, and research vendors that met the business need. They then had to identify accessible options, validate that research, select the product that best met accessibility requirements and submit the procurement documentation to VA’s Office of 508 Compliance.

The documents served different purposes. The performance work statement described required results. Market research addressed available products and their compliance. The acquisition-policy update in February 2023 called for a contractor checklist, an accessibility notice in solicitations and an accessibility clause in contracts and orders. Those records help us identify what the government required and what the vendor represented for the particular purchase.

VA Bought the Systems Without Validating Accessibility

The inspector general found that VA officials relied on contract language and vendor declarations without validating accessibility. Of 30 sampled systems, VA’s compliance office classified four as compliant and 26 as noncompliant. These classifications came from VA’s reporting, not independent testing by the inspector general.

Officials had researched products that met business requirements, and some vendors supplied compliance documentation. But the officials took no additional action to verify accessibility. The audit describes the substitution plainly:

We find that a remarkable way to buy accessible technology: put the requirement in the contract, accept the seller’s declaration and leave the validation undone. The obligation made it into the paperwork while people with disabilities still faced barriers to using what VA bought.

A Screen Reader Could Not Identify the Headline

Adobe Learning Manager had a critical defect: screen readers could not identify headline text for users. VA used the product to support employee training aimed at improving veterans’ benefits claims processing nationwide. The inspector general cited VA’s accessibility audit of the product for that finding.

The example puts a user behind the compliance statement. A training system’s accessibility includes whether an employee using a screen reader can identify the text that employee needs. For a tester or implementation employee, the useful detail is the particular barrier, the affected product and what the test showed.

What Proof Do You Need as a Whistleblower?

Useful evidence connects the accessibility requirement, the vendor’s dated statement, the delivered product, the defect and the government purchase or payment. We work through those connections with you, including what the company knew when it made the statement.

• The requirement. The solicitation, performance work statement, contract clause and any approved exception identify the accessibility promise attached to the purchase.
• The representation. A vendor declaration, checklist or accessibility conformance report shows what the supplier said. Its date matters alongside the product it described.
• The product. The release and configuration supplied to VA let us compare the representation with the technology the customer received.
• The test and the knowledge. A product audit, defect entry and communications about the barrier can connect a technical finding to who understood it and when.
• The payment connection. Acceptance records, invoices and payment records connect the promised product to the government money.

An invoice, agency acceptance and Treasury disbursement are distinct records. We connect the purchase and billing evidence to the accessibility promise that mattered under that contract. A developer may know when a defect entered the product. A tester may know when it was reproduced. An implementation employee may know which configuration reached VA. Those are different contributions to the same comparison.

The False Claims Act reaches knowing false claims and false records that matter to claims for government payment. Here, we examine the vendor’s own statements and knowledge alongside the technical failure and the purchase. A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.

Dates and Exceptions Belong to the Same Purchase

The governing requirements and any approved exception belong beside the dated vendor statement. The audit described written reasons for exceptions and exemptions kept in the contract file. VA’s procedures required exception requests to go to the compliance office for approval. We examine which requirement applied when VA bought the product and whether the exception covered what was supplied.

The inspector general also identified a practical timing problem: a system’s deployment date could come months or years after procurement. Scores in VA’s Defect Tracking Tool changed as defects were addressed, so a later score could differ from the original audit report. We compare the version VA received with what the vendor said about it at the time.

What the Compliance Label Missed

The earlier January 2024 audit, on VA’s broader accessibility oversight, found that some designations in the VA Systems Inventory disagreed with the compliance office’s certifications. The inspector general attributed inaccurate designations to information that had not been updated or validated. We would want the underlying audit: some systems labeled compliant in VA’s own inventory were noncompliant according to its own compliance office.

In its response to the procurement audit, VA management proposed reviewing accessibility conformance reports and other market-research materials to compare products’ compliance. Its response expressly distinguished that document review from a product audit. If you tested the software, that distinction matters: a review of the seller’s paperwork still leaves your test results to explain.

You Know What the Accessibility Statement Left Out

If you know a vendor’s accessibility declaration concealed a barrier already documented inside the company, speak with our whistleblower experts about the product and the promise. We work with you to build your strongest case around the testing, the company’s knowledge and the government purchase. We bring in government procurement whistleblower lawyers who understand software accessibility claims and stay beside you through the process.