MVP accessibility checklist

Set an accessibility boundary before design hardens

Identify the core users, contexts, target platforms and complete journey. Include disability-related needs in research and risk assessment rather than treating accessibility as a generic final audit. Choose the applicable internal standard and obtain qualified legal or domain advice where obligations depend on jurisdiction, sector or procurement. This guide is a delivery checklist, not legal advice.

Do not accept an MVP exemption by default. A deliberately narrow product can still use semantic controls, clear language, focus order and adaptable layout from its first implementation. Stop and seek specialist input when the journey involves safety, health, finance, employment, public service or another consequential domain, or when the team cannot interpret the relevant standard for a critical interaction.

Inventory the complete journey and content forms

List headings, landmarks, controls, forms, validation, tables, media, charts, gestures, drag interactions, time limits, authentication and dynamic updates. For each, record name, role, state, instructions and an equivalent way to complete the task where a modality would otherwise exclude users. Include empty, error, loading, success and recovery states, not just designed happy-path screens.

Create a baseline on representative devices and browsers using keyboard-only navigation, zoom and text resizing, high contrast or forced colors where relevant, screen-reader navigation and reduced-motion settings. Automated scanning can find some patterns but cannot judge whether reading order, labels, instructions or task outcomes make sense. Record tool versions, manual steps and observed barriers.

Plan fixes into components and acceptance criteria

Prioritise barriers that block the primary outcome, then repeated component defects and content issues. Put semantics, focus behavior, error association, contrast, touch target considerations, captions or text alternatives and responsive behavior into the component system. Avoid parallel accessible versions when one maintained interface can meet the need, because duplicate paths drift and create unequal functionality.

Add observable criteria to each relevant story and a product-wide accessibility gate to the definition of done. Assign design, content and engineering owners. Test early with real components rather than visual mockups alone. If user research with disabled participants is appropriate, design it ethically and compensate through the organisation’s normal research process without treating a small sample as universal proof.

Accept the critical journey with layered evidence

Combine standards-based automated checks, code review and manual tests. Verify keyboard or switch reachability, focus visibility and order, screen-reader names and announcements, zoom and text reflow, contrast, motion preferences, error recovery and platform accessibility services. Document environment, evidence, failures and exceptions. Passing an automated scan or one assistive-technology path is not complete accessibility proof.

Define acceptance as observable evidence. Examples include a tested user journey, an approved build, reproducible checks, an incident runbook and a verified handover. None of those proves retention, revenue or product-market fit. Keep delivery proof, external provider approval and business results as separate claims.

Carry accessibility into release and maintenance

Publish known limitations and an accessible support route when appropriate, with owners and review dates. Preserve test scripts, component rules and audit findings in the product systems and repeat critical checks after dependency, design-system or operating-system changes. Include accessibility in incident triage and handover. Monitor user feedback without exposing personal data or claiming that absence of complaints proves absence of barriers.

Keep source control, domains, stores, analytics, cloud organisations and production credentials under explicit organisational ownership. Grant scoped, revocable access and rehearse handover before the final invoice. The supplier label matters less than whether another authorised person can inspect, deploy, recover and continue the product.

Decision criteria

Use the same questions for every option before choosing.