Accessibility Team Meeting Notes: July 16, 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 📣

• WordPress 7.1 Beta 1 is released
• Guide to WCUS 2026
• WordPress 7.0.1 Maintenance Release

Discussion on proposed team restructure

The team discussed reorganizing the Accessibility Team’s focus areas on the Get Involved page by replacing the existing working groups with three primary focus areas:

• 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

Docs

• Several accessibility documentation updates were published, including refreshed accessibility testing guides and an updated page on accessibility legislation.
• The Accessibility Team Handbook is being migrated 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/ and simplified to focus on team information and contributor onboarding, while accessibility guidance will remain on wpaccessibility.org.
• The proposed handbook updates also reflect the team’s new focus areas in place of the previous working groups.
• Documentation work will continue with improvements to content discoverability, including better cross-linking, a user sitemap, and an updated reading guide.

General & Gutenberg

• With WordPress 7.1 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 released, the team’s focus has shifted to bug fixes and accessibility testing ahead of RC1. One remaining enhancement is expected to be included in Beta 2.
• Contributors were encouraged to review recently introduced features, including Notes, client-side media and media editing, lightbox captions, the Tabs and Playlist blocks, revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision., the Identity panel, and Command Palette updates.
• The team also reviewed the progress of accessibility work for WordPress 7.1, with 24 accessibility-related TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets completed and 16 still open for the release cycle.

Themes

• Accessibility-ready theme reviews continue to progress, though work remains slow due to the size of the existing backlog.The team discussed extending the review deadline, with the end of September suggested as a more realistic target.
• A formal announcement will be made once the new timeline is finalized.Review efforts will continue to prioritize themes whose authors have requested re-reviews, followed by themes that have shipped updates.

#accessibility, #meeting-notes