What is Accessibility?

TL;DR

• Accessibility means designing products so people with different abilities can use them.
• It includes visual, motor, auditory, cognitive, and situational needs.
• Accessibility is not the same as usability, although the two overlap.
• Keyboard access, contrast, semantics, labels, focus, and error handling all matter.
• Automated checks help, but they do not replace human review and user testing.

What does accessibility actually mean?

Accessibility asks whether a person can successfully perceive and operate a product even when they do not interact with it in the way the designer first imagined.

A user might navigate only with a keyboard, rely on a screen reader, need larger text, have low color vision, use voice input, or be working with one hand on a crowded train. Good accessibility reduces unnecessary barriers across all of those contexts.

What does accessible product design include?

Perceivable information

Text, controls, status, and media need alternatives that people can perceive. Examples include sufficient contrast, meaningful alt text, captions, and visible focus.

Operable interactions

Important tasks should not depend on a mouse alone. Keyboard navigation, sensible focus order, target size, and enough time to complete tasks are common concerns.

Understandable behavior

Labels, validation, navigation, and errors should behave consistently and use clear language.

Robust semantics

Interfaces should expose enough structure that assistive technologies can interpret headings, controls, relationships, and state.

Accessibility vs. usability

Usability asks how effectively and efficiently intended users can complete tasks. Accessibility asks whether people with disabilities and different access needs can use the product at all.

A product can be easy for one group and inaccessible to another. Strong teams evaluate both.

How do teams improve accessibility?

1. Use semantic components and labels from the start.
2. Check color contrast and text scaling.
3. Test keyboard-only navigation and focus order.
4. Make status and errors available without color alone.
5. Use automated tools to catch obvious violations.
6. Review important flows with assistive technology.
7. Include people with disabilities in research where possible.

Common accessibility mistakes

Treating accessibility as a final QA pass

Late fixes are harder because accessibility affects structure and interaction, not only color.

Assuming automated checks are enough

Tools can flag many technical problems but cannot fully judge whether an experience makes sense.

Removing visible focus

A keyboard user needs to know where they are.

Using placeholder text as the only label

Labels need to remain available after a user starts typing.

Frequently asked questions

Is accessibility only for permanent disabilities?

No. Temporary and situational constraints can create similar needs.

Does accessible design make products worse for everyone else?

Usually the opposite. Clear labels, larger targets, better focus, and stronger error handling often improve the experience broadly.

The bottom line

Accessibility asks a simple question: who is prevented from using this product because of how we designed it?

The goal is to remove avoidable barriers before they become part of the product.

Related terms

Usability · UX design · User interface · Interaction design

Relevant Figr resource

Read UX Design Principles for the broader principles that support accessible product design.