Accessibility is about making technology work for everyone, regardless of ability

Accessibility means designing technology so that people with disabilities can use it just as effectively as anyone else. This includes people who are blind or have low vision, deaf or hard of hearing, have mobility limitations, cognitive differences, or any other disability. When a website, app, or device is accessible, it works with assistive tools like screen readers, voice control, and magnification software — and it doesn't require workarounds or extra steps that non-disabled users don't have to take.

Accessibility is not a feature you turn on. It is built into how something is designed from the start. A truly accessible product works well for everyone: a video with captions helps not just deaf viewers but also people watching in a noisy room or a language they are still learning. A website that works with keyboard-only navigation helps people with mobility disabilities and also people who simply prefer keyboards. Accessible design makes technology faster and clearer for everyone.

Key Takeaways

  • Accessibility means people with disabilities can use technology without extra difficulty or workarounds that non-disabled users do not face.
  • Common accessibility features include captions, screen readers, voice control, high contrast modes, and keyboard navigation.
  • Accessible design benefits everyone — captions help in noisy environments, large text helps people with aging eyes, and voice control works when your hands are full.
  • Many countries have laws requiring websites and apps to meet accessibility standards, particularly those run by government or serving the public.
  • You can check whether a device or app is accessible by testing it with the assistive tools you use or by reading its accessibility documentation.

How accessibility differs from universal design

Universal design means building something that works well for the widest possible range of people from the start, without needing special versions or add-ons. Accessibility is narrower: it focuses specifically on removing barriers for people with disabilities. Both are important, and they overlap significantly.

A ramp is accessible — it lets someone in a wheelchair enter a building. But a building designed with universal design might have a gentle slope from the street, so the ramp is barely noticeable and everyone benefits from it, not just wheelchair users. A video with captions is accessible. A video with captions, transcript, and audio description is more universally designed because it serves deaf viewers, blind viewers, people learning the language, and people who want to search the text later.

The main categories of accessibility

Accessibility breaks down into several overlapping areas, each addressing different types of disability:

  • Visual accessibility helps people who are blind, have low vision, or are colorblind. This includes screen readers (software that reads text aloud), magnification tools, high contrast modes, and text descriptions of images.
  • Hearing accessibility helps people who are deaf or hard of hearing. This includes captions on videos, transcripts of audio content, and visual alerts instead of sound-only notifications.
  • Motor accessibility helps people with limited hand strength, tremors, or who cannot use a mouse. This includes keyboard navigation, voice control, switch access (using a single button to control a device), and customizable button sizes.
  • Cognitive accessibility helps people with dyslexia, ADHD, autism, intellectual disabilities, or other cognitive differences. This includes clear language, consistent layouts, extra time to complete tasks, and the ability to turn off animations or distracting elements.

A single person may need features from multiple categories. Someone who is deaf and uses a wheelchair needs both hearing accessibility and motor accessibility. Someone with dyslexia may benefit from text-to-speech (hearing accessibility tools) even though their primary disability is not hearing-related.

Where accessibility requirements come from

Many countries have laws requiring certain organizations to make their technology accessible. In the United States, the Americans with Disabilities Act (ADA) requires government websites and many public-facing businesses to meet accessibility standards. The Section 508 amendment requires federal agencies and contractors to follow accessibility rules. The Web Content Accessibility Guidelines (WCAG), published by an international standards organization, set the technical benchmarks most laws reference.

The European Union, Canada, Australia, and many other countries have similar laws. However, requirements vary by country, by industry, and by whether an organization is public or private. A small business website may not be legally required to be accessible in all places, but a hospital or government office almost always is. Even where not legally required, many organizations make accessibility a priority because it expands who can use their product and reduces the risk of lawsuits.

What accessibility looks like in practice

On a website, accessibility might mean that every image has a text description so a screen reader can explain it to a blind user. Form fields are labeled clearly so someone using voice control knows what to say. The site works with keyboard alone — you can tab through links and buttons without a mouse. Text is large enough to read without magnification, and colors have enough contrast that someone with low vision or colorblindness can tell them apart.

On a smartphone, accessibility might mean that an app works with VoiceOver (on iPhone) or TalkBack (on Android) — built-in screen readers that read the screen aloud. Buttons are large enough to tap accurately. Videos have captions. You can adjust text size without breaking the layout. You can turn off animations if they cause dizziness or distraction.

In a physical device like a printer or ATM, accessibility might mean buttons are labeled in Braille, the screen has high contrast, and the device works with a keyboard or switch as well as a touchscreen.

How to know if something is accessible

The most direct way is to test it yourself using the assistive tools you rely on. Does the website work with your screen reader? Can you navigate using only your keyboard? Are the captions accurate and complete? If you do not use assistive tools but want to check accessibility for others, most organizations publish an accessibility statement — a page that describes what features they support and what they are working to improve.

You can also look for third-party certifications or audit reports. Some organizations hire accessibility consultants to test their products and publish detailed reports. However, a certification or audit is only as current as its date — accessibility can break when a website is updated or a new version of an app is released.

If you find that something you need to use is not accessible, you can report it to the organization. Many have accessibility feedback forms or contact information for accessibility teams. In some cases, particularly with government websites or services, you may have legal recourse if accessibility barriers prevent you from using something you are may have access to to access.

Accessibility as an ongoing process

Building accessibility into technology is not a one-time task. When a website adds a new feature, that feature needs to be accessible too. When an operating system updates, accessibility tools need to keep working. When a company hires new developers, they need training in accessible design. This is why many organizations have accessibility teams or officers whose job is to keep accessibility working across all their products.

The field of accessibility is also always changing. New assistive technologies emerge, new disabilities are better understood, and new standards are published. What counts as "accessible" today may be considered a bare minimum in five years. Organizations that treat accessibility as a permanent part of their work, not a box to check once, tend to do better at serving disabled users over time.

Frequently Asked Questions

Does accessibility cost a lot to add to a website or app?

Building accessibility in from the start costs less than adding it later. If accessibility is part of your design process from day one, it is often just good practice — clear labels, keyboard navigation, and semantic code. Retrofitting an inaccessible product can be expensive because you may need to rebuild parts of it. Many organizations find that the cost is worth it because it expands their user base and reduces legal risk.

If something is accessible, does it work worse for non-disabled people?

No. Accessible design typically makes technology work better for everyone. Captions help in noisy environments. Large, clear text is easier to read. Keyboard navigation is faster for many people. High contrast modes reduce eye strain. The only exception is when accessibility features are poorly designed, but that is a design problem, not an accessibility problem.

Can I request accessibility features for a product I use?

Yes. Most organizations have accessibility feedback channels — a contact form, an email address, or a support ticket system. Be specific about what you need and why. If many users request the same feature, organizations are more likely to prioritize it. If a product is required for your job or education and lacks critical accessibility features, you may also have legal grounds to request accommodations.

What is the difference between accessibility and accommodations?

Accessibility is built into the product itself — everyone benefits from it. An accommodation is a change made for a specific person because the product is not accessible enough. If a website is fully accessible, no accommodations are needed. If it is not, you might request an accommodation like a human-written transcript of a video. Ideally, accessibility makes accommodations unnecessary.

Are there accessibility standards I should know about?

The most widely used standard is the Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium. WCAG 2.1 is the current version and covers websites and apps. It has three levels: A (basic), AA (standard), and AAA (enhanced). Most laws and organizations aim for AA compliance. If you are building something or checking whether a product meets standards, WCAG is the benchmark to reference.