Accessibility Team meeting notes – May 8, 2020

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). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Announcing the first WordPress Accessibility Day!

The first ever WordPress Accessibility Day was just announced this week:

Starting at 18:00 UTC on October 2nd, 2020, the WordPress Accessibility Team will sponsor a 24-hour online event focused on WordPress and Accessibility. If you want to learn about the future of accessibility in WordPress, join us for 24 hours of mind-expanding online learning!

Speaker submissions will be opening soon, so keep an eye on wpaccessibilityday.org.

A big round of applause to all the folks who’ve been working hard on planning and putting together this event. Please spread the word!

Review 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. https://wordpress.org/gutenberg/ PR

The team reviewed and discussed this Gutenberg PR that implements the roving tabindex pattern on 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. toolbar.

We agreed that this is a welcoming change but expressed concerns on how a change like this could be communicated to end-users.

Open floor

@afercia shared the work he’s been doing on #50105. Feedback and help testing the patch is needed.

#meeting-notes