When we announced the new accessibility-ready theme guidelines in May, the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both direct access (i.e. unassisted) and indirect access meaning compatibility with a persons assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) time set an ambitious timeline to re-review all themes and require action from theme authors by June 30th of this year.

Well, that date fled by three weeks ago, and the team hasnt taken action yet to delist any themes.

The team has found that we need more time to be able to reasonably go through all themes and make progress, so were extending this deadline until September 30th, 2026.

What does this deadline mean?

As a theme author, we expect you to have contacted the accessibility ready team using our theme accessibility review request form. That review indicates that you have taken steps to improve your theme and move towards the new requirements, and are engaging on the process. As long as you have submitted the form and begun the process of fixing your theme, your theme will not be delisted from the directory.

On October 1st, any theme that has the accessibility-ready tag and has not requested a re-review will be de-listed.

What does delisting a theme mean?

Your theme is no longer visible in the theme directory. You are still able to submit updates to your theme, and all existing installations of your theme will still receive updates. But it will not appear in any theme directory searches or tag views.

What if my theme meets the requirements, anyway?

If you believe your theme meets the requirements, then submit the request form! Were logging all the requests, so we have records of everybody who has made this request.

If I meet the old requirements, will I meet the new requirements?

No.

There are several new requirements that did not apply to the tag previously, so we expect that all authors will need to make theme updates.

Reviewed by @alh0319

#accessibility-ready

• Login to Reply

With: the feedback we received on the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both direct access (i.e. unassisted) and indirect access meaning compatibility with a persons assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)-ready requirements and the knowledge base during Contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what theyve learned throughout the year and share the joy. Learn more. Europe, as well as the work we did to process that feedback.

Read the recap of the Accessibility Teams work at WordCamp Europe 2026 for more details.

During the contributor day of WordCamp Europe, people at one table tested themes for the accessibility-ready tag. This gave us an excellent opportunity to see if the knowledge base works. We got useful feedback and the rest of the month we worked on processing this.

All the documentation for the accessibility-ready tag is now renamed Accessibility-ready program and is placed under one main menu item. Now the information is easier to discover and it gives us room to add more related documentation to this section. Some URLs have changed, we tried to catch all links but if you discover a still broken URLURL A specific web address of a website or web page on the Internet, such as a websites URL www.wordpress.org, please let us know.

Important feedback was: We need to enhance accessibility-ready guidelines with classic vs. blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. theme information and examples how to achieve the guidelines. More info about this in [issue #332].

The Last updated date now works thanks to @joedolson. So for example on Using headings in the content, the Last updated: May 22, 2026, at the bottom of the content with the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. data, is now correct.

Rian hopes to update and finish the documentation about how to test for accessibility in July.

#accessibility-ready, #wp-a11y-docs

Effective today, the theme accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both direct access (i.e. unassisted) and indirect access meaning compatibility with a persons assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)-ready guidelines have been updated. The new guidelines more closely adhere to Web Content Accessibility Guidelines (WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/.) expectations, although it continues to be the case that WCAG does not apply directly to themes; WCAG is a measurement for content, and themes are only a wrapper for your content.

Why are the accessibility-ready requirements changing?

The original requirements were written in 2011, and added to the theme review process in 2012. This was before WCAG 2.1 or WCAG 2.2 were published, and before HTML5 or ARIA had wide support and adoption.

Since 2012, general awareness of accessibility has increased, and the capabilities for creating more accessible websites have also improved. Its become increasingly important for WordPress Accessibility-ready requirements to modernize, to ensure that people implementing accessibility-ready themes are getting the best experiences.

Where can I find the new accessibility-ready requirements?

The theme review guidelines have been updated and are listed in the Accessibility section of the theme review handbook. The topics are currently being maintained on the Accessibility Teams documentation site. On that site, you can also find extensive guidance on all of the accessibility issues raised by the theme review requirements.

What has changed?

You should read the requirements for full details on what has changed. At a high level, here is a summary of changes:

• Guidelines for themes have been updated to only include requirements, and recommendations have been removed. Some recommendations have been made requirements; other recommendations have been removed as they are best practices and not blockers to receiving accessibility-ready tag approval.
• Requirement titles have been rewritten to clearly summarize the expectation.
• All guidelines now follow a standard format with the following sections:
  • Basic principle: explains what the requirement is and why it matters.
  • Testing: includes a list of tools needed for the testing process and detailed, numbered, step-by-step explanations on how to test the requirement, with clear pass/fail criteria at each step.
  • WCAG resources: links to relevant WCAG docs that apply to our requirement, for people who want to learn more.
• A standard process has been established for documenting testing in a Google Sheet, with a copyable template. The aim of this process is to make it easier for anyone to test, even without prior accessibility knowledge, and to ensure that theme developers receive consistent feedback, regardless of who tests their theme.
• Some new requirements have been added:
  • Support for reflow, resize, and text spacing changes
  • No unexpected changes of context
  • Content on hover or focus is accessible
  • Accessibility statement
  • Must not recommend or require inaccessible plugins

How can I learn more about the requirements?

The documentation is very detailed, and covers how to test each requirement. However, to help users understand the process from the beginning, @alh0319 will be hosting a webinar on Thursday, May 21st Global Accessibility Awareness Day. Shell walk through the entire process of testing a theme for accessibility-ready standards, and attendees will be able to learn by testing themes during the webinar.

If enough people sign up for the webinar, the aim is to get all of the current 108 accessibility-ready themes re-tested against the new requirements. @rianrietveld and @joedolson will be available to provide support and help testers work through challenges!

How does this impact my live accessibility-ready theme?

All accessibility-ready themes will be expected to update their themes to meet the new standards. Many of the requirements are essentially the same, but there are some new requirements as noted above.

Theme authors will have until June 30th, 2026 to begin the process of getting their themes updated either to update their accessibility, or to remove the tag.

Read the requirements, update your theme, then please request a review when youre ready!

Thanks & Props

The primary work on the new accessibility-ready guidelines was done by Amber Hinds, with assistance from Joe Dolson. However, many others have contributed to the long process of developing the requirements and the process for testing:

• @rianrietveld
• @jessicagoddard
• @miriamgoldman
• @slferguson
• @mpmike
• @christophermhinds
• @pirenko
• @clumi
• @Ryokuhi
• @Nadav
• @Tehila
• @oksankaa
• @akinom500
• @stuartpyper
• @nikunj8866
• @maxelementary
• @mirasus
• @vineettalwar
• Cam Coulter
• Karim Jetha

Did you help with this process, but dont see yourself in the list? Please comment below to let us know!

Additional thanks are owed to InstaWP, for donating their services to mount testing sites. You may wonder why this process isnt using Playground, which is already available on WordPress.org. Unfortunately, Playground renders inside an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the users browser., which breaks a number of key testing tools used to examine the content, particularly bookmarklets. It is possible to test within Playground, but considerably more labor-intensive.

The goal is to make it easier for anyone to contribute to theme accessibility-ready testing using common tools, and InstaWP makes this possible.

Reviewed by @alh0319 and @rianrietveld.

New and updated documentation: about alternative text for images, headings and links plus an introduction to WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/.. Featured content: Styling links.

Work in progress: documentation about how to test for accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both direct access (i.e. unassisted) and indirect access meaning compatibility with a persons assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), update of the info about the accessibility-ready tag in the themes handbook and figure out a section Can I use.

New and updated content, added in April 2026:

• Getting started:
  • Introduction to WCAG. Annelies Verhelst (@anneliesjenl ) wrote an explanation about what the Web Content Accessibility Guidelines are and how they relate to WordPress.
• Content and images:
  • Alternative text for images in the content.
  • Using headings in the content.
  • Write meaningful link text.
  • Images as links.
  • Link destinations.
• Design and user experience:
  • Styling links.
• Frontend code:
  • Alternative text for images, SVGs and icons in development.
  • Image animation and accessibility.
  • Heading structure in theme development.

Work in progress

At the moment we are working on extending and updating the docs about how to web accessibility.

In May 26 we want to update the information in the Themes handbook about the accessibility-ready tag. We updated the guidelines and the current info on Themes handbook about accessibility is outdated.

We are also discussing if and how to set up a Can I Use section for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks. With the status per blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. about its accessibility. All input is appreciated, we want to set something up that is not a ton of work, but is findable and informative for users. This may be a good topic to work on at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what theyve learned throughout the year and share the joy. Learn more. Europe 26.

All feedback on the documentation is very much welcome.

#accessibility-ready, #wp-a11y-docs

This update informs you about:

• new documentation;
• user feedback on the content structure;
• WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/.-EM audit on the website;
• plans for February.

New documentation

Amber Hinds and Joe Dolson wrote and published documentation for the new accessibility-ready tag guidelines for WordPress themes:

• Theme accessibility guidelines.
• Testing WordPress themes for accessibility.
• Documenting accessibility.

The documentation about web forms is almost ready, new is Provide help,
with:

• Allow copy/paste.
• Autocomplete.
• Avoid input patterns.
• Review, modify, undo.
• Provide valid values.

User testing

From user testing by Dutch frontent developers, we got ideas for a better organisation of the content structure. We are working on less items in the main menu and better in-page navigation to related content. That way content is better findable and can be found in multiple ways, not only by the search option or the main menu.

WCAG-EM audit

The website wpaccessibility.org got an official WCAG-EM audit, the site passes the audit for WCAG 2.2 AA compliance. We created an accessibility statement for the website.

Work for February 26

• Finish the reorganisation content
• Add a reading guide
• Finish all documentation about forms, next is Focus management in forms.
• Start with the documentation for the section Content and images
• Rian will give a presentation about the WP A11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both direct access (i.e. unassisted) and indirect access meaning compatibility with a persons assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Docs project at WPLDN in London on February 26.

All feedback on the documentation is very much welcome.

#accessibility-ready, #wp-a11y-docs

The AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both direct access (i.e. unassisted) and indirect access meaning compatibility with a persons assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team had a great turnout for Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what theyve learned throughout the year and share the joy. Learn more. Europe, including 14 people who were new to the accessibility team. Thank you to everyone who participated!

@joedolson and @alh0319 led two tables, focusing on accessibility testing themes that had requested the Accessibility Ready tag and addressing open accessibility tickets in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses blocks to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/.

During the day, contributors accomplished the following

Accessibility-Ready Theme Review

Several contributors reviewed all four themes that had requested the accessibility-ready tag. They provided feedback to theme developers about elements that need to be fixed before the themes can be approved for the tag.

@rianrietveld started reviewing the current accessibility-ready requirements and is putting together a doc with suggested updates and possible new items to include. The current accessibility-ready requirements are many years old and outdated. This doc is a work in progress, but the idea is to update the accessibility-ready tag requirements so themes with it will provide a better starting point to align with current best practices and accessibility standards.

@alh0319 is building a tool to walk contributors and developers through testing themes for the accessibility-ready tag. The idea for this tool is to make it easier for anyone to determine if a theme meets the accessibility-ready requirements and to generate reports that can be easily posted in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. when the tag is requested.

Weve also opened an issue to update the accessibility theme unit test data to better support accessibility testing of blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based and full site editing themes.

Core Tickets Worked On

Contributors worked on testing issues that have been reported and reviewing patches for tickets. The following tickets were worked on:

• Audit the usage of `aria-haspopup` in the admin menu: New patch completed to resolve issue
• Dynamically added notifications need ARIA role alert or status: Patch tested and confirmed
• Improve and extend focus styles for Windows High Contrast mode: Significant testing completed; some new issues identified and raised.
• The links hover color has insufficient color contrast: Significant testing completed
• Post editing area: keyboard accessibility, tab order and focus: Significant testing completed

Committed: #40331

Thank You to Contributors

Thank you to all the contributors who helped in-person in Italy and virtually via SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/! Here are some of the people who contributed:

• @alanfuller
• @alexapeduzzi
• @alh0319
• @Benjamin_Zekavica
• @christophermhinds
• @ireneyoast
• @joedolson
• @krokodok
• @marcoacato
• @marinakoleva
• @nuritnt
• @rade1
• @rianrietveld
• @rcreators
• @samuelsilvapt
• @tdrayson
• @zex2911

Please leave a comment if we missed you, and I will add you to the list of contributors.

#accessibility-ready

#accessibility-ready, #design, #website-redesign

#accessibility-ready, #design

#accessibility-ready, #design, #website-redesign

#accessibility-ready, #design, #website-redesign