Review a digital design by checking whether people can perceive its information, operate its interface, understand its organization, and access content through compatible web interfaces. Then map every finding to the applicable WCAG 2.2 success criteria.
Start the Review with WCAG 2.2 and POUR
WCAG 2.2 organizes 13 guidelines under four principles: Perceivable, Operable, Understandable, and Robust—often shortened to POUR. Use these principles as four review lenses rather than treating them as a simple pass-or-fail checklist.
Begin by selecting a representative page or interface state. Review its text, images, structure, presentation, dynamic content, and any multimedia. Record each barrier under the most relevant POUR principle, along with its location and effect on access.
Next, connect observations to WCAG’s testable success criteria. These criteria are grouped into conformance levels A, AA, and AAA. Supporting guidance, techniques, and test rules can help with implementation and evaluation, but a broad visual review alone does not establish conformance. The practical goal of the first pass is to find likely barriers systematically and identify which findings need criterion-level testing.
Review Perceivability: Contrast, Color, and Structure
Start with the information users must be able to perceive. Inspect foreground text against its background and flag combinations with insufficient contrast. Low contrast can make content difficult to perceive for people with vision-related disabilities. Visual inspection can reveal suspicious combinations, but the result should still be evaluated against the applicable success criterion.
Then look for meaning communicated only by color, shape, or size. Examples might include an instruction that identifies an item solely by its color or a status system with no accompanying text. Record where users would lose the message if they could not distinguish the visual cue, and propose an additional cue rather than removing useful color.
Finally, examine headings and content order. Headings should expose a clear organization, while the reading sequence should remain logical. Unclear structure or illogical ordering can hinder comprehension and navigation, particularly for screen-reader users. Review these elements as part of perception and comprehension, then map each issue to an applicable WCAG 2.2 success criterion instead of calling the visual inspection itself a conformance test.
Review Operation, Understanding, and Robustness
For Operable, attempt to navigate the page and activate its interface elements with a keyboard. Identify anything that requires a mouse and note the blocked task, not merely the affected component. An interface that cannot be navigated by keyboard can prevent non-mouse users from operating it.
For Understandable, examine whether the content follows a logical structure and whether repeated page elements remain consistent. Consistent elements and clear organization reduce avoidable confusion. Check representative states, including any dynamic content available within the page, because the review applies to more than a static screenshot.
For Robust, move from general observations to criterion-based evaluation. WCAG conformance is determined through testable success criteria, so record the relevant criterion, the observed result, and any supporting technique or test rule used. Do not label the design conformant merely because it appears to satisfy the four high-level principles.
Apply the same process to the kinds of web content within scope, which may include text, images, sounds, presentation, dynamic material, multimedia, mobile web content, and AI web interfaces. W3C encourages the use of WCAG 2.2 and states that content conforming to WCAG 2.2 also conforms to WCAG 2.1 and 2.0.
Conclusion
Use POUR as a repeatable sequence: inspect contrast, non-color cues, headings, and content order; test whether the interface can be operated by keyboard; check logical structure and consistent page elements; then evaluate findings against applicable WCAG 2.2 success criteria.
Keep observations separate from formal conformance conclusions. A focused review can expose barriers and organize follow-up testing, while criterion-level results determine conformance. Choose one representative page now, record every issue under its POUR principle and relevant success criterion, and prioritize fixes that prevent users from perceiving information or operating the interface.
Frequently asked questions
Does a POUR review prove that a design conforms to WCAG 2.2?
No. POUR provides a useful structure for finding and organizing accessibility concerns, but conformance is determined by meeting applicable testable WCAG success criteria. Supporting techniques and test rules can guide the necessary evaluation.
What do WCAG levels A, AA, and AAA mean in a review?
A, AA, and AAA are the three levels used to group WCAG success criteria. Record the applicable criterion and its level when documenting a finding rather than assigning a level from a general visual impression.
Disclosures and limitations
- This article was prepared with AI assistance and is based exclusively on the two sources identified in the supplied research package. It provides a practical review framework, not an independent certification of WCAG conformance.
Related reading
- Design & Media Guides for Clear Visual Communication
- How Drake Album Covers Use Color, Hierarchy, and Typography
Sources
- Article Detail — service.shure.com
- System Science – Part 3: Analogue Connections — Focusrite
- WCAG 2 Overview — Web Accessibility Initiative (WAI)
- Data – Wikipedia — en.wikipedia.org
- ChartGPT — chartgpt.io
- WCAG 101: Understanding the Web Content Accessibility Guidelines — WCAG
- Layer Cake Bakery | Cakes & Pastry | Irvine, CA, USA — Layer Cake Bakery