inclusive-design

# Inclusive Design Inclusive design answers a different question from accessibility: > **Does this respect the real-world context, identity, language, culture, device, confidence level, and constraints of the person using it?** Accessibility asks whether someone *can operate* the interface with their abilities and assistive tools. Inclusion asks who gets *left out* by the assumptions baked into the product — the person on a $40 phone over a metered 2G connection, the person whose name doesn't fit your form, the person reading in their third language, the person who has never done this online before and is afraid of getting it wrong. WCAG conformance does not address any of that. This skill does. Per W3C, accessibility, usability, and inclusion overlap but each has a distinct focus: accessibility targets **disability**, usability targets the **quality of the experience** (effective, efficient, satisfying), and inclusion targets the **full breadth of human diversity** — hardware and software, literacy, economic situation, education, geography, culture, age, and language. ## When to use Use this skill when the work is about *who you might be excluding and why* — not about a specific assistive-tech bug. Triggers: reviewing a design "through an inclusive lens," building personas, internationalization/localization, designing name/address/profile forms for a global audience, supporting low-end devices or poor connectivity, lowering cost/data barriers, onboarding nervous or fir...