duo-inclusive-access

Stop your product filtering people out on circumstance instead of ability. Covers removing preconditions (location, hardware, contiguous free time), building escape hatches at the level of the blocked capability rather than the session, putting scaffolding on user-controlled toggles, never penalising slips you were not measuring, letting the user own the turn boundary in conversational interfaces, and auditing fairness against delivery context — device, screen size, connection — not just demographics. Use when someone asks who literally cannot use this, is this requirement measuring ability or access, should this be a setting or a change to the completion rules, should the free tier be a weaker product, how do we make onboarding accessible, or how do we build for a community nobody on the team belongs to.

Version

2.0.0

License

MIT