Accessibility Team meeting notes for 6 December 2019

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.

Proposed times for the Global WP Accessibility Day initial planning meeting

A set of dates have been proposed for the upcoming planning meeting for the Global WP Accessibility Day. Folks interested in participating are encouraged to join the #accessibility-events channel in SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at (requires registration) and vote for a date.

Advancing 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. Interface

At last week’s meeting, we brought up this Gutenberg GitHub issue that is exploring the current constrains of the block’s toolbar and is proposing some updates that will make it more usable and robust. Being a long issue that goes into a lot of depth, we agreed last week to give everyone some time to digest it and revisit the topic during this meeting.

Those who had time to review it shared their thoughts. The conversation also touched on process and how there’s still room for improvement when it comes to these kind of proposals.

Folks are encouraged to leave feedback and comments on the issue.

Updates on 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. focus handling research work

We revisited the research work that started a few weeks ago on focus handing of Gutenberg blocks. The team made a lot of progress and we’ll revisit the topic next week once we’ve had more time to go over the results.

New Welcome Guide modal in Gutenberg

This pull request from the Gutenberg GitHub repo was brought up because there are still some implementation issues that need to be addressed.

It was suggested that the modal component be set with a role=dialog, and since we can’t predict what kind of content will live within the modal, a role=document be used for the content.

The team also discussed usability issues present on the modal. All this feedback has been summarized and added to the PR.

WAI-ARIA compliant custom select

While extensive accessibility testing has been performed on this component, there are still improvements to be made.

The conversation also touched on accessibility testing process and documentation and ways we could improve it. We agreed to explore the idea of creating documentation for baseline accessibility testing procedures and expectations.