POUR is an acronym for the four accessibility principles in the Web Content Accessibility Guidelines (WCAG). Each principle focuses on making digital content and experiences accessible to different types of users with disabilities. Consider the four letters as your pillars of producing accessible digital products and content. WCAG and success criteria are organized around the following four principles, which lay the foundation necessary for anyone to access and use web content.
Anyone who wants to use the Web must have content that is:
Information and user interface components must be presentable to users in ways they can perceive.
This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses). Example: Text Alternatives. Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, translations, or simpler language.
Examples of perceivable web content:
Videos must have captions for deaf or hard-of-hearing users.
Audio files must have transcripts for deaf or hard-of-hearing users.
Images must have alternative text describing the image for visually-impaired users.
Text must be added to the page via HTML rather than CSS so the text can still be read if styles are turned off completely.
User interface components and navigation must be operable.
This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform). Example: Keyboard Accessible. Make all functionality available from a keyboard or a keyboard interface so that people with disabilities are able to operate websites without needing a mouse.
Key features of operable websites include:
Multiple ways to interact with the website.
User control over time limits/timing.
Clear instructions and error recovery options that can be controlled regardless of ability.
Semantic HTML on links and buttons, rather than using <div> or <span> tags.
No elements that require drag-and-drop interactions unless there is an accessible alternative.
Information and the operation of user interface must be understandable.
This means that users must be able to understand the information as well as the operation of the user interface (the content or operation cannot be beyond their understanding), Example: Labels and Instructions. Labels and instructions are provided to users whenever content requires user input, e.g. sign up or login forms.
Understandable websites have:
Appropriately targeted language and reading level (typically at 8th- or 9th-grade reading level if writing for the general public).
Understandable functionality, which typically comes from elements like:
Written descriptions of information contained in charts or graphs.
Transcripts of audio or video files.
Audio files that let people listen to pages instead of reading them.
Supplemental representation of information, such as:
Consistent font styles (family, colors, and sizing) across all pages of the site.
A well-thought-out and easy-to-use navigation structure.
Clear instructions for forms and visible form labels.
Tooltips or “getting started” guides for special features.
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
This means that users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible). Example: Parsing. Maximize compatibility with current and future user agents, including assistive technologies, by ensuring content created using markup languages are coded correctly and have complete start and end tags. This allows user agents to present content without crashing.
Ideally, robust websites must:
Be functional across current and (as much as possible) future devices, operating systems, and browsers.
Support some outdated operating systems and browser versions, as elderly people and people who use assistive technology are less likely to be running the most up-to-date versions of their browser or operating system.
Validate against technical standards for any applicable platforms.
If any of these are not true, users with disabilities will not be able to use the Web.
Here at the Digital Accessibility Workshop, there are corresponding icons listed with each exercise. These reinforce how these principles apply to specific aspects of technology, while reminding you that WCAG 2.1 AA is the State's standard for compliance.
We have a variety of exercises across eight (8) topic areas designed to get you thinking in terms of the POUR principles.
These are the State of Colorado's technical standards to follow when creating accessible digital products.
By following WCAG as our minimum standard of accessibility, you are helping ensure the State of Colorado's digital products are equitable and inclusive for all.