Accessibility
WCAG POUR Principles
Web accessibility is organised around four principles: content must be Perceivable, Operable, Understandable, and Robust — failure on any one principle makes content inaccessible to some users.
Where it comes from
POUR is the organising framework of WCAG — the Web Content Accessibility Guidelines, published by the W3C. Every accessibility requirement is grouped under one of four principles: content must be Perceivable, Operable, Understandable, and Robust.
Why it matters for your website
WCAG — the Web Content Accessibility Guidelines — organises all accessibility requirements around four principles known as POUR. Perceivable: information must be presented in ways users can detect regardless of sensory ability. Operable: all functionality must be usable regardless of input method. Understandable: content and interfaces must be clear and predictable. Robust: code must be clean enough to work reliably with assistive technologies now and as technology evolves. Failure on any single principle creates a real barrier for real users. The Click-Away Pound Survey found that 69% of disabled online consumers simply leave websites they find difficult to use — taking their spending power with them. The WebAIM Million 2025 report found accessibility failures on 95%+ of home pages analysed. POUR is the diagnostic lens; WCAG 2.2 AA is the minimum conformance target that UK, EU, and US accessibility law point to.
Each letter names a way access can fail. Perceivable — can users detect the content regardless of sensory ability? Operable — can they use it regardless of input method? Understandable — is it clear and predictable? Robust — does the code work reliably with assistive technologies? Failure on any one creates a real barrier for real users.
And the barriers cost real money. The Click-Away Pound survey found 69% of disabled online consumers simply leave sites they find hard to use — taking their spending with them — while the WebAIM Million 2025 report found accessibility failures on over 95% of home pages. POUR is the diagnostic lens; WCAG 2.2 AA is the minimum conformance target that UK, EU, and US law point to.
Wrong vs right
A site that fails one POUR principle — say, unusable by keyboard (not Operable) — and so excludes a whole group of users.
A site that satisfies all four principles, so it's accessible regardless of ability or input method.
Treating accessibility as a niche concern rather than a barrier that turns away a large, spending audience.
Treating WCAG 2.2 AA as the baseline, recognising accessibility as both a legal and commercial requirement.
Passing some accessibility checks while failing one principle entirely, leaving the page inaccessible to some.
Covering all four principles, since a failure on any one creates a real barrier.
Understanding WCAG POUR Principles
POUR is the framework that organises the Web Content Accessibility Guidelines (WCAG), the W3C's international standard for web accessibility. Every WCAG requirement falls under one of four principles: content must be Perceivable (detectable regardless of sensory ability), Operable (usable regardless of input method), Understandable (clear and predictable), and Robust (working reliably with assistive technologies, now and as they evolve).
The four principles are a diagnostic lens, and crucially they're conjunctive: failure on any single one creates a real barrier for real users. A page can be perceivable and understandable but, if it isn't operable by keyboard, it still excludes the people who rely on that. Accessibility isn't an average across the principles — it requires all four.
The stakes are practical, not abstract. The Click-Away Pound survey found 69% of disabled online consumers simply leave sites they find difficult to use, and the WebAIM Million 2025 report found accessibility failures on over 95% of home pages. POUR is the lens; WCAG 2.2 AA is the minimum conformance target that UK, EU, and US accessibility law point to. It connects to colour contrast, keyboard navigability, alt text, and focus management.
How Kweri checks it
POUR is the umbrella, and Kweri's coverage of it is mixed by nature — accessibility is the area where automated testing helps most but covers least. Kweri runs automated checks (via axe-core) against many measurable WCAG criteria — contrast, alt text, semantic structure, and more — which catch a meaningful share of issues. But industry estimates put automated coverage at roughly a third to a half of accessibility problems; things like whether alt text is *meaningful*, whether a keyboard order makes sense, or whether content works with a real screen reader need human and assistive-technology testing. So Kweri reports what it can measure across the four principles and is explicit that a clean automated pass is not the same as a fully accessible, WCAG 2.2 AA-conformant page.
FAQ
What are the POUR principles?
POUR is the framework organising WCAG accessibility requirements into four principles: Perceivable (content users can detect regardless of sensory ability), Operable (usable by any input method), Understandable (clear and predictable), and Robust (working reliably with assistive technologies).
What does each POUR principle mean?
Perceivable: information must be presentable in ways users can sense. Operable: all functionality must work regardless of input method. Understandable: content and interfaces must be clear and predictable. Robust: code must work reliably with current and future assistive technologies.
Why does failing one principle matter?
Because the four are conjunctive — failure on any single one creates a real barrier for some users. A page that's perceivable and understandable but not operable by keyboard still excludes the people who rely on keyboard access. Accessibility requires all four.
What conformance level should I target?
WCAG 2.2 AA is the minimum target that UK, EU, and US accessibility law point to. POUR is the diagnostic lens for understanding the requirements; AA is the practical baseline for legal and ethical compliance.
Is web accessibility a commercial issue?
Yes. The Click-Away Pound survey found 69% of disabled online consumers leave sites they find hard to use, taking their spending with them. With accessibility failures on over 95% of home pages, it's both a legal requirement and a significant commercial opportunity.
Related principles
Every interactive element must be reachable and operable using a keyboard alone, with visible focus indicators showing where the user currently is.
Keyboard focus must be visible at all times, move in a logical order, and be actively managed when content changes — especially when modals open, overlays appear, or dynamic content updates.
Every image, icon, or non-text element that conveys meaning must have a text alternative that communicates the same information to users who cannot see it.
Text needs enough contrast against its background to be read — WCAG's ratio is the floor, not the goal.
Attribution & sources
Identified by W3C Web Accessibility Initiative (WAI). Catalogued from W3C — Web Content Accessibility Guidelines (WCAG).
POUR is the organising framework of WCAG, the international accessibility standard; the linked W3C page is the primary source.
See WCAG POUR Principles on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →