{"id":14723,"date":"2020-05-29T23:47:33","date_gmt":"2020-05-29T23:47:33","guid":{"rendered":"https:\/\/make.wordpress.org\/accessibility\/?p=14723"},"modified":"2020-05-29T23:47:33","modified_gmt":"2020-05-29T23:47:33","slug":"accessibility-team-meeting-notes-may-29-2020","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/accessibility\/2020\/05\/29\/accessibility-team-meeting-notes-may-29-2020\/","title":{"rendered":"Accessibility Team Meeting Notes: May 29, 2020"},"content":{"rendered":"

These are the weekly notes for the AccessibilityAccessibility<\/span> 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 \u201cdirect access\u201d (i.e. unassisted) and \u201cindirect access\u201d meaning compatibility with a person\u2019s assistive technology (for example, computer screen readers). (https:\/\/en.wikipedia.org\/wiki\/Accessibility)<\/span><\/span><\/span> Team meeting that happens on Fridays. You can\u00a0read the full transcript on our Slack channel<\/a>\u00a0and\u00a0find the meeting\u2019s agenda here<\/a>.<\/p>\n\n\n\n

Prototype: move blocks between levels with keyboard<\/h2>\n\n\n\n

The team discussed this GutenbergGutenberg<\/span> 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 \u2018blocks\u2019 to add richness rather than shortcodes, custom HTML etc.\rhttps:\/\/wordpress.org\/gutenberg\/<\/a><\/span><\/span><\/span> PR that explores adding the ability to move blocks in and out of nesting levels with keyboard only.<\/p>\n\n\n\n

We agreed that is is a very welcoming and promising exploration. There was a particular interest in figuring out what would be the best way to communicate these position changes to screen readers.<\/p>\n\n\n\n

Accessibility audit of the new auto-update feature for plugins and themes<\/h2>\n\n\n\n

We discussed the recently merged auto-updates feature for plugins and themes from an accessibility perspective. There was discussion about how links that act like buttons should be handled, clarity of announcements, hiding icons, and button labels that change.<\/p>\n\n\n\n

@<\/span>ryokuhi<\/a> had the excellent idea of bringing some of these issues to next week\u2019s WCEU contributor dayContributor Day<\/span> 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 https:\/\/make.wordpress.org\/<\/a> There are many teams that people can participate in, each with a different focus. https:\/\/2017.us.wordcamp.org\/contributor-day\/<\/a> https:\/\/make.wordpress.org\/support\/handbook\/getting-started\/getting-started-at-a-contributor-day\/<\/a><\/span><\/span><\/span>.<\/p>\n\n\n\n

Please refer to the Slack discussion for a more detailed overview<\/a>.<\/p>\n\n\n\n

Documentation of Gutenberg\u2019s accessibility features<\/h2>\n\n\n\n

We discussed how to better inform users of the various accessibility features that are present on the blockBlock<\/span> 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.<\/span><\/span><\/span> editor. The idea of creating documentation and adding a link to it, such as \u201cAccessibility Help\u201d was well received.<\/p>\n\n\n\n

We agreed to bring back this topic on next week\u2019s meeting and look at all the different accessibility features and options that would be useful to have documented.<\/p>\n

#<\/span>meeting-notes<\/a><\/p>