Summary team chat, December 21, 2015

Accessibility standards for core

There where several comments on the post with the accessibility code standards for core.
@joedolson will add the relevant remarks. These standards will be added to the WordPress Coding Standards of the core Handbook.

Documentation

@trishasalas made a Google Doc with an overview of all the documentation that needs to be written for our handbook. More details about how to help her and contribute to the documentation in the blogpost Accessibility Handbook and Docs Update.

Tickets

#34957 #a11y-focus: Standardizing the handling of :focus and :hover
Moving forward, we’ve established that :focus is the primary transition for when a user interacts with a link or button. :hover is an extension of :focus that comes from a direct action, whereas :focus comes from an indirect action. Because :focus lacks a direct action, it needs to be styled in a way that brings clear visual attention to the element. Michael Arestad (@michaelarestad) is working on the visual update and we’ll move forward with implementing it once we have that complete.

#26601: Inappropriate content in headings on admin screens
Consensus is: ‘Add New Button’ === burn it with fire (agreed on by @michaelarestad)
@trishasalas will write a refreshed patch for this.

Next meeting

Next meeting will be in January 4, 2016 at 18:00 UTC

#accessibility-team-meetup, #weekly-meetings