Case Study

Making Accessibility Standard Practice

A multi-phase accessibility audit that surfaced 200+ issues and turned a one-time fix into a permanent part of how our team estimates and builds projects.

Client Oracle Consulting / PLCB
Role Accessibility Lead
Key Outcome 200+ accessibility issues resolved

The Challenge

Accessibility was an afterthought in our organization's process for too long. Despite the fact that we were building customer-facing web products for large organizations, accessibility compliance wasn't systematically factored into estimates, development workflows, or QA processes.

I initiated and led a comprehensive accessibility audit as part of an important customer engagement, with the goal of building a process that could be ported to future projects.

Output from the Oracle Accessibility Toolbar showing a list of accessibility violations

Output from Oracle's internal accessibility evaluation tool – one of several tools used during Phase 1 of the audit

The Audit Process

I structured the audit in two phases:

  • Phase 1 – Automated scanning: A member of the design team reviewed both the B2C and B2B PLCB sites using browser-based accessibility plugins. This surface-level scan caught the most obvious issues – missing alt text, poor color contrast, unlabeled form fields – and gave us a baseline count.
  • Phase 2 – Manual screen reader review: Design and QA team members followed up with in-depth manual reviews using screen readers (VoiceOver on macOS and NVDA on Windows).

In total, the team found over 200 issues across the project.

Beyond the Audit: Building a Process

I led the development of two lasting process changes. First, we began org-wide accessibility training, including the "why" behind accessibility requirements.

Second, I revised our project estimating process to include dedicated accessibility development and testing time on every new engagement. Previously, this work had been invisible in estimates – it either didn't happen or came out of development and QA's general time budget, which meant it got deprioritized.

What I Learned

The lesson from this project isn't really about accessibility specifically. It's about the need to continually push to build broader practice changes. Even after the success of this effort, subsequent accessibility estimates have been called into question by leadership. Having this success to remind everyone of the value properly addressing accessibility is a big step forward for our team.