Accessibility Team Meeting Notes: June 5, 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.

Documentation of 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/’s accessibility features

We continued the discussion about documenting the features present in Gutenberg that help make the editor more accessible and the best way to bring awareness to them.

We agreed that this documentation should be easy to find and not buried or hidden under a menu. Some of the features we think would make part of this documentation are:

  • Edit and select modes
  • 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. Navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. and block breadcrumbs
  • Top toolbar
  • Spotlight mode

We agreed to continue this discussion next meeting.

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

As @audrasjb steps down from being a team rep to focus more of this time on the Core team, the team is planning to launch new team rep nominations during the next team meeting. @nrqsnchz will continue to be team rep and the new person to fill JB’s place will share tasks and responsibilities with him.

Open floor

@afercia reminded everyone of the list of tickets that need help from the Editor and Media teams. @audrasjb will be reaching out to those teams.

Andrea also asked if there has been any progress or updates on the PR for addressing accessibility concerns of WritingFlow. There’s been consensus around creating a setting to turn this feature on and off and those involved are currently discussing how to call this setting in the PR.

#meeting-notes