- Article
- Intermediate
- 3 minutes read
- Reviewed August 3, 2026
A WordPress theme shapes much of the semantic structure and interaction visitors experience.
It controls landmarks, navigation, focus styles, typography, responsive layouts and the markup surrounding content. A strong theme creates an accessible foundation, but no theme can guarantee accessibility when content, plugins or customizations introduce barriers.
Semantic Structure and Landmarks
Templates should use meaningful HTML elements and landmarks.
Typical regions include:
- Header.
- Navigation.
- Main content.
- Complementary sidebar.
- Footer.
Block themes can assign semantic elements to Group, Template Part and Query blocks. Classic themes define them in PHP templates.
Use one clear main region and avoid unnecessary landmark duplication.
Skip Links
A skip link lets keyboard users bypass repeated navigation and move directly to the main content.
The target must exist, receive focus appropriately and remain visible when focused. Theme changes should not remove or obscure this mechanism.
Keyboard Navigation and Focus
Every interactive control must be operable without a mouse.
Test:
- Navigation menus and submenus.
- Search controls.
- Modal and overlay components.
- Carousels.
- Form controls.
- Pagination.
- Comment interfaces.
Focus indicators must be visible against the surrounding design. Do not remove outlines without providing an effective alternative.
Typography and Color
The theme should support readable text and sufficient contrast.
Consider:
- Font size and line height.
- Line length.
- Text spacing.
- Color contrast.
- Link recognition beyond color alone.
- Zoom and text resizing.
- Dark and custom color combinations.
Global Styles should not expose combinations that make accessible content difficult to maintain.
Navigation Accessibility
Menus require clear labels, logical order and usable submenu controls.
Collapsed mobile navigation needs an accessible name and state. Keyboard and screen-reader users should understand whether the menu is open and where focus moves.
Do not depend on hover alone.
Dynamic and Repeated Content
Query Loops, carousels and interactive blocks need appropriate headings and announcements.
Repeated cards should avoid duplicate link text without context. Pagination needs descriptive labels and a clear current page.
Dynamic changes should preserve focus and communicate status where necessary.
Editor and Theme Responsibilities
The theme owns the structural foundation, but editors also affect accessibility through:
- Heading order.
- Alternative text.
- Link wording.
- Table structure.
- Color choices.
- Captions and transcripts.
- Block selection.
Provide patterns, style presets and documentation that make the accessible choice the easy choice.
Accessibility-Ready Themes
The WordPress.org accessibility-ready designation indicates that a submitted theme passed specific review requirements.
It does not certify the final website, third-party plugins or later customizations. Continue testing the complete implementation.
Testing Process
Use a combination of:
- Keyboard testing.
- Screen-reader checks.
- Automated accessibility tools.
- Contrast analysis.
- Zoom and reflow testing.
- Reduced-motion settings.
- Real-user feedback where possible.
Test representative templates, not only the homepage.
Frequently Asked Questions
Can a plugin make an inaccessible theme accessible?
An overlay or plugin cannot reliably repair structural problems across an entire site. Fix the underlying theme, content and component issues.
Are block themes automatically accessible?
No. Blocks provide useful semantics and controls, but templates, styles and content must still be implemented correctly.
Who owns accessibility after launch?
Accessibility is shared across design, development, content and maintenance. Assign ongoing review responsibilities.
Continue Learning
Previous: Responsive Design in WordPress