Workflows
Proven protocols to move accessibility from “Audit” to “Action.”
Accessibility fails when it is treated as a final check. I have designed these workflows to “Shift Left,” integrating compliance into the moments where decisions actually happen. These are the exact processes I use to ensure quality without sacrificing velocity.
The Vetting Workflow (Procurement)
How to choose third-party tools without inheriting their accessibility debt.
Before adding a new library, plugin, or widget to your project, follow this 3-layer audit protocol to protect your codebase:
The Documentation Audit
Review the vendor’s VPAT (Accessibility Conformance Report). If it claims “100% Support” without detailed remarks, treat it as a red flag.
The Automated Smoke Test
Run a diagnostic scan on the vendor’s live demo. If basic contrast or HTML structure fails here, the component is likely brittle.
The Manual Stress Test
Use the wA11y Vetting Guide to test keyboard traps and screen reader announcements.
Arrive at a clear Pass, Remediate, or Fail verdict before you commit to integration.
The Handoff Workflow (Design to Dev)
How to eliminate “guesswork” and create a clear contract for implementation.
A design isn’t finished until the accessibility intent is documented. This workflow ensures that developers have everything they need to build it right the first time:
Focus Order Mapping
Use annotations to show exactly how a keyboard user should move through the page.
ARIA Intent
Don’t just design a “dropdown”—document the expected aria-expanded and aria-controls behavior.
The State Matrix
Always provide mocks for Focus, Hover, Active, and Disabled states to avoid “default” browser overrides that might fail contrast.
The QA & Defect Workflow
How to validate the human experience and track progress.
Standardized testing prevents “subjective” bugs. Use this sequence to verify every release:
The 30/70 Rule
Use automated tools (like Axe) to catch the “low-hanging fruit” (30%), then dedicate your time to manual testing (70%) to verify logic and usability.
Standardized Bug Reports
Use the wA11y Bug Templates to ensure every ticket includes a WCAG reference and clear reproduction steps.
The “Release Gate” Logic
Define clear severity levels. If a defect prevents a user from completing a core task (a “Blocker”), the feature does not ship.
The Maturity Workflow (Strategy)
How to roadmap long-term organizational growth.
Use the W3C Maturity Model as your strategic compass. By auditing your processes across these dimensions, you can move your team from “Reactive” (fixing bugs) to “Proactive” (preventing them).
Gap Analysis
Identify the weakest dimension (e.g., Procurement or Communications).
