The accessibility 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) tables where divided in two parts as always:
- people who wanted help understanding a11y 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) or needed a review of their work
- accessibility experts that wanted to help out
But now we also had developers from the Gutenberg 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/ and Yoast team who helped with the list of GitHub issues that still needs work.
Andrea Fercia led the Gutenberg work.
- Thanks to Adrian Roselli we came to a decision for: List block and screen readers: greatly inconsistent behavior. Basically it was decided to treat the List block 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. as all the other blocks with an editable area.
- We also discussed to try something new for: Simplify and streamline keyboard navigation through blocks. That is: trying the switch between navigation and edit mode using a visually hidden button for the switch (still to experiment)
- Jorge Costa started looking into Publishing Flow accessibility but there’s still lot to do there, so any testing and feedback is very welcome.
- Then the Review the usage of RichText multiline / aria-multiline issue was closed, thanks to Jorge.
- Issue Fix the blocks aria-label was solved by Irene Strikkers and Enej Bajgoric.
- We worked on refactoring of the landmarks to make them static and make sure all content is inside the landmarks
Meetings with other teams
Sami Keijonen and Rian Rietveld talked to the marketing team about how to promote/ integrate our handbook best practice section in the other teams documentation.
- Rian did a super quick review of Jetpack and showed Enej Bajgoric how to use some test tools like aXe.
- Adrian Roselli reviewed and helped improve the Minimal Share Buttons with Milen Petrinski-Gonzo
Thanks all of you so much for joining the 2 a11y tables.