Accessibility statement

Basic principle

Accessibility Ready themes must include an accessibility.txt file to help website owners make informed decisions when choosing a theme.

This file has a standardized format outlining the themes accessibility audit status, how it has been tested, and any included accessibility features. It also provides information on reporting accessibility issues, making it easier to ensure that websites remain compliant with accessibility standards over time.

Testing

Tools: browser or text editor.

1. Verify that there is a file in the main theme directory named accessibility.txt.
2. Open the accessibility.txt file with a text editor or the theme file editor.
3. Review the contents of the file and verify it adheres to the WordPress accessibility.txt readme standard.

Resources

Related pages in this documentation

• Accessibility.txt files in Standards and best practice, Documenting accessibility.
• Accessibility statements in Standards and best practice, Documenting accessibility.

• 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

• Must not recommend or require inaccessible plugins

  Accessibility-ready themes must not recommend or require inaccessible plugins.

• 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

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.

↑ Back to top