Accessibility team update: August 4, 2019

WordPress 5.3 tickets

As of today, we have 75 accessibility focused tickets planned to ship with WordPress 5.3.

Therefore we have 38 open tickets without any owner. One of our main task next week will be to find owners for each ticket in the milestone.

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. 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). ( tickets

As of today, we have:

The Accessibility Team need more persons able to follow that closely.

Besides the fact that we try to be more numerous to take care of this work, we also evaluate the possibility to find ways to have more sponsored contributors (even a couple hours a week would be a great sponsorship!).

WordPress Accessibility Day organization

By the end of July, the Accessibility Team decided to evaluate the possibility of organizing a dedicated WordPress global accessibility event, like polyglots do with WordPress Translation Day (WPTD).

The idea is to organize a 24-hour virtual event all around the world with some video conferences and focused on contributing to WordPress accessibility.

A couple of weeks ago, a spreadsheet was shared so Accessibility team contributors could sign up to be involved in this organizing team. A dozen of people signed up to the organizing team.

The next step is to discuss the main focuses of the event and to divide the roles between the organizing team.

For information, WP Tavern already published a blog post about this initiative.

Various other tasks

  • Usage of .screen-reader-text class in accessibility documentation: Theme Review Team contributors raised some concerns about the current screen-reader-text class documentation. We are going to take care of rewriting the related docs and will work with Theme Review Team to ensure the new documentation is clear enough for theme authors and WordPress developers.
  • Theme Review Team Accessibility requirements: The team was asked to perform Theme Review Team blog post copy review for new accessibility requirements about keyboard navigation.
  • 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. Directory in WordPress Admin: the Accessibility Team raised some initial feedback for these early design. For reference, see first section of Meeting Notes from July 26 Accessibility team meeting.
  • Gutenberg: Support Navigation and Edit Mode: All meeting attendees agree that this is a good improvement. It would be necessary to be extensively tested by as many persons as possible, including users of assistive technologies. For reference, see first section of August 2 team meeting notes. The next Gutenberg PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party release is planned for August 12th. The Accessibility Team will publish a call for testers with some testing scenarios to test this big improvement.

#accessibility, #accessibility-team-meeting