Accessibility Team Meeting Notes: August 28, 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). ( Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

WordPress 5.5 release post-mortem

The team shared and discussed what we thought went well and went wrong with our team’s projects and tasks during the release of WordPress 5.5.

The issue of not enough early involvement and feedback during design and development updates to 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. editor was brought up a few times and discussed at length. We all agreed that the process needs to be improved and our team is still very limited in terms of time and resources.

We agreed to explore solutions and ideas that would help us improve this cycle and follow-up in a separate document or post. @sarahricker volunteered to put all of this feedback together.

Team goals and priorities for WordPress 5.6

We reviewed the suggested projects and priorities that were added to the call posted earlier this week. After some discussion and a show of hands, the following projects gathered enough interest and participation:

  1. Updating the WordPress Accessibility coding standards from WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) 2.0 to WCAG 2.1 and document accessibility anti-patterns
  2. Accessibility of the WordPress 2021 default theme
  3. A feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. to create an “Accessibility Statement” tool with features equivalent to Privacy Policy Tools

All other items on the agenda that couldn’t be covered will be added to next week’s meeting agenda.