At a glance
- Industry
- Health technology associated with medical-device products and hospital procurement
- Product type
- Websites and portals, device-related assessment tools, and mobile apps
- Service
- Website and application accessibility audits of web, assessment, and mobile products, plus a VPAT 2.5 INT ACR
- Standard
- WCAG 2.2 Level AA
- Scope
- Digital only: websites and portals, device-related assessment tools, and mobile apps. Physical medical devices were not in scope.
- 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 health technology company associated with medical-device products needed its digital products evaluated for hospital procurement. Hospital and healthcare buyers may ask vendors for current, test-backed accessibility documentation before approving a purchase. The company needed that evaluation to cover more than a single marketing site.
The scope included the company’s digital properties—websites and portals—and assessment tools associated with its devices. We also audited mobile apps. Physical medical devices were not part of the work. The digital products were used in clinical and administrative settings, where a barrier in a form, result, or app control could prevent completion of an important task.
The vendor needed an independent audit of the in-scope web, assessment, and mobile products and documentation a hospital procurement team could review. The engagement was scoped to the vendor’s digital products and hospital procurement requirements. It was not a Section 504 audit of a hospital or other covered provider.
Our approach
We carried out a manual audit of the in-scope websites, portals, assessment tools, and mobile apps against WCAG 2.2 Level AA. Testing targeted WCAG 2.2 Level AA and included the WCAG 2.1 Level A and AA criteria incorporated into the HHS Section 504 rule. The HHS rule itself references WCAG 2.1, not WCAG 2.2. Testers worked through real user tasks and checked keyboard access on the web products.
Testing took place on desktop and mobile in Firefox, Edge, Chrome, and Safari. We used NVDA, JAWS, VoiceOver, and TalkBack, except where a product did not support a platform. Mobile apps were evaluated using the assistive technologies supported by their platforms.
We produced a detailed audit report and an Accessibility Conformance Report on the VPAT 2.5 INT template. Findings were recorded by workflow and recurring pattern, so the company’s teams could see what needed attention in the websites and portals, assessment tools, and mobile apps.
What we found
- Form labels and error handling in the portals and assessment tools needed work.
- Some assessment results and data tables could not be interpreted by a screen reader.
- Custom controls in the assessments, including dropdowns, steppers, and sliders, were not announced or could not be operated from the keyboard.
- The mobile apps had unlabeled buttons in VoiceOver or TalkBack.
- Status and result updates were not announced.
Issues were grouped by product area—digital properties, assessment tools, and mobile apps—rather than treated as a single generic website audit.
Outcome
We completed the audit across the websites and portals, assessment tools, and mobile apps, and prepared an ACR on the VPAT 2.5 INT template. Hospital procurement reviews then moved forward. Support has continued through periodic evaluations, ACR updates, and remediation assistance.
This work later supported additional high-value contracts.
What this means for health technology vendors selling to hospitals
In our work, hospital procurement teams commonly ask software and device vendors for current accessibility documentation. What procurement teams look for in a VPAT/ACR is a useful starting point for that request. A report that is not tied to recent testing of the actual product—including assessment tools and mobile apps, not only a public website—may not provide enough evidence for a reviewer.
There is a regulatory reason buyers ask. Hospitals and other healthcare organizations that receive HHS financial assistance have web and mobile accessibility obligations under the HHS Section 504 rule, which uses the Level A and Level AA success criteria of WCAG 2.1. The compliance dates are May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller recipients. The rule also covers web content and mobile apps a recipient provides through contractual, licensing, or other arrangements. A hospital may therefore ask a vendor for test-backed documentation before licensing a portal, assessment tool, or mobile app.
A health technology vendor is not, by that request alone, necessarily a covered Section 504 recipient. The practical effect is that inaccessible vendor technology can make the buyer’s own obligations more difficult to meet. Auditing the real workflows—including device-related assessment tools and mobile apps—gives the vendor evidence it can provide to a procurement team and a clearer list of what to correct.
Work with us on a healthcare accessibility audit
If hospital procurement has requested current, test-backed documentation of a health technology product, we can help you scope the work.
Related pages: website and application accessibility audits, healthcare 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
SaaS Accessibility Audit Case Study: A Tested Baseline and a Remediation Roadmap
Hardware Accessibility ACR Case Study: Physical Devices and Companion Software
Client names and identifying details have been omitted or generalized to protect confidentiality.
