What Accessibility Really Means
Welcome. Over this course you're going to learn a skill that will set you apart from most developers working today: how to build websites and applications that everyone can use. Not most people. Everyone. Before we write any code, let's be clear about what “accessibility” actually means — because most people, including most developers, get it half right.
Accessibility is not just about blindness
When developers hear “accessibility,” they usually picture a blind person with a screen reader. That's part of it — and as your instructor, it's the part I live every day. But it's a small slice of a much bigger picture.
Accessibility means building so that people with a wide range of abilities can use what you make. Think about who that includes:
- Vision — people who are blind, have low vision, or are colour-blind. Some use screen readers, some magnify the screen, some just need strong contrast.
- Motor — people who can't use a mouse: they navigate with a keyboard, with voice commands, or with a switch device. Someone with a hand tremor, or an arm in a cast, is in this group too.
- Hearing — people who are Deaf or hard of hearing, who need captions on your videos and transcripts for your audio.
- Cognitive — people with dyslexia, ADHD, memory difficulties, or who simply find cluttered, confusing interfaces hard to follow. Clear, simple design helps them — and everyone else.
And it's not only about permanent disability
Here's the idea that makes accessibility click for most developers. Disability isn't always permanent, and it isn't always about a person. Often it's about the situation.
Consider one ability — using your hands to operate a mouse:
- A person with one arm has a permanent limitation.
- A person with a broken arm has a temporary one — for six weeks, they're a keyboard user too.
- A parent holding a baby in one arm has a situational one — right now, they've got one hand.
All three benefit from the exact same thing: an interface that works without a mouse. When you build for the person with the permanent need, you quietly serve millions of people in temporary and situational versions of it. We'll come back to this powerful idea later in the module.
Accessibility is an engineering skill, not a favour
It's tempting to think of accessibility as being kind — a nice thing you add at the end if there's time. That framing is why so many websites are inaccessible: “the end” never comes.
Treat it instead as what it really is: a mark of engineering quality. An accessible interface is one built on correct, meaningful HTML, that works with a keyboard, that handles focus properly, that doesn't rely on colour alone. Those aren't charitable extras — they're the signs of a page built properly. A developer who writes accessible code writes better code, full stop.
And there's a real, practical payoff, which we'll unpack in the next lesson: accessibility is increasingly required by law, demanded in contracts, and rewarded in the job market. It's one of the rarest and most valuable specializations a web developer can hold.
How this course teaches it
Throughout this course, I'll do something no textbook can: I'll show you how a page actually sounds through a screen reader. You'll hear the difference between markup that works and markup that shuts people out — the same difference I experience every day. That's the thread that ties everything together, from semantic HTML to ARIA to testing your own work.
You already know HTML, CSS, and JavaScript. What you'll learn here is how to use them so that nobody is left standing outside your website. Let's begin.
What you learned
- Accessibility means building for a wide range of abilities — vision, motor, hearing, and cognitive — not blindness alone.
- It serves permanent, temporary, and situational needs, so building for one person quietly helps millions.
- It's a mark of engineering quality, not a favour added at the end — and a rare, valuable, increasingly required skill.
- This course will let you hear the difference good markup makes, through a screen reader.