What web accessibility is, who it helps and why it pays off

A website is accessible when people can use it whatever their eyesight, hearing, hands, attention or circumstances. Picture a customer who listens to your shop instead of looking at it, a retiree who zooms in to read your prices, someone filling in your contact form with one hand because the other is in a cast. This article explains what that means in practice, who it is for, why it pays off and how to start without turning it into a huge project.

What "accessible" means in practice

Accessibility is not a special version of your site. It is your normal site, built so that nobody gets stuck. The people who benefit most are a much broader group than many site owners expect.

People who are blind or have low vision. Many use a _screen reader_, software that reads the page aloud or sends it to a braille display. Others zoom in to 200% or more, or switch on high-contrast colours. They need text descriptions of images, clear headings and text that stays readable when enlarged.
People who are deaf or hard of hearing. They need captions on videos and a written alternative for audio, such as a transcript of a podcast.
People with motor disabilities. Some cannot use a mouse and move through a page with the keyboard alone, pressing Tab to jump from link to link. Others use a _switch_, a single large button, or voice control. Every link, button and form field has to be reachable and usable without a mouse.
People with cognitive or learning disabilities, such as dyslexia, ADHD or memory problems. Plain language, a predictable layout, clear error messages and no tight time limits make the difference.
Older people. Eyesight, hearing and fine motor control tend to change with age. Small grey text and tiny buttons are often the first obstacles.
Everyone, some of the time. A broken arm, a migraine, bright sunlight on a phone screen, a noisy train where you cannot hear a video, a baby on one arm while you try to pay a bill. Microsoft's inclusive design team calls these temporary and situational limitations: designing for a person with one arm also helps the person with an arm injury and the new parent holding a child.

How many people we are talking about

According to the World Health Organization, an estimated 1.3 billion people, about 1 in 6 people worldwide, live with a significant disability. The WHO also expects that by 2030, 1 in 6 people in the world will be aged 60 or over.

Closer to home, Eurostat reports that in 2024, 23.9% of people aged 16 and over in the EU said they had a long-standing limitation in their usual activities because of a health problem. That is almost one in four adults. The share rises steeply with age, to 72.3% among people aged 85 and over.

Meanwhile, most websites still have basic barriers. WebAIM's 2026 analysis of the home pages of the top one million websites found detectable problems on 95.9% of them, with an average of 56 errors per page. The most common problems are familiar and fixable: text with too little contrast (on 83.9% of home pages), images without a text description (53.1%), form fields without a label (51%) and links or buttons without a name.

The four principles, in plain words

The international reference for accessible websites is WCAG, the Web Content Accessibility Guidelines published by the W3C, the body that also sets web standards. The current version, WCAG 2.2, became a W3C Recommendation in October 2023. All of its requirements are grouped under four principles.

Perceivable: people can take in the content

Information should not depend on one sense only. Everyday example: a photo of a product needs _alt text_, a short written description that a screen reader reads aloud and that appears if the image fails to load.

<img src="rain-jacket.jpg" alt="Red rain jacket with hood, seen from the front" />

The text between the quotes after alt= is what a blind visitor hears instead of seeing the picture. Most site builders have a field called "alt text" or "image description" where you type it, so you rarely need to touch code. Captions on videos and enough _contrast_ (the difference in brightness between text and its background) belong under this principle too. WCAG asks for a _contrast ratio_ of at least 4.5 to 1 for normal text, which rules out light grey on white.

Operable: people can use every part of it

Every function must work for people who do not use a mouse or a touch screen. Everyday example: put your mouse aside and press Tab on your own site. You should see a clear outline move from link to link, and you should be able to open the menu, fill in the form and press "Send" with the keyboard alone.

Understandable: people know what is going on

Text is clear, pages behave predictably and forms help people recover from mistakes. Everyday example: when someone enters a phone number in the wrong format, the message says "Enter your phone number with digits only, for example 0470123456", next to the field, instead of a red border and "Invalid input" at the top of the page.

Robust: it works with the tools people use

Your site should work in different browsers and with assistive technology such as screen readers, magnifiers and voice control. Everyday example: a "Buy" button that is built as a real button is announced as "Buy, button" and can be pressed by voice command. A button that only _looks_ like one, made from a styled box, may be silent for a screen reader and impossible to reach with the keyboard.

Why it pays off

Accessibility is often framed as a cost. In practice, most of the work also improves things you already care about.

A bigger audience. With nearly one in four adults in the EU reporting a long-standing limitation, and populations ageing, a site that excludes them leaves customers and readers behind.
Overlap with search engines. Google's own guidance says it uses alt text, together with the page content, to understand what an image shows. Clear headings, descriptive link text such as "View opening hours" instead of "Click here", and well-structured pages help search engines and screen reader users in similar ways.
Better usability for everyone. Captions help in quiet offices and loud trains. Good contrast helps on a phone in the sun. Clear forms help people in a hurry.
Fewer support questions. When forms explain what they need and pages are easy to follow, fewer people email or phone to ask how to place an order or book an appointment.
Legal duties. Since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) requires many businesses that sell certain products and services to consumers, such as online shops, banking, e-books and passenger transport tickets, to make them accessible. Micro-enterprises providing services, with fewer than 10 employees and an annual turnover or balance sheet total of no more than 2 million euros, are exempt from the service requirements. Public sector websites already had their own rules. Whether and how the law applies to you depends on your situation, so check with a legal adviser for your specific case.

Four myths worth dropping

Blind visitors are an important group, but they are one of many. Keyboard users, people with dyslexia, older visitors, people with a hearing loss and anyone in a temporary or situational limitation all benefit from the same work.

"It makes design ugly"

Accessible design is mostly good design: readable text sizes, sufficient contrast, clear focus outlines, consistent navigation and generous click areas. It limits a few choices, such as pale grey text on white, but it does not dictate a style.

Overlays are plug-ins that add a toolbar or an "accessibility" icon to your site and promise to repair problems automatically. They cannot. They do not know what your photos show, cannot rewrite unclear instructions and cannot rebuild a menu that does not work with a keyboard. Many people who rely on assistive technology already have their own settings, and an overlay can get in their way. In 2023 the European Disability Forum and the International Association of Accessibility Professionals stated jointly that overlays do not make websites accessible or compliant with European legislation. In January 2025, the US Federal Trade Commission ordered overlay maker accessiBe to pay 1 million dollars over claims that its tool could make any website compliant with WCAG.

"It is a one-off project"

Every new page, blog post, product photo or campaign can introduce new barriers. Accessibility works like spelling or security: you get it in good shape once, then keep it there as part of everyday work.

A realistic way to start

You do not need to fix everything at once. A steady, practical approach works better than a big bang.

Check your most important pages. Start with your home page, contact page, a key product or service page and any form or checkout. An automatic check finds many common problems quickly, roughly a third to half of all issues, but not all of them.
Fix the most serious things first. Begin with anything that stops people completing a task: a form that cannot be sent with the keyboard, a button without a name, a field without a label. Then tackle problems that appear on every page, such as low contrast in your template or a menu that only opens with a mouse.
Test by hand. Spend ten minutes using your site with the keyboard only. Zoom your browser to 200% and see whether anything overlaps or disappears. Try the screen reader that is built into your device, VoiceOver on a Mac or iPhone or TalkBack on Android, or the free NVDA on Windows. Read your key texts aloud and ask whether a newcomer would understand them.
Write an accessibility statement. A short page that explains what you have checked, which problems you know about, what you are doing about them and how people can reach you if they get stuck.
Keep it in your process. Add alt text and clear link text to your content checklist, ask your web agency or site builder for accessible templates, and recheck after every redesign or major update.

Check your own site

The easiest first step is to see where your site stands today. Check a page on ibin for free: you get a plain-language report that shows what is wrong, who it affects, where it is on the page and how to fix it. Use the repair guides to work through the findings and our guide to writing an accessibility statement when you are ready to publish one. Sign in with your email address and you can check up to 200 pages of the same site for free.

See how your own site does

Check a page for free, without an account. You get a plain list of what to fix first, with pictures of where each problem is.