What accessibility means in a product
A product is accessible when people with a wide range of abilities can use it, whether they can see, hear, move, remember or concentrate in the ways a designer might assume or not. Some of those differences are permanent, such as blindness or limb loss. Others are temporary, such as a broken wrist, or situational, such as carrying a baby in one arm or using a device in bright sunlight.
Seen this way, accessibility is not a niche. Nearly everyone is limited at some point, and nearly everyone ages. Features that help one group, such as large controls or captions, often make a product easier for everyone. That is the idea behind inclusive design: aim for a flexible product rather than a special version for a “special” user.
Accessibility also overlaps with law and standards in many places, especially for software, public services and some regulated goods. Rules differ by region, so treat this article as general information, not legal advice.
Start from the range of abilities
It helps to think in broad categories, remembering that real people rarely fit one neatly.
- Vision: blindness, low vision, color blindness, sensitivity to glare. Red-green color blindness is the most common form and is more often found in men than women.
- Hearing: deafness, hearing loss, or simply a loud room.
- Movement and strength: tremor, limited reach, arthritis, one-handed use, low grip strength.
- Thinking and memory: attention differences, dyslexia, learning disabilities, stress, or being tired.
- Speech and communication: conditions that make voice controls unreliable.
Studying the physical side of this overlaps with human factors, which looks at how hands, arms and bodies actually interact with objects. Accessibility extends that work to people at the edges of the range, not only the middle.
Core principles
Offer more than one way
A single signal fails someone. A device that only beeps excludes a person who cannot hear it; one that only flashes a light excludes someone who cannot see it. Pairing light, sound and touch (a vibration, a raised edge) lets people use whichever channel works for them. Labels that combine text, an icon and a shape do the same job.
Do not rely on color alone
If a status light is only red or green, some users cannot tell the states apart. Add a shape, position, label or pattern. For text and important symbols, aim for strong contrast with the background. Many accessibility guidelines for screens suggest a contrast ratio of at least 4.5 to 1 for normal-sized text, which is a useful reference point even for printed labels, though lighting changes the real result. How color shapes mood and meaning is a separate topic, covered under color psychology.
Make controls forgiving
Small buttons placed close together, or controls that need a precise twist, are hard for people with tremor or limited dexterity. Larger targets, space between them, and controls operable with a fist or one hand all help. Avoid requiring two hands at once or sustained pressure unless it is a deliberate safety feature.
Keep it simple and predictable
Clear structure and consistent behavior reduce the load on memory and attention. Use plain words, put similar things in similar places, give feedback after every action (“it clicked”, “it saved”), and make errors easy to undo. A product that is intuitive for someone distracted or stressed is usually easier for everyone.
Allow for different body sizes and postures
People use products seated, standing, in a wheelchair or leaning on a counter. Think about reach, height, and whether a user can see a display from where they actually are. Where a single fixed dimension cannot suit everyone, an adjustable one can.
Tell people how to use it
Even a well-designed product needs instructions that people can follow. Good product instructions use plain language, clear pictures and large type, and are available in more than one format where possible, such as printed and online with text that screen-reading software can handle.
Accessibility in electronics and maker projects
Makers often build for themselves first, but small choices carry over when a project is shared or sold. A few examples:
- Choose switches and knobs that are easy to find by touch.
- Make indicators visible from a distance and readable without relying on color.
- Provide sound alongside lights, and the reverse, where it makes sense.
- Avoid timing that is too tight; give people time to respond.
- Make enclosures that are easy to open for battery changes only if that is safe, and keep anything hazardous out of reach.
Accessibility must never override safety. A feature that reduces force needed for a latch, for instance, should not weaken a guard that protects fingers. Read up on product safety before changing anything that protects the user.
Test with real people
Checklists and guidelines are a start, but they cannot predict everything. People with disabilities are the real experts on their own experience, and a design team without that perspective will miss problems. Bring them into the process early, not just at the end.
A simple approach:
- Start with user interviews to learn how people already cope with similar products and what frustrates them.
- Build rough versions early. A model made with cheap cardboard prototyping materials is enough to test handle sizes and reach.
- Run usability testing sessions where participants try realistic tasks while you watch and listen without helping.
- Record where people hesitate or fail. Treat those moments as design problems, not user mistakes.
- Change the design and test again.
Be respectful and honest. Explain what you are testing, make clear that the product is being tested rather than the person, pay or thank participants fairly if you can, and never claim a product is “fully accessible” after a handful of sessions. Needs vary widely, and no product suits everybody.
Common mistakes
- Treating accessibility as an add-on at the end, when changes are expensive.
- Designing for an imagined “average” user and ignoring the edges.
- Assuming one accessibility feature covers all needs.
- Testing only with colleagues or friends who have the same background as the designer.
- Making an “accessible version” that looks different or costs more, which can feel stigmatizing.
A realistic mindset
Perfect accessibility is not achievable, and chasing it can stall a project. A better aim is steady improvement: understand who might be excluded, fix the biggest barriers first, listen to feedback and keep going. Each time a decision in the design process is checked against the question “who might struggle with this?”, the final product tends to get a little better for everyone.