What inclusion looks like in practice
Inclusion in digital products is not a values statement on the About page. It is the answer to a series of small design decisions made every day: whose finger sizes the buttons are sized for, whose screen the contrast is checked against, whose connection speed the page assumes, whose language the copy is written in.
Done well, inclusion is invisible. Users complete their task without friction, regardless of how they arrived: screen reader, magnifier, switch input, voice control, two thumbs, one thumb, sunlight, baby on hip. Done badly, inclusion shows up in support tickets, abandoned carts, complaints to the regulator, and reputation in the disabled community.
Who gets included
21.4 percent of Australians live with disability. Add temporary impairments, ageing, and situational limitations and you reach almost the entire customer base, at least sometimes. Inclusion is not a minority concern. It is the design discipline that takes the existence of varied users seriously, and builds for them by default.
Why this is also organisational
Inclusive products tend to come from inclusive teams. Procurement processes that surface accessibility (see NSW procurement requirements), recruitment that doesn't filter out disabled candidates, internal tooling that supports assistive tech, leadership that knows what WCAG is - these are all part of the same picture.
Where to go next
- Business benefits
Inclusion as a commercial decision.
- Customer experience
What better looks like.
- Legal obligations
What the law expects.
- How we help
From audit to embedded practice.