Accessibility Team Meeting Agenda: November 19, 2026

This is the proposed agenda for the bi-weekly 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting on Thursday, November 199, 2026 at 08:30 PM GMT+5:30

📣 Announcements

Working groups

  • WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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. Editor
  • Accessibility-ready Program
  • Documentation about Web Accessibility

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub is every Tuesday at 16:00 UTC, held in the #accessibility channel on the Make WordPress 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/ (registration required).

#accessibility, #agenda

Accessibility Team Meeting Notes: November 05, 2026

These is the bi-weekly notes for 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on alternate Thursday in #accessibility. You can read the full transcript here or see the full meeting schedule.

📣 Announcements

The following updates and announcements were shared:

Working Group Updates

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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. Editor

  • WordPress 7.2 is nearing the end of its Beta phase. The remaining theme-related items are expected to be completed within the week.
  • There are currently 22 accessibility tickets open in the WordPress 7.2 milestone. Joe Dolson aims to resolve all remaining tickets by the Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. (RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.) phase.
  • A total of 41 accessibility tickets have already been closed during this release cycle.
  • Joe will also be reviewing the new default theme, drawing on his recent accessibility reviews of Twenty Twenty-Three through Twenty Twenty-Five.
  • Due to travel and other commitments, Joe will be unavailable for the next two Tuesday bug scrubs, including November 17. An alternative bug scrub may be scheduled to review new tickets during the RC phase and help prepare for WordPress 7.3.
  • Team members are welcome to volunteer to run the bug scrubs in Joe’s absence. Please comment on this post or in #accessibility if you are planning to facilitate the bug scrub.

2. Accessibility-ready Program

  • Joe has coordinated with Otto on the upcoming changes to accessibility-ready tag management in the Theme Directory.
  • The plan is to make the updated tag management process live as soon as possible while keeping all currently tagged themes visible initially.
  • Theme assignments will then be updated gradually as reviews are completed, rather than making a single change to the entire directory.
  • William Patton offered to help manage theme assignments once the updated process goes live. He also confirmed that he should have the necessary access to make these changes.
  • Having additional team members who can manage tag assignments will help distribute the work and keep the process moving.
  • The team hopes this will also help resume progress on the pending theme reviews.

3. Documentation About Web Accessibility

  • @rianrietveld is working on defining the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. specification for migrating content from wpaccessibility.org into a format suitable for publication in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Developer Hub.
  • The intention is to continue maintaining the primary documentation on wpaccessibility.org, where the team can provide a more accessible interface, while using a continuous integration process to keep the content synchronized with a WordPress.org-friendly format in the repository.
  • Once the specification is ready, development assistance will be needed to turn it into an actual migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. script.
  • Joe will review the documentation throughout November while Rian continues working on completing the remaining content.
  • The goal is to have the documentation largely ready by December.
  • The team can publish a call for development help once Rian gives the go-ahead and the API specification is finalized.

Open Floor

There were no additional questions or discussions during the open floor. As most participants were unavailable, the open floor was skipped for this meeting.

Thank you to @joedolson for sharing the working group updates and to everyone who continues to contribute to the WordPress Accessibility Team.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

Wishing everyone celebrating a happy Diwali and a prosperous New Year! ✨

#accessibility

Accessibility Team Meeting Agenda: November 05, 2026

This is the proposed agenda for the bi-weekly 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting on Thursday, November 05, 2026 at 08:30 PM GMT+5:30

📣 Announcements

Working groups

  • WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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. Editor
  • Accessibility-ready Program
  • Documentation about Web Accessibility

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub is every Tuesday at 16:00 UTC, held in the #accessibility channel on the Make WordPress 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/ (registration required).

#accessibility, #agenda

WP A11y Docs update October 2026

This update informs you about:

  • Remaining documentation for wpaccessibility.org.
  • 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team Handbook on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/.
  • Preparations for publication of the docs on developer.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/

Remaining documentation for wpaccessibility.org

In October Rian wrote the remaining content listed in the Tracking issue Content pages: create or review or rewrite. This resulted in 11 pull requests. Joe Dolson plans to review these PRs in November, when he has hopefully more time, next to his accessibility work for WP coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

Accessibility Team Handbook on GitHub

The maintenance of the WordPress Accessibility Team Handbook has moved to GitHub in the repository WordPress/accessibility-team-handbook. Moving the Team Handbook to GitHub makes it easier to maintain, allows anyone to suggest changes, and provides better visibility into document history.

Preparations for publication of the docs on developer.wordpress.org

We are writing the specifications for an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to synchronize the documentation on wpaccessibility.org with a new section on developer.wordpress.org called Accessibility.

The following sections from the WP Accessibility Knowledge Base on wpaccessibility.org will be published on the WordPress Developer Resources:

For context: we will have two different resources:

  • The WordPress Accessibility Team Handbook on Make/WordPress, about the team, how to contribute or report issues.
  • The WordPress Accessibility Handbook in the Developer Resources, that will contain information about accessibility itself.

#wp-a11y-docs

Accessibility Team Meeting Notes: October 22, 2026

These is the bi-weekly notes for 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on alternate Thursday in #accessibility. You can read the full transcript here or see the full meeting schedule.

📣 Announcements

Working Group Updates

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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. Editor

  • WordPress Core has entered the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. phase, and all remaining enhancements have been moved to WordPress 7.3. The focus is now on bug fixes, with around 20 tickets still open, most of which have patches and are progressing well.
  • An accessibility review of the new default theme is a priority. Joe Dolson will coordinate the review.
  • Since the new default theme has been committed to SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/., further changes will need to be tracked through WordPress TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. The GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ repository will be archived, and changes may need to be moved to Trac and PRs opened against the wordpress-develop repository.

2. Accessibility-Ready Program

  • Reviewing all remaining themes is taking considerable time. The team may proceed with the current review incomplete, leaving themes without completed reviews in the tag until their reviews are resolved.
  • Joe has developed a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. that automatically inserts a theme’s own block patterns while excluding unrelated and nested patterns, reducing duplicate testing and simplifying the review process.
  • The plugin will be included and activated in the recommended InstaWP template. The testing instructions will also be updated, and the plugin will be made available for those using other testing setups.
  • With this change, template parts will no longer need to be tested separately on the block patterns page, as they should already be covered when testing the relevant pages.

3. Documentation About Web Accessibility

Open Floor Discussion

Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. Roles for 2026–2027

  • @krupajnanda expressed interest in continuing as a Team Rep for another year and received support from Joe Dolson and Rian Rietveld.
  • The team discussed whether to bring in a second Team Rep. Krupa is comfortable continuing independently if needed but emphasized that anyone taking on the role should remain actively involved and follow through on their responsibilities throughout the term.
  • The team agreed that consistency and communication are essential. Since these are volunteer roles, stepping down when circumstances change is acceptable, provided the person communicates rather than becoming inactive without notice.
  • There is no immediate need to appoint a second representative; the decision can be revisited later if additional support is needed.
  • @muddassirnasim’s continuation remains unconfirmed. Joe will treat the lack of a response by the end of the month as a tacit resignation.

Ipsum : New Default Theme

Thank you @joedolson and @rianrietveld for providing updates and thanks to everyone who joined and contributed to the discussion!

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

#accessibility, #meeting-notes

Accessibility Team Meeting Agenda: October 22, 2026

This is the proposed agenda for the bi-weekly 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting on Thursday, October 22, 2026 at 08:30 PM GMT+5:30

📣 Announcements

Working groups

  • WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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. Editor
  • Accessibility-ready Program
  • Documentation about Web Accessibility

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub is every Tuesday at 16:00 UTC, held in the #accessibility channel on the Make WordPress 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/ (registration required).

#accessibility, #agenda

Accessibility Team Meeting Notes: October 08, 2026

These is the bi-weekly notes for 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on alternate Thursday in #accessibility. You can read the full transcript here or see the full meeting schedule. The biweekly Accessibility Team meeting was kept brief, with updates shared asynchronously, as WordPress Accessibility Day 2026 just concluded before the meeting.

📣 Announcements

  • WordPress Accessibility Day 2026 took place online on October 7–8, featuring 24 hours of free sessions focused on digital accessibility.
  • The tentative WordPress 7.2 release party schedule was announced, with the release planned for December 8, 2026.
  • WordPress 7.1.3 was released with maintenance and security fixes.
  • Additional updates included CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. and GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ spring cleaning, progress on the Presence APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., and the release of 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/ 24.1.

Working Group Updates

WordPress Core and 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. Editor

  • WordPress 7.2 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is approaching, with significant work planned over the next two weeks. Overall progress is looking good.
  • Ticket #66018: Needs a contributor to take ownership and prepare a PR. Without progress, it may be moved to a future release.
  • Ticket #50486: Expected to be committed soon. Additional testing would be appreciated.

Accessibility-Ready Program

  • The delay in the accessibility-ready theme verification process has been communicated, with a resolution expected in approximately one week.
  • Contributors available to help follow up on accessibility-ready themes are encouraged to contact @joedolson, as considerable work remains to finalize the process.

Documentation about Web Accessibility

  • The Design and User Experience section of the Accessibility Knowledge Base has been completed.
  • @Rian Rietveld will continue writing and updating the remaining topics in the Frontend Code section.

Open Floor

  • No urgent issues or additional agenda items were raised.

Thanks to @joedolson and @rianrietveld for providing the working group updates, and to @afercia for joining the meeting.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

#accessibility, #meeting-notes

Accessibility Team Meeting Agenda: October 8, 2026

This is the proposed agenda for the bi-weekly 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting on Thursday, October 08, 2026 at 08:30 PM GMT+5:30

📣 Announcements

Working groups

  • WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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. Editor
  • Accessibility-ready Program
  • Documentation about Web Accessibility

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub is every Tuesday at 16:00 UTC, held in the #accessibility channel on the Make WordPress 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/ (registration required).

#accessibility, #agenda

#accessibility, #agenda

Accessibility-ready directory changes coming!

Work is largely completed for making the accessibility-ready tag conditional in the theme directory, as proposed in meta trac ticket #8427. There’s a little bit more work to be done to set up the changes, which is going to briefly delay implementing the updates to what themes will be listed in the tag.

The important details for theme authors and reviewers to know:

  • With this change, no themes will be delisted from the directory because they have not yet met the requirements for the accessibility-ready tag.
  • Adding the accessibility-ready tag will not delay getting your theme approved, and will be treated as an application to be added to the listings.
  • The value of the accessibility-ready tag as a signal of trust will be considerably higher, as we will be able to directly remove that listing from themes that do not meet our 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) guidelines.

In the meantime, take a moment and check out the schedule for WordPress Accessibility Day 2026, which starts this Wednesday! We’ve got a schedule packed with great information covering a wide range of accessibility topics – if you haven’t registered yet, it’s not too late!

#accessibility-ready

WP A11y docs update September 2026

With:

  • New and updated documentation.
  • MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of 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 person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team Handbook.
  • Our plans for October.
  • The roadmap of the project.

New and updated documentation

In standards and best practice:

Migration of the Accessibility Team Handbook

We are moving the maintenance of the Accessibility Team Handbook over to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ in the repo WordPress/accessibility-team-handbook, @coffee2code is helping. The reason for the migration is that more people can contribute to the content of the handbook when it’s on GitHub.

Our plans for October

We continue to work on getting the issues done in the Tracking issue Content pages: create or review or rewrite, and hopefully get the migration of the Accessibility Team Handbook finished.

The roadmap of the project

As a reminder, this is the roadmap:

  • Phase 1: finish the content of the Knowledge Base, we hope to achieve this soon.
  • Phase 2: Sync the content in the Knowledge Base with a new section in developer.wordpress.org called accessibility.
  • Phase 3: Read through the accessibility information on wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and decide if content needs to be updated or point to Knowledge Base on developer.wordpress.org. We want to keep one source of truth to avoid duplication and outdated info.
  • Phase 4: Maintenance. WordPress, web techniques, and accessibility change, we want to keep the documentation up-to-date.

Rian explains the roadmap in more detail in the interview with @mbootsman: Rian Rietveld on the Four Phases of the WP Accessibility Project.

#wp-a11y-docs