At a glance
- Industry
- A hardware manufacturer with companion web, mobile, and software products
- Product type
- Physical devices plus related web applications, mobile apps, utilities, and user documentation
- Service
- Hardware accessibility testing and ACRs on the VPAT 2.4 template
- Standard
- WCAG 2.1 Level AA for digital products, and Revised Section 508 §407 Operable Parts and §409 Status Indicators for the devices
- Scope
- A web application tied to a pending contract, followed by a wider set of physical devices, companion software, mobile apps, utilities, and documentation, including the connection between devices and companion software
- 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, plus hands-on testing of the physical devices
The challenge
The work began because a contract already in progress asked for a test-backed Accessibility Conformance Report on a web application. Product managers had been describing accessibility themselves without a formal testing method behind those statements. Once procurement reviewers asked more detailed questions, that internal material was no longer enough.
The problem was not confined to one application. The scope also involved physical devices, mobile apps, software utilities, and user documentation. Incomplete or weakly supported claims had started to raise risk in contract reviews.
The vendor needed an independent evaluation, a structured way to prepare ACRs, help during procurement and legal review, and a process it could apply to later products and releases. The engagement covered physical hardware products and their companion software.
Our approach
We introduced a manual evaluation against WCAG 2.1 Level AA on the digital products in scope. Testers worked through real user tasks and checked keyboard access. For those digital products, we tested on desktop and mobile in Firefox, Edge, Chrome, and Safari using NVDA, JAWS, VoiceOver, and TalkBack, except where a product did not support a platform.
We also evaluated the devices in person alongside the software that accompanied them. The hardware review addressed Revised Section 508 §407 Operable Parts and §409 Status Indicators. The §407 review covered whether controls could be distinguished by touch, how buttons and similar parts were operated, and whether they could be used without tight grasping or twisting. We also examined how the physical product and companion software behaved together, including configuration tools and the connection between the device and application.
As the relationship continued, we prepared Accessibility Conformance Reports using the VPAT 2.4 template, reviewed accessibility questionnaires in RFPs, examined accessibility language in contracts, and advised the product team before releases. The client’s legal team coordinated later ACR requests.
What we found
- Some physical controls covered by §407 required tight grasping or twisting.
- Some status indicators relied on light alone, with no audio or tactile cue.
- The setup or configuration app was not usable with a screen reader.
- The mobile companion app had unlabeled buttons in VoiceOver or TalkBack.
Beyond the specific issues, the evaluation showed that self-reported statements were not a sufficient basis for an ACR once reviewers asked for detail. Those areas, together with the digital-product findings, were written into the reports and into guidance the legal and product teams could use in later reviews.
Outcome
The company moved from informal internal statements to a more consistent method for testing and documentation. Reviewers accepted the reports, and the VPATs were well received. Before the engagement, weak documentation had caused procurement delays; those delays were reduced once test-backed reports were available. The legal team had more confidence during contract review. Accessibility work was organized across the product set rather than handled separately for each item.
The engagement also left a workflow the vendor could apply to new devices and later software releases: test, document, and support procurement as a regular process instead of treating the ACR as a last-minute request. This work later supported substantial additional contracts.
What this means for hardware vendors selling to public buyers
Buyers in government and other public institutions may ask for an ACR that covers both the device and the software used to configure or operate it. A report that addresses only a companion website may not answer questions about operable parts, tactile controls, status indicators, or the way hardware and software work together. What procurement teams look for in a VPAT/ACR explains how reviewers may assess those claims.
Hands-on device testing belongs in that work. Screen-reader results on a web console matter, and so does whether a control can be found and used without relying on vision alone and without tight grasping or twisting. Vendors that sell a family of products are better served by one repeatable method than by starting over whenever a contract comes up for review or renewal.
Work with us on a hardware ACR
If you need an Accessibility Conformance Report that covers physical devices and their companion software, we can help you scope the testing and documentation.
Related pages: hardware accessibility testing, government and public-sector accessibility, and what procurement teams look for in a VPAT/ACR.
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
Health Technology Accessibility Case Study: Auditing Digital Products for Hospital Procurement
Client names and identifying details have been omitted or generalized to protect confidentiality.
