Image Krupa Nanda 8:40 am on July 3, 2026
Tags: ,   

X-post: WordPress 7.1 Release Party Schedule

X-comment from +make.wordpress.org/core: Comment on WordPress 7.1 Release Party Schedule

Image Krupa Nanda 9:29 am on July 1, 2026
Tags: ,   

Accessibility Team Meeting Agenda: July 02, 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, July 02, 2026 15:00 UTC

Announcements 📣

Proposed Discussion

Team perspective on the use of pure white text on dark backgrounds (and vice versa), including 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/. 3 and APCA research. (Proposed by Afercia.)

Updates from the working group

  • Documentation
  • General
  • 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/
  • Themes

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

Image Rian Rietveld 7:29 am on June 30, 2026
Tags: ,   

WP A11y Docs update June 2026

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 person’s 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 they’ve 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 Team’s 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 website’s 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

Image Isotta Peira 12:11 pm on June 29, 2026
Tags: ,   

X-post: WordPress Credits Updates

X-comment from +make.wordpress.org/project: Comment on WordPress Credits Updates

Image Krupa Nanda 6:42 am on June 23, 2026
Tags: ,   

Accessibility Team Meeting Notes: June 18, 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.

  • Core Committers WCEU recap is published.
  • Check out What’s new for developers June 2026
  • What’s new in Gutenberg 23.4? (June 17, 2026)
  • Discussed accessibility considerations for how different types of contributions are recognized and represented in the new 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/ contributor activity tracking system.
    • The Accessibility Team created a shared Google Doc to brainstorm and define criteria for tracking contributor activity and impact, aiming to avoid subjective human judgment in the process.
    • @Rian Rietveld suggested that the Google Doc should also cover how contributions are tracked and what constitutes “meaningful” contribution.

The WordPress 7.1 release squad announcement

The WordPress 7.1 release squad has been announced, with @joedolson and @Aki Hamano serving as tech leads, ensuring accessibility will be a top priority for the August 19, 2026 release.

Docs

General and Guternberg

  • Progress was limited during the WordCamp Europe week, with more active development expected in the coming weeks. Priorities for the WordPress 7.1 release began to take shape following the announcement of the release squad.

Themes

Themes Updates

  • Significant progress was made on re-reviewing accessibility-ready themes, with additional work still remaining.
  • The previously announced June 30 deadline was expected to be treated as a milestone for themes to begin the review process rather than complete it.
  • The post will be published with updated guidance to clarify the review expectations if needed.

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

Image Rian Rietveld 7:57 pm on June 19, 2026
Tags: wceu   

A11y at WordCamp Europe ’26 in Krakow

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 they’ve learned throughout the year and share the joy. Learn more. Europe happened on June 4-6, ’26 in Krakow, Poland.

At 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/ 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 had 3 full tables. One table focused on testing themes for the accessibility-ready tag, one on fixing issues in 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/ and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and one on reviewing the documentation in the WordPress Accessibility knowledge base. During the WordCamp, Joe and Rian had numerous discussions with attendees about how to optimize the accessibility-ready tag documentation and other documentation on wpaccessibility.org.

Testing themes

Amber Hinds (@alh0319) wrote a very helpful document with step by step instructions on how to test for the accessibility-ready tag. The team intends to re-use this document and add it to our handbook in the section “Get involved“.

8 Contributors tested and notified theme authors about issues in their themes, working on reviews for several additional themes.

Core and Gutenberg issues

5 Contributors worked on patches for two core tickets, updated numerous issues, and provided several tickets with feedback.

Reviewing Documentation

8 Contributors reviewed documentation on wpaccessibility.org. These reviews are bundled and documented in 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/ Tracking issue Feedback contributors at the contributor day WCEU’26. We will create separate issues the next few weeks so we can start working on them.

Thank you!

Thank you Claire Brotherton (@abrightclearweb), Jeff Chi (@krokodok), Łukasz Zygiel (@lukaszygiel), Remo (@Remo), Maja Benke (@majabenke), Veera (@veerap), Maud Leray @mleraygp), Anne-Mieke Bovelett (@annebovelett), Tibi Buzdugan (@tibibuzdugan), Simon Duduica (@simondud), Carolina Romo (@corazondejaguar), Željko Milošević (@zex2911), Mira Hiltunen (@mirasus), JB Audras (@audrasjb), Francisco Guarnieri (@franciscovitamina), Ankit Kumar Shah (@ankitkumarshah) and others for joining and helping at the accessibility tables

If your name and handle are missing from the list, comment below, so it can be added!

Useful discussions during the other WordCamp days

  • Information about the accessibility-ready tag primarily focuses on testing. Jessica Lyschik (@luminuu) wants to add information on how to implement the accessibility-ready tag, to better support theme developers. Related GitHub issue: Enhance accessibility-ready guidelines with classic vs. block theme information and examples how to achieve the guidelines.
  • Sami Keijonen (@samikeijonen) wants to help reviewing PRs in GitHun for new documentation
  • Joe and Rian sat down with the Playground team and helped them on their way with how to test for accessibility. We realized that the documentation about automated testing needs an update, as the info we have now is outdated.
  • Joe and Rian talked to Milana Cap (@milana_cap) about core documentation. Rian is going to write a short section about web accessibility with useful links for an accessibility Documentation section on wp.org
  • JB Audras (@audrasjb) is translating relevant info from the Knowledge Base into French for fr.wordpress.org/support. This may be something to discuss with other local communities.

The attending members of the team came back with a ton of ideas, to be followed up in the next months. Thanks everyone!

Reviewed by @joedolson

#wceu

Image Krupa Nanda 4:14 am on June 19, 2026
Tags: ,   

X-post: Roadmap to 7.1

X-comment from +make.wordpress.org/core: Comment on Roadmap to 7.1

Image Krupa Nanda 1:19 pm on June 17, 2026
Tags: ,   

Accessibility Team Meeting Agenda: June 18, 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, June 18, 2026 15:00 UTC

Updates from the working group

  • Documentation
  • General
  • 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/
  • Themes

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

Image Krupa Nanda 8:07 am on June 12, 2026
Tags: ,   

X-post: Call for Testing: Unicode email addresses.

X-comment from +make.wordpress.org/core: Comment on Call for Testing: Unicode email addresses.

Image Krupa Nanda 9:29 am on June 9, 2026
Tags: ,   

Accessibility Team Meeting Notes: June 04, 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.

  • 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 they’ve learned throughout the year and share the joy. Learn more. Europe held last week, and contributors were encouraged to join the Accessibility Team table 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/.
  • The Accessibility Team shared updates on ongoing documentation improvements for May 2026.
  • The call for volunteers for the WordPress 7.1 release is closed.
  • Contributors were reminded that one week remained to apply as a speaker for WordPress Accessibility Day.
  • A hotfix addressing the publish button placement issue was released.

Docs

  • @rianrietveld shared an update that work on improving the Accessibility Team documentation continued.
  • During WordCamp Europe Contributor Day, attendees reviewed the new documentation and provided valuable feedback to help refine and improve the content.

General

  • @joedolson shared that most tickets milestoned for 7.1 already have patches, so the focus of bug scrubs over the coming weeks will be on reviewing those patches and confirming they still apply correctly.
  • It was also mentioned that some bug scrubs may need to be rescheduled due to scheduling constraints. Any schedule changes will be communicated as far in advance as possible.

Gutenberg

  • @joedolson shared that the 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/ team is still primarily focused on polishing items that missed shipping in the 7.0 release.

Themes

Only four weeks remain to complete re-reviews of all current accessibility-ready themes. By June 30, all accessibility-ready themes are expected to be either:

  • Approved,
  • Actively in progress with participation from the theme author, or
  • Delisted if they do not meet accessibility standards and there is no evidence of author engagement to address the identified issues.

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