Accessibility Team Meeting Notes: August 5, 2022

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 SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel and find the meeting’s agenda here.

Accessibility 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. nominations

@ryokuhi posted a Call for Team Rep Nominations on 15 July 2022, asking team contributors if they were interested in taking the role he has held for a more than two years.

@sabernhardt was nominated by @joedolson and @ryokuhi, but he had already expressed his doubts at the time of the nomination.

The call stays open for now until further notice.

Accessibility of pattern previews in theme pages

In a message on the channel, @poena had asked to discuss the new feature adding pattern previews to individual theme pages, which had an issue that prevented navigating through the pattern list when using keyboard only.

By the time of the meeting, the issue had been solved, but the new interface would still benefit for some extra accessibility testing: findings might be added as comments to the ticket on Meta Trac about adding pattern demos to themes and new bugs can be reported by creating new tickets on 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. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. @Ryokuhi reported that he was able to spot a couple bugs while quickly testing.

Updates from the working groups

Only groups that provided updates are shown below.


@ryelle shared that the 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. redesign is underway and that the current progress can be viewed on the staging site. Bespite being still in progress, accessibility feedback on the homepage and the download page is welcome and can be added to the repository of the block-based theme.


@azhiyadev reported that a few minor changes were made last week. She invited everyone who spot anything that needs updating to let her know and that she’ll try to dedicate more time to the team, as far as daily job allows it.


@ryokuhi reported that the Team is keeping track of tickets in the Awaiting Review queue (at the time they were 12) and of tickets milestoned for the 6.1 release: at the moment, 17 of them are still open and 10 of them have already been committed.

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.

In a message posted before the meeting, @get_dave asked for accessibility feedback on the Pull Request about adding custom labels to blocks in list view. @joedolson already gave a quick feedback, but such a feature could use some more feedback.


@poena completed a review of the accessibility of the Twenty Twenty-Two theme and added the findings as a comment to the ticket about adding the accessibility-ready label to the Twenty Twenty-Two theme. The only issue is that the aria-hidden attribute is missing from icons in the query pagination: such an issue has already been addressed in Gutenberg and will be included in the 6.1 release.

She also asked if the team wants to use the accessibility-ready tag for 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. themes at all: it was decided to rediscuss this issue during the meeting happening on September 2, 2022, inviting contributors to Gutenberg and to the Themes Team to attend to have a preliminary discussion about the topic. After that, discussion can continue through comments to a post published on the Accessibility Team blog or by bringing discussion to a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chat.

Open floor

@joesimpsonjr reported that he submitted information about Table Leads for the Accessibility Table 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. US 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 There are many teams that people can participate in, each with a different focus., happening on Sunday, 11 September 2022: @joedolson and @joesimpsonjr will be present all day long, with @alexstine possibly joining for part of it and @ryokuhi available remotely through Slack. They will prepare a list of small potential tasks people can look at, covering a broad spectrum of knowledge bases and specialties, including docs, testing, coding, etc.

Congratulations to @joedolson and @alexstine for being accepted as speakers for WordCamp US!

@ryokuhi won’t be able to attend the bug scrub on 26 August 2022, but @chaion07 volunteered to facilitate it.