Theory
The user you forgot
FestConnect now works beautifully for the students you tested. But consider users you did NOT test: a student with low vision who cannot read the light-grey fine print, one who is colour-blind and cannot tell the red error text from black, one whose motor disability means they cannot use a mouse, one using a screen reader that finds an image with no description.
For them, your polished product is a locked door. Accessibility is designing so that EVERYONE can use it: and it turns out to make the product better for all users, not just some.
Theory
Accessibility, formally
Accessibility (often 'a11y') is designing products usable by people with the widest possible range of abilities, including disabilities.
Disabilities to design for span several kinds:
- visual: blindness, low vision, colour blindness
- auditory: deaf or hard of hearing
- motor: limited dexterity, unable to use a mouse
- cognitive: differences in memory, attention, processing
Accessibility is not a niche add-on for a few: disabilities are common, temporary (a broken arm) or situational (bright sunlight), and it is often an ethical and legal requirement. Designing for the edges strengthens the centre.
At a glance
Accessibility practices (and who they help)
| Practice | Helps | FestConnect example |
|---|---|---|
| Sufficient colour contrast | Low vision, sunlight, everyone | Dark text, not light-grey, on the register button |
| Never colour alone for meaning | Colour-blind users | Errors shown with an icon + text, not just red |
| Text alternatives (alt text) | Blind users (screen readers) | The Garba photo described in alt text |
| Keyboard navigation | Motor disabilities, power users | The whole form usable without a mouse |
| Adequate target size | Motor difficulties, everyone | Buttons big enough to tap reliably |
Theory
WCAG and the POUR principles
The recognised standard for accessibility is WCAG (Web Content Accessibility Guidelines), organised around 4 principles remembered as POUR:
- Perceivable: users can perceive the content (contrast, alt text, captions)
- Operable: users can operate the interface (keyboard, enough time, big targets)
- Understandable: content and operation are clear (simple language, predictable)
- Robust: works with assistive technologies (screen readers)
You do not need to memorise every WCAG rule, but knowing the POUR framework shows you understand accessibility as a structured discipline, not a vague 'be nice' aspiration.
Quiz
FestConnect shows form errors ONLY by turning the field's text red. Why is this an accessibility problem, and what fixes it?
- No problem: red is a clear error colour for everyone
- Colour-blind users cannot perceive the red cue; add an icon and text message so meaning is not colour-only
- The fix is to make the red brighter
- Errors should be hidden entirely
- Only screen-reader users are affected; ignore it
Show the answer
Colour-blind users cannot perceive the red cue; add an icon and text message so meaning is not colour-only
Relying on colour ALONE excludes colour-blind users (a large population), who cannot distinguish the red text from normal text, so they miss the error entirely: a direct violation of the perceivable principle. The fix is redundancy: convey the error through MULTIPLE cues: an icon, a text message ('Enter a valid phone number'), AND colour: so no one depends on seeing red. Option A states the misconception. Option C (brighter red) does not help someone who cannot perceive red at all. Option D is absurd (hiding errors). Option E under-counts who is affected. The rule: never use colour as the ONLY carrier of meaning.
Think first
The curb-cut effect
Curb cuts (the ramps in kerbs) were built for wheelchairs, yet they help parents with prams, delivery workers, cyclists and travellers with suitcases. How does this idea apply to designing FestConnect accessibly? Then tap.
Show the answer
It is the curb-cut effect: design made for people with disabilities routinely helps EVERYONE. In FestConnect: high contrast built for low-vision users also helps anyone reading in bright hostel sunlight; big tap targets for motor difficulties help everyone's clumsy thumbs; captions for deaf users also help a student in a noisy common room with the sound off; clear simple language for cognitive accessibility helps a stressed first-year. So accessibility is NOT a costly favour to a minority: it is better design, period, that widens your user base and improves the experience for all. That reframe, from 'compliance burden' to 'better for everyone', is the mature designer's view.
Watch out
Accessibility slips
Colour-only meaning: excludes colour-blind users; always add icon/text.
Low contrast: pretty light-grey text is unreadable for many (and in sunlight for all).
Missing alt text: images invisible to screen-reader users; describe them.
Mouse-only interactions: locks out keyboard and assistive-tech users; support keyboard.
Accessibility as an afterthought: bolted on at the end is expensive and partial; design for it from the start.
Tiny tap targets: hard for motor difficulties (and everyone).
Theory
The subject comes together
You have now run the ENTIRE user-centered design process on FestConnect: understood users (research, personas, interviews), designed the structure (interaction, IA, wireframes, navigation), made it look right (visual design), and validated it (testing, iteration, accessibility). One lesson remains: a CASE STUDY that walks the whole journey end to end on a real-feeling product, so every principle clicks into one coherent story. The finale.
Summary
Key takeaways
- Accessibility means designing products usable by the widest range of abilities, including visual, auditory, motor and cognitive disabilities.
- Key practices: sufficient contrast, never colour-alone for meaning, text alternatives (alt text), keyboard navigation, adequate target size.
- The standard is WCAG, with 4 principles: Perceivable, Operable, Understandable, Robust (POUR).
- Never rely on colour alone; convey meaning through multiple cues (icon + text + colour).
- The curb-cut effect: accessible design helps EVERYONE, not only people with disabilities.
- It is an ethical/legal requirement and expands the user base; design for it from the start, not as an afterthought.
- Memory hook: accessible design is just better design, for everyone.