Summary Team Chat for January 4, 2016


#33952: get_search_form() 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). ( improvements

The main issue when using `get_search_form()` is redundancy.  A lot of  “search, search for… search… search button”

Given that `get_search_form()` is used in both the admin & the front end as well as by themes it was determined that we will look at a uniform search for the 4.6 release.  In the meantime, we will remove the `title` attribute for a quick ‘win’.

#35187: Remove title attributes: the terms List Table

The current structure is semantically inaccurate but fixing it will require some design input to rework the list table layout. We have decided to stick with the original plan to remove the title attributes and find solutions for other issues at a later time.

Accessibility standards for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

@joedolson posted an updated link to the Accessibility Standards for Core document from last week. He has asked anyone who is interested to review and make comments.  He will eventually communicate with the core team to get this information into the Core Handbook.


During the next week I will begin adding sub categories to the sections in this spreadsheet.

The hope is to get more of a structure in place to make it easier to contribute.  So that, rather than needing to figure out where content will go you can pick a subcategory page and focus on the content for that page.
We also discussed consistency as well as what the need to be sure that any of the content we link to from the handbook is vetted by the Accessibility Team as a whole.

Next meeting

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

#accessibility-team-meetup, #weekly-meetings