Accessibility Team meeting notes for February 14, 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.

Discussion of the updated button component in 5.4

We discussed a recent update introduced to the Button component in 5.4. The team agrees that the implementation of fixed heights in buttons will break accessibility. Furthermore, this goes against the recent CSS changes introduced to wp-admin in 5.3

This topic led to a discussion about processes, the pace of development 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., and communication between teams. We agreed to come back to this concern next week, and address how, if possible, the Accessibility team can be more involved in the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. repository.

Feedback on the TabPanel component

We discussed this issue in the Gutenberg repository that requires accessibility feedback. A decision needs to be made in terms of how keyboard navigation should behave in a tabbed interface. We currently implement custom navigation for the tabs located in the editor inspector (Gutenberg sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.), while the WAI-ARIA Authoring Practices recommend a different approach. A summary of our feedback will be posted on the issue.