Web accessibility audit for a
browser-based cloud product

Evaluating and documenting web accessibility conformance for a web browser-based cloud collaboration tool, resulting in a published VPAT

Project brief

Enterprise and government customers increasingly require accessibility compliance before procurement, so companies conduct voluntary accessibility audits to assess and document how well their products meet established standards.

The audit was conducted for a browser-based cloud collaboration product using a VPAT (Voluntary Product Accessibility Template), a structured framework that translates accessibility standards into testable criteria. A completed VPAT with documented findings is referred to as an Accessibility Conformance Report (ACR).

The accessibility criteria cover two aspects: the overall product and the electronic documents associated with it. As the product is browser-based, the VPAT chapters related to hardware and software were not applicable.

Year

2025

Domain

Manufacturing

Platform

Web application

My role

As Senior UX Designer, I led the product side audit, evaluating all key workflows, UI, and interactions against WCAG 2.0, 2.1, 2.2 and Section 508. My familiarity with the product allowed me to conduct a thorough evaluation of each criterion against real usage scenarios. A content designer separately handled the electronic documents section.

Evaluation Methodology

I used a combination of evaluation methods to ensure the audit reflected the true state of the product.

Manual testing

I manually audited all key workflows within the product, documenting the conformance level for each criterion with associated remarks, explanations, and examples. This produced the first draft which was refined through the other evaluation methods.

Testing using accessibility tools

For criteria requiring assistive technology evaluation, I tested using screen readers including VoiceOver and Microsoft Narrator, alongside browser extensions such as High Contrast to assess visual accessibility.

Online accessibility audit tools

Online accessibility audit tools were explored early in the process, but most lack the product and domain knowledge needed to accurately evaluate complex software workflows producing inconsistent and incomplete results. A conscious decision was made not to rely on them.

Developer collaboration

After completing the manual audit, I cross-referenced the findings with the development team to distinguish intended behaviour from implementation gaps, ensuring the report accurately reflected the product's true state.

Deliverable and next steps

The audit resulted in a published Accessibility Conformance Report (ACR). It is available on the official product website for enterprise, government and individual customers to assess product accessibility before procurement.

As a next step, I am working on an AI initiative to support and scale accessibility audits, addressing the limitations identified through the manual process and automated testing tools. This initiative will not only be useful for VPAT documentation but also for general accessibility audit for all designers.

My learnings

Conducting this audit deepened my understanding of accessibility as a practice. An accessibility audit is beyond a checklist; it requires product knowledge, a structured methodology, and cross-functional collaboration.

I understood that WCAG criteria are intentionally open-ended to accommodate diverse product requirements, meaning product knowledge isn't just helpful, it is essential for accurate evaluation
Collaborating with the development team proved valuable. It not only confirmed the intended implementation but it also surfaced gaps the team was unaware of, shifting the team toward more accessibility-aware development practices
Conducting a hands-on audit revealed accessibility gaps in interaction behaviours and edge cases that are invisible in design review and only became apparent through systematic testing