Accessibility Team meeting notes – May 22, 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.

Preparations for team facilitators for WCEU Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus.

Those of us who have signed up to help and facilitate during WCEU contributor day were made aware of the latest updates and requests from the organizing team.

Updates on 5.5 projects

@audrasjb updated the team on the progress of Alternate list views, which is ready and awaiting reviews.

@afercia also shared that the removal of infinite scrolling from the media grid is also ready and waiting and accessibility review.

If you can, please help review those tickets and leave your feedback.

@nrqsnchz shared a WIP mockup of a dark, high-contrast theme for wp-admin as part of the accessible color schemes the team is working on.

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. issues

Edit mode: arrow up/down should not move to other blocks

The team continued the discussion on this Gutenberg PR that looks to improve navigation for screen reader users when in Edit mode.

We agreed that creating a setting or option that enables or disables WritingFlow would be a favorable path forward. There are still concerns about how this setting would be called and how obvious it could be. @alexstine left a summary of the team’s discussion on the initial issue.

Add screen reader only text format

The team also discussed this Gutenberg issue that proposes adding a text format option to mark text as screen-reader only.

The team agreed that this is a very interesting suggestion that could be beneficial in a variety of use cases. There is also concern about possible abuse or misuse of such feature, and the negative implications that it could have for accessibility.

@nickthegeek added a summary of our discussion to the issue.