- Article
- Beginner
- 2 minutes read
- Reviewed August 4, 2026
WCAG organizes accessibility around four principles: perceivable, operable, understandable and robust.
These principles provide a useful mental model for evaluating WordPress content and functionality.
Perceivable
Information must be available in forms that users can perceive.
WordPress examples include:
- Alternative text for informative images.
- Captions for video.
- Sufficient contrast.
- Text that can be resized.
- Headings and landmarks exposed programmatically.
- Instructions that do not rely only on colour.
If information exists only visually or only through audio, some users may miss it.
Operable
Users must be able to navigate and operate the interface.
WordPress examples include:
- Keyboard-accessible menus.
- Visible focus.
- Logical focus order.
- Pausable moving content.
- Large enough targets.
- No keyboard traps.
- Predictable modal and menu behavior.
A control that works only with a mouse is not operable for everyone.
Understandable
Content and interactions should be clear and predictable.
This includes:
- Plain and appropriate language.
- Consistent navigation.
- Descriptive labels.
- Clear error messages.
- Instructions before complex forms.
- Predictable button behavior.
- Confirmation before destructive actions.
Robust
Content should work with current and future user agents and assistive technologies.
Use valid, semantic HTML and standard controls before custom ARIA implementations.
A native button already provides keyboard and accessibility behavior. A styled div requires significant additional work and can still fail.
Applying the Principles to WordPress
Evaluate each layer:
- Content created by editors.
- Theme templates and navigation.
- Plugin interfaces and forms.
- Gutenberg blocks.
- Custom front-end applications.
- Administration workflows.
- External embeds.
A page can satisfy one principle while failing another. For example, a high-contrast menu may still be impossible to operate by keyboard.
Accessibility Is Contextual
The same component can require different treatment depending on purpose.
An image can be informative, functional or decorative. A table can represent data or merely imitate a layout. A link can navigate while a button performs an action.
Start from purpose, then select the correct structure.
Frequently Asked Questions
What does POUR mean?
It is an acronym for Perceivable, Operable, Understandable and Robust.
Is semantic HTML enough?
It creates a strong foundation, but interaction, content, design and testing still matter.
Continue Learning
Previous: [What Is Web Accessibility?](/resources/wordpress-manual/accessibility/what-is-web-accessibility/)
Next: [Writing Accessible WordPress Content](/resources/wordpress-manual/accessibility/writing-accessible-content/)