Product Managers & Strategy
Accessibility starts at the definition phase.
Treating accessibility as a “fast follow” or tech debt creates compounded costs later in the development lifecycle. To build truly inclusive products, accessibility must be a first-class citizen in your product roadmap, requirement definitions, and procurement choices.
Strategic Planning: 4 Key Pillars
Budget for Audits
Allocate time and budget for external accessibility audits (VPATs) before major releases
Shift Left
Include accessibility checks in design reviews before a single line of code is written
Define MVP
Make "Keyboard Accessible" and "Screen Reader Compatible" non-negotiable launch criteria for any MVP
Vendor Checks
Don't inherit barriers. Require accessibility compliance from all third-party tools and vendors
Requirements & Procurement
How to operationalize inclusion in your daily workflows
User Stories
Developers need clear acceptance criteria. Use the “As a… I want… So that…” format to include disability scenarios.
- Example: “As a keyboard user, I want visible focus on buttons…”
- Checklist: Tab order, focus states, alt text.
Procurement (VPATs)
When buying or renewing software, request a VPAT or Accessibility Conformance Report (ACR).
Ensure WCAG 2.2 Level AA requirements are documented and escalate risks early.
Accessibility-ready Definition of Done includes keyboard access, focus visibility, error handling, and basic screen reader checks.
Example User Stories
Keyboard Navigation
“As a keyboard-only user, I want to be able to close the modal using the ESC key so that I am not trapped in the overlay.”
Screen Reader Feedback
“As a screen reader user, I want to hear a confirmation message when I save my settings, so that I know the action was successful.”
Acceptance Criteria Checklist
All interactive elements are reachable via Tab key
Focus state is clearly visible (consistent with design system)
Images have appropriate alt text defined
Error messages are associated with their respective inputs programmatically
Vendor Procurement
When buying third-party tools (chatbots, HR software, video players), you are responsible for their accessibility on your site. Don’t inherit barriers.
Request a VPAT / ACR
Ask vendors for their Voluntary Product Accessibility Template or Accessibility Conformance Report. If they don't have one, it's a red flag.
Contract Clauses
Include language in your MSA (Master Services Agreement) requiring the vendor to remedy accessibility defects within a specific timeframe (e.g., 30-90 days).
Verify Claims
Don't just trust the documentation. Have your internal accessibility team do a quick "smoke test" of their product demo.
References
Accessibility Statements
Instructions for creating a public commitment to inclusion and a feedback mechanism for users
ROI & Business Case
Data and stats to help justify the investment in accessibility to stakeholders.
Legal Risk
Understanding the legal landscape (ADA, AODA, Section 508) and compliance requirements.
