Accessibility Is Design for the Full Range of Real Bodies
Accessibility means the product works for disabled people, covering sight, hearing, movement, and differences in reading and thinking.
This is not a rare edge case, since roughly 1 in 6 people worldwide live with a significant disability.
Temporary and situational limits count too: a broken wrist, a cracked screen, bright sunshine, a noisy bus, one hand holding a bag.
Accessible choices tend to help everybody, and captions get switched on far more often by people in quiet train carriages than by deaf viewers.
Designing it in from the wireframe stage is nearly free, while adding it after the build means rebuilding screens you thought were finished.
Alt Text Describes the Job, Not the Picture
Alt text is a short written description attached to an image, read aloud in place of the image by assistive software.
Write what the image is doing on that page, so "Bar chart, book loans peak in September" beats "bar chart".
Keep it under about 125 characters and move anything longer into the text around the image.
Purely decorative images get empty alt text so the software skips past them instead of announcing clutter.
Do not open with "image of", because the software has already said it is an image.
Example
The image is a photo of a student holding a card at a self service machine.
Weak alt text: "student".
Better alt text: "Student scanning a library card at the self service machine".
The striped background pattern behind it gets empty alt text and is never mentioned.
Keyboard Navigation and Focus Order
Plenty of people never touch a mouse: some use only a keyboard, others use a switch, a head pointer or voice control that behaves like one.
Every action in your product must be reachable with Tab, Shift and Tab, Enter, Space and the arrow keys.
Focus is the invisible cursor showing which element the keyboard is currently on, and it needs a clearly visible ring or outline.
Focus order should follow the visible order down the screen, so nobody tabs from the header to the footer and back up to the middle.
A keyboard trap is the classic failure: a pop-up you can tab into but never out of, which leaves the user stuck with no way back.
Screen Readers Read Structure, So Give Them Some
A screen reader speaks the screen aloud, and the common ones are VoiceOver on Apple devices, TalkBack on Android and NVDA on Windows.
Experienced users jump between headings and links rather than listening to a page from the top, which is far faster.
Real headings in order, build the map they jump around, while text that is merely big and bold builds nothing.
Every form field needs a label properly joined to it, so the reader says "Email address, edit box" instead of just "edit box".
Link text has to make sense on its own, because a list of eleven links all reading "click here" tells a listener nothing.
Common Mistake
Jumping from a level 1 heading straight to a level 4 breaks the map a screen reader user navigates by.
It nearly always happens because someone picked the heading that looked the right size.
Choose the level for meaning first, then set its size separately.
Captions, Transcripts, Target Size and Motion
Captions show the words of a video in time with it, and they cover important sounds such as a doorbell as well as speech.
A transcript is the whole thing written out, which suits people who would rather read in two minutes than watch for eight.
Automatic captions are a first draft only, since they mangle names, subject vocabulary and anything said quickly.
Target size matters to anyone with unsteady hands, and about 44 by 44 px is the usual minimum for something you tap.
Leave a gap between targets too, because two 44 px buttons pressed right against each other still produce wrong taps.
Movement makes some people dizzy or sick, so skip auto playing video and sliding backgrounds, and honour the reduce motion setting on the device.
WCAG Turns Good Intentions Into Testable Rules
Definition
WCAG
The Web Content Accessibility Guidelines, a published set of testable rules for making digital content usable by disabled people, graded at three levels: A, AA and AAA.
The WCAG is built on four ideas: content must be perceivable, operable, understandable and robust.
Level A is the minimum, covering the things without which some people simply cannot use the product at all.
Level AA is the level schools, public services and most organisations aim for, and it holds the 4.5 to 1 contrast minimum for body text.
Level AAA is the strictest, asking for things like 7 to 1 contrast, and is rarely applied to a whole product.
Aim at AA for your project and list which points you met and which you missed, because that list is checkable evidence for criterion D.
Tip
Browser accessibility checkers flag missing alt text, low contrast and broken heading order in seconds.
Automated tools catch only part of the picture, so they add to testing with people rather than replacing it.
Screenshot the tool's report, date it, and put the before and after versions in your folder.
Test It Yourself: Put the Mouse in a Drawer
Unplug the mouse, keep your hands off the trackpad, and try to finish your product's main task with the keyboard alone.
Check three things: can you always see where you are, can you reach every control, and can you escape every pop-up.
Then switch on the screen reader already built into your phone or laptop and listen to one screen with your eyes shut.
Zoom the browser to 200% and look for text that overlaps, buttons that vanish off the side, or menus that stop opening.
Both tests take ten minutes each and expose problems that no amount of staring at the design will ever reveal.
Active recall
What does alt text do, and what alt text should a decorative image get?
What is focus order, and what goes wrong when it does not match the visible layout?
Name the three WCAG levels and say which one most projects aim for.
Why are automatic captions only a starting point?
Describe a keyboard only test you could run on your own prototype tomorrow.