Accessibility - Always
Accessibility — Making WCAG 2.1 AA the Default, Not a Deadline
______________________________________________________________________________________
Case Study Snapshot:
Summary:
Accessibility-by-design: WCAG 2.1 AA baked into the design system
Goal: Make WCAG 2.1 AA the default behavior of our enterprise UI—so accessibility isn’t a late-stage audit scramble.
What I did: Institutionalized an accessibility operating model by embedding accessible behavior into shared components and standards—keyboard interaction patterns for dense panels, token-driven high-contrast mode, and pre-engineered semantics/states with guardrails teams couldn’t accidentally break.
Impact: Reduced audit churn and compliance “paperwork UX,” prevented regressions by standardizing patterns in shared components, and enabled faster shipping of inclusive experiences without specialist bottlenecks.
______________________________________________________________________________________
Context:
In dense enterprise applications, accessibility isn’t a checkbox—it’s operational usability. When screens are complex and decisions are time-sensitive, the UI has to work for every user, every time, across input methods and visual needs.
Problem:
Accessibility was being treated as a late-stage quality gate. That created predictable failure modes:
Audit overhead: extra handoffs and compliance documentation
Regressions: fixes didn’t stick because patterns weren’t standardized
Inconsistency: each team interpreted requirements differently
Deadline rework: retroactive remediation after UI was already built
Strategy: Accessibility-by-design (WCAG 2.1 AA):
I institutionalized an accessibility-by-design operating model company-wide by embedding WCAG 2.1 AA standards into the foundation of our design system. Instead of policing compliance after the fact, we made the system itself do the work.
This shifted accessibility from “an expert task” to an automatic property of every component—so designers and engineers shipped inclusive UI by default, not by exception.
My role:
Operating model + standards definition
Design system requirements + governance
Partnering with engineering on implementation patterns
Rollout/adoption plan + measurement
Applied to 30 product teams / dozens of components
What we built (the hard parts):
Keyboard model for dense panels: predictable focus order, escape hatches, and interaction patterns that worked across high-density layouts (tables, filters, property panels, toggles).
High-contrast mode: token-driven theming and states that remained legible and unambiguous across dark UI, charts, alerts, and selection states.
Pre-engineered semantics and states: components designed with accessible names/labels, roles, error messaging patterns, and non-color-only status communication.
Guardrails + usage guidance: documentation that prevented teams from “breaking” accessibility during composition and implementation.
Performance constraints in high-density UIs
Inconsistent team implementation patterns before standardization, used tokens
Artifacts:
Design tokens spec (contrast tokens + state tokens)
Keyboard model diagram (focus order + escape hatches + expected shortcuts)
Component anatomy example (labeling, error messaging pattern, non-color-only status)
Documentation screenshot (the guardrails you mention
Impact:
Reduced accessibility artifacts required to prove compliance (less audit churn and “paperwork UX”).
Fewer regressions because accessible behavior lived in shared components, not scattered one-off implementations.
Faster, more confident shipping of inclusive experiences—without slowing teams down or relying on specialist intervention.
Audit findings: 200+ issues before vs. after
Regression rate: accessibility bugs reopened/reintroduced per release dropped to less than 10%
Delivery speed: time to remediate accessibility issues measured in "hours" as opposed to "days"
Coverage: 100% of UI built from compliant shared components
Why it matters:
This wasn’t a compliance effort. It was a delivery strategy: by baking WCAG 2.1 AA into the design system, accessibility became repeatable, scalable, and durable—raising quality across the product while removing friction from the development lifecycle.