A mobile app is redesigned so all controls can be operated with a single thumb, primarily to accommodate users with permanent motor disabilities. Who else benefits from this change?
AOnly users who have disclosed a permanent motor disability
BOnly users who have explicitly enabled accessibility settings
CA broad range of users — including people holding an object, commuters gripping a handrail, parents holding a child, and users wearing gloves
DNo one — optimizing for one-handed use reduces usability for the two-handed majority
This is the curb-cut effect: designing for a permanent disability case produces benefits for a much larger population with temporary or situational constraints. One-handed use is needed by many people in ordinary situations that have nothing to do with disability. Inclusive design consistently shows this pattern — solving for the edge improves the center, rather than trading off one against the other.
Question 2 Multiple Choice
A product team says they will add 'accessibility features' once core development is complete, treating them as a polish layer at the end of the project. A colleague objects. The colleague is most correct because:
ALegal requirements mandate accessibility be addressed before any public launch
BRetrofitting accessibility after design is finalized is far more costly and less effective than designing inclusively from the start
CAccessibility features require a dedicated budget line that must appear in the initial project proposal
DAccessibility testing takes longer than functional testing and must be front-loaded to meet deadlines
Inclusive design treats diversity as a design input from the beginning, not an accommodation added at the end. When accessibility is retrofitted, it typically requires restructuring information architecture, redesigning interaction patterns, and rewriting content — changes that are expensive because they fight against already-locked decisions. Designing inclusively from the start costs less and produces better outcomes because diverse needs inform the design while it is still malleable.
Question 3 True / False
Designing for users with permanent disabilities often also improves the experience for users facing temporary or situational constraints, such as a broken arm or a noisy environment.
TTrue
FFalse
Answer: True
This is the core principle behind the curb-cut effect. Disability is situational and contextual: a wheelchair user has a permanent constraint, a new parent has a temporary constraint (baby in one arm), a cyclist has a situational constraint (hands on handlebars). Designing for the permanent case — ramps, one-handed controls, captioned audio — serves all three. Inclusive design consistently produces this broadening effect.
Question 4 True / False
Inclusive design is primarily about achieving WCAG compliance and meeting legal accessibility requirements to avoid liability.
TTrue
FFalse
Answer: False
WCAG compliance is accessibility — a necessary baseline focused on disability. Inclusive design extends further: it addresses language, culture, age, literacy, technology constraints, and economic circumstances, treating the full range of human diversity as a design input rather than an afterthought. Compliance asks 'does this technically work for disabled users?'; inclusive design asks 'does this work well for everyone across real contexts of use?' Compliance is the floor, not the ceiling.
Question 5 Short Answer
What is the 'curb-cut effect,' and why does it suggest that designing for marginalized or constrained users benefits everyone?
Think about your answer, then reveal below.
Model answer: The curb-cut effect is named after the sidewalk ramps mandated for wheelchair users that turned out to benefit a much wider population: parents with strollers, travelers with luggage, cyclists, and delivery workers. The pattern generalizes: solving a design problem for a user facing a permanent, severe constraint often produces a solution that is better for everyone because it removes friction that was always present but tolerable for more-privileged users. Disability is situational — the same constraint that is permanent for one person is temporary or situational for many others.
This is the business and ethical case for inclusive design in one argument: it's not about trading off quality for accommodation, it's about discovering that constraints are universal and that designing for the hardest case makes the average case better. Organizations that internalize this stop asking 'how do we accommodate these edge cases?' and start asking 'what are we missing by not including these perspectives?'