Accessibility team update for December 11, 2017

Transcript meeting in Slack

Handbook

The writing continues steadily, we still hope to finish the best practices mid March.

In the meantime we need to set up a marketing plan for the handbook. @samikeijonen and @postphotos want to work in this, with the help of the Marketing team (@mcdwayne, @gidgey and @anafransilva).

Thoughts and ideas are in the Google doc: Marketing plan for accessibility handbook.
We will continue the discussions in the SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel #accessibility-docs.

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/

The Gutenberg inserter has been tested at the contributors day at WCUS and by @abrightclearweb

The the Gutenberg toolbar roving tabindex is still on the to-do list.

Note from @afercia: The roving tabindex thing is implemented for now just on the Inserter “tabs”. The point is, consider to use the same technique for the toolbar too?
See Toolbar: consider to use a roving tabindex and standardize navigation · Issue #3383

It’s well explained in the ARIA Authoring Practices example. Worth noting there’s now an option to set the toolbar in different positions:

  • docked to the top
  • floating on top of each 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.

Further more we need urgent frontend testers/reviewers/devs for the issues Sami created om GitHub to prevent inline style going into the frontend code. There have been good conversation about inline styles in Proposal of removing inline styles · Issue #2862.

Items on the To-do list

  • Prevent frontend style getting in Gutenberg
  • Research screen reader performance for code short codes like [ php ] or [ htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. ] – action Sami, if he has time
  • Write up a summary of things that will change in WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.1 for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and design – action Rian, next week

#accessibility-team-meeting