At a glance

Industry
B2B SaaS used by enterprise and public-sector customers
Product type
A public website and a web application
Service
Website and application accessibility audit and remediation planning
Standard
WCAG 2.1 Level AA
Scope
Real user flows on the public site and application, including forms, dynamic interfaces, and cross-browser behavior
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

The company came to us after a significant enterprise opportunity was lost. Reviewers had asked for current documentation, and the organization did not have a recent, test-backed report to provide.

That experience made a wider issue visible. Accessibility work was happening only after a buyer asked, which left the company exposed in later enterprise and public-sector reviews. There was no tested baseline to draw on when the next questionnaire arrived.

The scope covered the marketing site and signed-in application. Several flows could not be judged reliably by automated tools alone: dynamic and interactive interfaces, forms and field validation, task paths that depend on displayed data, and behavior that changed across browsers and devices.

The vendor needed an independent audit, concrete guidance for developers, and a way to bring accessibility into product and sales work instead of treating it as a last-minute obstacle.

Our approach

We ran a structured manual audit against WCAG 2.1 Level AA on the marketing site and signed-in application. Testers followed real user tasks and checked keyboard access. The audit was carried out on desktop and mobile using Firefox, Edge, Chrome, and Safari together with NVDA, JAWS, VoiceOver, and TalkBack, except on platforms the product did not support.

We then provided a prioritized remediation plan and worked with internal stakeholders on next steps. We ranked issues by user impact. The guidance was written for the development team and described repeated interface patterns, including forms, navigation, semantics, and labeling. The goal was a cycle the team could follow as the product changed: audit, remediate, and retest rather than start over at the next buyer request.

After the initial delivery, we continued to provide advisory support, further validation, and documentation assistance.

What we found

Findings clustered in recurring areas: forms, navigation, semantics, labeling, and dynamic updates.

  • Forms had issues with labels, required fields, and error handling.
  • Navigation barriers appeared in skip links and menus.
  • Some buttons were built as divs, and pages were missing landmarks or list structure.
  • Icon-only buttons and vague link text, such as “click here,” did not describe their purpose.
  • Dynamic alerts were not announced.

Automated tools were not sufficient for the more interactive flows. Dynamic interfaces, form validation, and task paths that depend on displayed data needed manual review with a screen reader and keyboard, and they needed to be checked in more than one browser. Those were the areas where a baseline mattered most because they were also flows buyers were likely to ask about.

Outcome

The company went from being unprepared when accessibility arose in an evaluation to having a clearer, test-backed baseline and a remediation plan developers could use. Issue verification focused on validating the issues the client corrected. We supported that process and drafted a roadmap. We also prepared Accessibility Conformance Reports on the VPAT 2.5 INT template. Current VPAT materials could then be shared earlier in procurement conversations instead of being assembled after a request appeared.

Legal, product, and business stakeholders also had a more shared view of the work. Accessibility was no longer only a compliance task or a sales problem that appeared at the end of a deal. It became connected to product planning and improving the platform over time. Current accessibility documentation supported later enterprise opportunities moving forward.

What this means for SaaS teams after a lost opportunity

If a buyer asks for current documentation and the vendor cannot show how the product was tested, the review can stop there. A useful response is not a quickly assembled form. It is an audit of the actual site and application, a remediation plan that begins with the patterns users encounter first—often forms, navigation, and labeling—and a retest of the fixes. A written remediation plan helps a product team turn findings into work it can schedule.

Once that baseline exists, sales and legal teams can include current documentation in later conversations instead of reacting under pressure. The value is as much in the follow-through as in the first audit: a method for re-evaluating the product and updating the documentation as it changes.

Work with us on an audit and remediation plan

If a lost opportunity has exposed a gap in your documentation, we can help you establish a tested baseline and plan the next stage of work.

Related pages: website and application accessibility audits, software accessibility, and building an accessibility remediation plan.

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

E-commerce Accessibility Audit: Testing the Shopping Journey

All accessibility case studies

Client names and identifying details have been omitted or generalized to protect confidentiality.