- Article
- Intermediate
- 2 minutes read
- Reviewed August 4, 2026
- Advanced WordPress and integrations
WordPress developers influence accessibility through markup, controls, state, focus, errors and authoring workflows.
Official WordPress ecosystem code is expected to conform to WCAG 2.2 at Level AA.
Use Native Semantics
Prefer native HTML elements:
- Links for navigation.
- buttons for actions.
- labels for form controls.
- headings for document sections.
- lists for grouped items.
- tables for data.
Native elements provide keyboard and accessibility behavior that custom div controls must recreate.
Keyboard and Focus
Every interactive function must be operable through the keyboard.
Custom dialogs, menus and disclosures need predictable focus movement, visible focus and escape behavior. Restore focus when temporary interfaces close.
Accessible Names and States
Icon controls need accessible names.
Dynamic controls should expose state through properties such as aria-expanded, aria-pressed or status messages when the semantic pattern requires them.
ARIA supplements correct HTML; it does not repair an unsuitable interaction model.
Authoring Accessibility
A block or plugin should help editors create accessible content.
Provide:
- Clear field labels.
- alt-text support.
- heading guidance.
- contrast-safe presets.
- captions and descriptions.
- validation messages.
- predictable keyboard workflows.
This aligns with authoring-tool accessibility principles.
Test the Editor and Frontend
Test:
- Keyboard-only operation.
- Screen-reader announcements.
- zoom and reflow.
- forced colours.
- reduced motion.
- form errors.
- generated markup.
- administration workflows.
- public output.
Automated tools detect only selected issues.
Frequently Asked Questions
Is using WordPress components enough to guarantee accessibility?
No. Components must be configured and combined correctly.
Should accessibility be tested only after development?
No. Include it in component design, acceptance criteria and continuous testing.
Continue Learning
Previous: WordPress Coding Standards