Introduction to inclusive design

(an excerpt from the Inclusive Design module for federal employees)

One of the foundational principles of human-centered design (HCD) is to “start from user needs.” Another closely related principle is “you are not your user.” In other words, you can't assume that the people you're designing with, and for, want and need what you want and need. This is why research, prototyping and testing are key practices of HCD.

Human-centered

The humans in “human-centered” are a diverse bunch: in languages and literacy, race, ethnicity, culture, gender, age, sexual orientation, geographic location, access to resources like time and money, access to reliable internet, digital literacy… And all of these identities and contexts intersect with one another and with different and evolving abilities, aspirations and needs, over time.

Design

If we can agree on one basic definition of “design” it is, as I mentioned earlier, a series of intentional decisions. Every decision designers make either raises or lowers barriers to accessing, understanding, and effectively using a product or service.

In government, these products and services are not just “nice to haves,” they are essential to people’s lives and well-being. Being a responsible designer in this system means you can’t design for just some of the users some of the time. Inclusive practices help ensure more effective design outcomes that serve more people’s needs.

The legal standards of accessibility (for example, “508 compliance”) are the ground floor, a baseline minimum. We can aim to expand beyond “access” to inclusion, full participation, easier interactions, and dignified, respectful experiences.