WCAG has dozens of guidelines. But everything boils down to four core principles. If you remember nothing else, remember POUR.
What is POUR?
POUR is your mental framework for thinking about accessibility. Each letter stands for a question you should ask about your website:
- P — Perceivable
- O — Operable
- U — Understandable
- R — Robust
Let’s break each one down.
P — Perceivable
Can people perceive (see, hear, or otherwise sense) your content?
Your website content must be presentable in ways users can perceive with at least one of their senses. This means:
- Text alternatives for images — Every meaningful image needs alt text. “Photo of a golden retriever wearing a red bandana at a park” is helpful. “Image123.jpg” is not.
- Captions and transcripts — Videos need captions for deaf users. Audio content needs transcripts.
- Don’t rely only on color — If your form shows errors in red text, also include an icon or text label.
- Sufficient color contrast — Text needs enough contrast against its background to be readable.
O — Operable
Can people operate (navigate and use) your website?
All functionality must be accessible through different input methods—not just a mouse:
- Keyboard navigation — Every button, link, and form field should work with just a keyboard.
- Enough time — If content has time limits, users need options to extend them.
- No seizure triggers — Avoid content that flashes more than three times per second.
- Clear navigation — Users need multiple ways to find content and should always know where they are on your site.
U — Understandable
Can people understand your content and how your site works?
This goes beyond making things visible—it’s about making sense:
- Readable text — Use clear language. Define technical terms. Break up long paragraphs.
- Predictable behavior — Navigation should be in the same place on every page. Links that look the same should behave the same.
- Input assistance — Help users avoid mistakes with clear labels, and help them recover with specific error messages.
R — Robust
Will your content work with current and future technologies?
Your website needs to work reliably across different browsers, devices, and assistive technologies:
- Clean, valid code — Properly structured HTML helps screen readers interpret your content.
- Assistive tech compatibility — Your site should work with screen readers, voice recognition software, and other adaptive tools.
- Future-proof — Following web standards helps ensure your site works with technologies that don’t exist yet.
Putting POUR Into Practice
Here’s the beautiful thing about POUR: it makes accessibility feel less like a checklist and more like a design philosophy.
When reviewing your website or creating new content, just ask yourself:
- Can everyone perceive this content?
- Can everyone operate these features?
- Can everyone understand this information?
- Will this work with different technologies?
If you can answer yes to all four, you’re on the right track.
Read the full guide: WCAG Compliance Guide
Need help making your website accessible? Contact Egmer Marketing for a free accessibility review.
