Accessibility and Inclusive Design

Picture a website you use every day — a video app, a shopping page, your school's login. Now imagine using it if you couldn't see the screen, or couldn't hear the sound, or couldn't hold a mouse steady, or found dense pages of text overwhelming. Millions of people are in exactly that situation right now. Technology that only works for people with perfect sight, hearing and hand control quietly locks everyone else out.

Accessibility means building technology so that everyone can use it, including people with visual, hearing, motor (movement) or cognitive (thinking, memory, attention) differences. It isn't a niche feature for a tiny minority — around 1 in 5 people has a disability of some kind, and almost everyone is temporarily or situationally disabled at times: a broken arm, a bright sunny screen, a noisy train where you can't hear the audio. Design for the edges and you help the middle too.

Matching the barrier to the solution

Every accessibility feature exists to knock down a specific barrier — something that stops a person from using a product. Explore how four common barriers pair up with the features that remove them. Step through the diagram:

Notice the pattern: the feature doesn't change what the technology does — a video still plays, a button still works — it just adds another way in so the content reaches more people.

The everyday toolkit of accessibility

Here are the features you are most likely to meet — and are expected to know for GCSE:

Screen readers & alt text. A screen reader is software that reads out (or sends to a Braille display) whatever is on screen, so a blind or partially sighted user can "hear" a page. But it can't see inside a picture — so every meaningful image needs alternative text ("alt text"): a short written description the screen reader voices instead. A photo of a graph might have alt text like "Bar chart showing sales doubling from 2023 to 2024."
Captions & subtitles for video. Captions put the spoken words (and important sounds, like [door slams]) on screen as text, so someone who is deaf or hard of hearing can follow along — and so can anyone in a silent library or a loud gym.
Keyboard navigation. Not everyone uses a mouse. People with motor differences, tremors, or who navigate by voice or by switch devices rely on being able to Tab through every link, button and form field and activate it with the keyboard alone. If something only works by clicking exactly on it with a mouse, those users are stuck.
High contrast, resizable text & careful colour. Letting users enlarge text or switch to a high-contrast theme helps people with low vision. And meaning should never rely on colour alone — roughly 1 in 12 men has some colour blindness, so "the red items are urgent" fails them unless the urgent items also have a label, an icon or a shape.
Clear, simple layouts. Predictable structure, plain language and generous spacing help people with cognitive or learning differences (and everyone who is tired, stressed or in a hurry). Clutter is a barrier too.

Inclusive design: build it in from the start

Inclusive design is the mindset behind all of this: instead of building for an imaginary "average" user and then bolting on fixes for everyone else, you design for the widest possible range of people from the very beginning. The remarkable result is that features created for one group end up helping far more people than intended.

The classic real-world example is the kerb cut (the little ramp where the pavement dips to meet the road). It was fought for by wheelchair users — but today it helps parents with prams, delivery workers with trolleys, cyclists, travellers with suitcases and anyone who has ever pulled a heavy bag. This is called the curb-cut effect: design for the person with the greatest barrier and you smooth the path for the crowd.

The same is true online. Captions were created for deaf viewers — now they're used by people watching on mute, learning a language, or in a noisy place. Voice assistants that help people who can't use a keyboard are used by everyone cooking with messy hands. Good accessibility is simply good design.

Disability isn't always permanent. Think of a spectrum: a person with one arm has a permanent reason to use a device one-handed; a person with a broken arm has a temporary one; a parent holding a baby has a situational one. All three benefit from a design that works one-handed. Designing inclusively serves all of them at once — which is a huge slice of your users, not a tiny corner.

Two mistakes to avoid:

Accessibility is not an optional extra you bolt on at the end. Leaving it until the product is "finished" makes it expensive, patchy and often impossible to retrofit — it is a design responsibility owned by the whole team from day one, and in many countries (including the UK, under the Equality Act) it is a legal requirement, not a favour.
Never rely on colour alone to carry meaning. A form that marks errors only by turning the box red is invisible to a colour-blind user. Always pair the colour with something else — a text label, an icon, a symbol or a shape — so the message survives even if the colour doesn't.