Accessibility Team Meeting Notes: May 7, 2021

These are the 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). ( Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Updates from the team’s working groups

Only teams that gave updates are listed.


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.

Full Site Editing (FSE)

  • The second Go / No Go Test was cancelled: the list of features that will be included in WordPress 5.8 can be found in the post about Full Site Editing next steps. Here is a list of items included in the scope, shared from the core-editor channel on Slack.
    • 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 building
    • Theme blocks (Query, Navigation, Site Logo…)
    • Template editing within the post editor
    • Widgets Editor & Block Widgets in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.
    • Persistent List view in the post editor
    • Duotone design tool
    • Gallery block refactor
  • The Global styles “interface” is not going to be included in 5.8, but Global Styles infrastructure which theme authors can use to build their themes is
  • Query Quest Summary for the latest call for testing. A community member did two different keyboard tests.
  • Round two of questions is open until May 12th and the next round of testing on template editing mode will ship on May 12th as well.
  • Template Editing Mode is gearing up to be an important feature most likely for 5.8 so getting testing done there would be very helpful. Tied to this, I expect testing for the Widgets Editor come up soon too. Of note, the current “opt out” approach seems to be through a new classic widgets plugin with more context in Add a plugin to disable the block based Widgets editor.


  • The Documentation working group is working on updating the Working Groups page.


  • In the last two weeks the Accessibility team checked all Enhancements / Feature Requests tickets, which are due by May 25. It’s seven tickets, so we should be able to get them committed in time.
  • There are also nine tickets marked as Bugs / Blessed Tasks, we’re starting to address them beginning next week, but still prioritizing Enhancements / Feature Requests.
  • Would like to clear the Awaiting Review queue, but will likely prioritize 5.8 milestone.


Open floor

  • The proposal by the team to add a new workflow keyword was shared during dev-chat, and both the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the Design teams were cross-linked. Feel free to add your thoughts to the post.
  • Because of concurring tasks, @ryokuhi and @alexstine won’t be able to facilitate the Accessibility bug scrub or meeting on May 21. @chaion07 has offered to lead the bug scrub and @joedolson has offered to lead the meeting.