Accessibility Team Meeting Notes: February 12, 2026

On Thursday, February 12, 2026, 15:00 UTC, a team meeting started in #accessibility kicked of by Nasim Miah and later continued by Krupa Nanda. You can read the full transcript or see the meeting agenda.

• WordPress 7.0 Release Party Schedule
  • WordPress 7.0 is scheduled for release on April 9, 2026. The proposed release party schedule has been published.
  • Beta 1 is scheduled in this week.
  • Enhancements need to be committed or moved to a new milestone before then.
  • Release parties will mostly take place on Thursdays (note: in the past they were typically on Tuesdays).
• Table Leads for WordCamp Asia 2026
  • The Accessibility Team is looking for Table Leads for WordCamp Asia 2026 Contributor Day.
  • Contributor Day will take place on April 9, 2026, at the Jio World Convention Centre.
  • We may consider having two table leads: one onsite and one supporting remotely.
  • If you’re attending and willing to take on this role, please fill out the application form shared on slack channel. Feel free to ping @krupajnanda for more details.
  • Remote support is also welcome.

Working Group Updates

Documentation

@rianrietveld shared an updates for docs part.

• A new menu and navigation structure has been implemented on wpaccessibility.org to improve scannability and navigation.
• The reading guide is nearly complete and helps visitors find relevant documentation more easily.
• Work is in progress on documentation for accessible focus management (to be added under web forms and frontend code).
• The team discussed updating the Accessibility Handbook to reference the new documentation (best practices section).
• Since redirects for popular pages are not possible, stub pages will be left in place to guide users to the updated content.
• Team members generally agreed that referencing the updated documentation is the right move.
• Feedback on the new docs is welcome.

General Updates

• Beta 1 for WordPress 7.0 is in this week only.
• The team believes work is on track.
• Bug scrub this week will focus on items needing decisions before Thursday.
• If you’d like to follow accessibility-related progress in 7.0, refer to the Current Release Progress page.

Gutenberg

• The new Tabs block was reviewed and several issues were identified and the editor team is handling the reported issues promptly.
• No major new accessibility concerns are currently known for the upcoming release, though continued testing is encouraged.
• The list of open issue for tabs block.

Themes

• The new accessibility-ready guidelines were presented two weeks ago.
• No feedback has been received yet; the team may follow up.

Open Floor

A question was raised about accessibility standards for color schemes in the admin area (specifically under the “User Profile” section).

Clarification:

• Default themes are required to meet WCAG standards.
• Alternate themes (opt-in) are not required to meet WCAG.

#accessibility, #meeting-notes