Must not recommend or require inaccessible plugins
Basic principle
Accessibility Ready themes must not recommend, promote, bundle, or require plugins that introduce known accessibility barriers as part of the themes setup process or ongoing use within the WordPress admin.
Themes play a significant role in shaping how site owners build and extend their websites. When a theme directs users toward inaccessible plugins whether through onboarding screens, admin notices, documentation, or demo imports it undermines the goal of providing an accessible foundation and can result in inaccessible websites even when the theme itself meets accessibility requirements.
Accessibility Ready themes should guide users toward accessible choices by default, not place accessibility barriers directly in their recommended setup paths.
Themes should either:
- Not recommend plugins at all or,
- If recommending plugins, only recommend plugins that similarly pass
accessibility-readyrequirements.
Testing
Tools: browser
- Look for admin banners or notices recommending or requiring plugins after activating the theme.
- If prompted to install recommended or required plugins, install and activate those plugins.
- Conduct all
accessibility-readytests with the recommended or required plugins active. - If accessibility problems are identified related to the plugins, this is considered a failure.
Note: When evaluating accessibility, responsibility for the issue is not relevant to the review outcome. Testers are not required to determine whether an accessibility problem originates in the theme or in a plugin recommended by the theme.
If an accessibility barrier is present, it should be reported. It is then up to the theme developer to determine whether the issue can be addressed within the theme, needs to be reported upstream, or requires removing the plugin recommendation altogether.
- First published: October 10, 2025
- Last updated: August 04, 2026
- Edit article: Improve it on GitHub
- Contributors: Amber Hinds, Joe Dolson.
Other pages in: Theme accessibility-ready guidelines
-
Skip to Content Link
The requirements for a Skip to Content link on accessibility-ready themes.
-
Meaningful landmark roles and names
Accessibility-ready themes requirements for meaningful landmark roles and names
-
Keyboard navigation support
The requirements for keyboard navigation in accessibility-ready themes
-
Controls with accessible names, roles, and states
Accessibility-ready theme requirements for accessible controls
-
Labeled form fields
Accessibility-ready theme requirements for how to label form fields
-
Headings with meaningful structure
Accessibility-ready theme requirements for how to use headings
-
Underlined links in text
Accessibility-ready theme requirements for how to indicate links in text
-
No ambiguous link text
Accessibility-ready theme requirements for ambiguous link text
-
Sufficient color contrast of text and UI controls
Color contrast requirements in accessibility-ready themes
-
Alternative text on images and graphics
Use of alternative text requirements for accessibility-ready themes
-
Accessible audio, video, and animations
Support for audio, video, and animations in accessibility-ready themes
-
Support for reflow, resize, and text spacing changes
Requirements for handling reflow, resize, and text spacing in accessibility-ready themes
-
No unexpected changes of context
Requirements for changes of context in accessibility-ready themes
-
No links opening new windows or tabs without warning
Requirements for opening new windows or tabs in accessibility-ready themes
-
Content on hover or focus is accessible
How to handle content revealed on hover or focus in accessibility-ready themes
-
Accessibility statement
Accessibility Statement requirements for Accessibility-ready themes
-
Screen reader text supported
How screen reader text must be supported on an accessibility-ready theme
Back to: Theme accessibility-ready guidelines
Quick links and main topics
Quick links
Disclaimer: This documentation is intended to help the WordPress community understand and implement accessible practices. It is not a replacement for the official Web Content Accessibility Guidelines. Please read the full disclaimer.