Achieving the POUR standard requires attention at every stage of the product lifecycle. Use the following list as a required validation step before each release.
Perceivable: Delivering Content That Everyone Can Sense
This principle focuses on helping all users access the information presented on the screen.
Text Alternatives
Write accurate, concise alt text for informative and interactive images. Mark decorative graphics with empty alt attributes (alt=""). Supply text descriptions for complex visuals such as charts or infographics.
Time-Based Media
Add captions to videos and transcripts to audio assets. Include audio descriptions for visual details that are important for understanding. Give users the ability to pause, stop, or adjust playback for all multimedia.
Adaptable & Distinguishable Content
Use semantic HTML for headings, lists, and sections so structure is meaningful. Keep the code’s reading order aligned with its visual layout. Don’t rely solely on color or placement to communicate meaning. Follow contrast ratios of at least 4.5:1 for normal text. Make focus indicators clearly visible and support text resizing up to 200% without losing functionality or readability.
Operable: Enabling Interaction Without Barriers
This principle helps users interact with every component of the interface.
Keyboard Accessibility
Check that all controls, like links, buttons, and form fields, respond fully to keyboard input. Keep focus indicators easy to spot. Avoid keyboard traps so users can move freely into and out of elements.
Timing and Motion
Remove unnecessary time limits. If timing is required, allow users to extend or deactivate it. Prevent unexpected auto-refreshing or animated content that might disrupt focus.
Avoid flashing elements and alert users when they may appear. If it’s impossible to remove flashing elements, adhere to the 3 Flashes rule: no content should flash more than three times in any one-second period.
Navigation
Use descriptive page titles and consistent navigation patterns. Replace vague link labels like “click here” with meaningful text. Add skip-navigation links for quick keyboard access to the main content. For complex paths, include breadcrumbs to support orientation.
Understandable: Clarity and Predictability in UX
The experience should be intuitive and easy to follow.
Readable Content
Use straightforward language with short, clear sentences. Define abbreviations and avoid unnecessary technical terms. Aim for a reading level suitable for a wide audience.
Predictable Behavior and Input Assistance
Keep navigation structures, iconography, and layouts uniform across pages. Avoid unprompted actions such as sudden redirects. Programmatically connect labels and error messages to their input fields. Offer inline help, sample values, and confirmation steps for sensitive or irreversible actions.
Robust: Ensuring Technical Compatibility
Users should be able to access the content using various technologies and devices.
Technical Compatibility
Write valid, standards-compliant HTML and apply ARIA roles only when appropriate. Test your interface with assistive technologies such as NVDA, JAWS, VoiceOver, and voice-controlled tools. Confirm the layout adapts reliably to different screen sizes and environments.
