The documentation working group will have a one time meeting on February 22nd at 17:30 UTC. We are going to discuss finalizing the structure of the Handbook as well as discuss strategy going forward. If you are interested in getting started with documentation this will be a great time to join in!
Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts
Core accessibility coding standards
@hearvox finished the Quick Start Guide in our Handbook. @rachievee is working to add other pages to expand on topics from the Quick guide that need longer explanations.
@trishasalas organizes a one time meeting on Februari the 22nd 17:30 UTC to discuss finalizing (for now) the structure for the handbook. In the meantime Trisha is going to begin writing the Plugin section of the Handbook.
Accessibility Test Team
Nimbus Hosting is so generous to sponsor the #wpa11y team with a VPS server. Here we can install a production, nightly and trunk version of WordPress and also have SVN and SSH access.
We will set the server up next week, then we’re up and running again and resume sending tests to our team.
Joe started to work on a fork of the theme unit test data, focused on accessibility testing – a smaller set of data, eliminating false positives in the data, etc. He will let us know when it’s usable.
The post with the requirements for the accessibility-ready tag has been improved. There is now more information on how to test a theme to help theme authors better.
@afercia: Investigation about color contrast continues.
#26601: Inappropriate content in headings on admin screens.
@trishasalas will write an new, refresed patch, keeping the add new link visually on the same place but placing it in the HTML outside the h1 heading
From Februari 16 on we will have an extra meeting to work on tickets. The group has grown so much last year that we need more time to discuss and work on core tickets then we have now in the regular meeting. This ticket meetings will be every Tuesday on 18:30 UTC.
And from everybody in the a11y team:
We wish @accessiblejoe a good and quick recovery!
The WordPress Accessibility Handbook now has a draft of a Quick Start Guide. The doc needs edits, comments, and vetting.
We intend this as a resource for developers to quickly grab WordPress-oriented code examples and a11y guidelines. Let’s make sure everything is accurate and clearly explained, and that nothing a11y-critical for WP dev is missing. (This process might also help us identify which topics need further explanations in other Handbook sections.)
Please review the draft and leave your comments on this post.
The accessibility code standards for WordPress have been added to the core handbook and are open for feedback over the next two week. Also see the Core blog announcement and the draft standards themselves!
The accessibility-ready guidelines for WordPress themes were updated today. There are no explicit changes to the requirements, but the order of the guidelines has been changed so that it corresponds more effectively to how it makes sense to run tests on the guidelines.
Additionally, I’ve added some information on how to run tests for each guideline into the guidelines, so that theme developers are more easily able to find information on how to self-test when they’re creating an accessibility-ready theme.
#34780: Updates screen: Plugin and Theme tables improvements
We discussed removing the scope from the th and td first and then think of a way to set up the layout, not in a table but in another, more semantic way.
#34625: wp-login.php site title link points to wordpress.org
We need to research if themes and plugins would break if the title attribute on the logo is removed. Maybe an option is to have no title output by default for the filter. @arush volunteered to own the ticket.
#35313: Remove title attributes: Posts, Pages, and CPTs screens
What to do with icons with a title attribute? For a sighted desktop user, the title attribute is the only indication what the icon means. There are many places where the link is just shown as an icon, and here the totle attribute was useful. We discussed how to solve this: we need to develop a core method to handle tooltips effectively. Andrea will open a ticket for this.
Color contrast: Some browsers do not support the styling of checkboxes and radio buttons. This means that in some browsers give that borders a poor contrast by default.
@afercia started to open tickets about the color contrast like #35497: List tables: Post format links improvements
@rianrietveld will make a list of all the color issues in the Admin, we can use as a reference to open new tickets.
Accessibility guidelines for core
@joedolson had some comments on the core a11y guidelines; just a couple, minor changes for clarity. Basically well received by the core team. Joe is waiting for a few more comments from members of the core team that did not have to chance to look at them yet.
Today I started to add subsections to the Accessibility Handbooks Contributor Spreadsheet and while I was looking over other Handbooks (Docs in particular) I decided it might be best to streamline content even further to separate Informational content about the team, mission, etc from the actual Resource for Developers. Documentation has a Docs Handbook for their section as well as links to other Handbooks for Developers. I’d like to see Accessibility follow that format and have reached out to @sewmyheadon and @topher1kenobe to get some insight into how they approached the process.
Join us in the meeting today, January 11 @ 18:00 UTC or comment here if you have any thoughts or additional ideas to help us move this project forward!
Thanks to everyone involved for all the help so far!
#33952: get_search_form() accessibility 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 core
@joedolson posted an updated link to the Accessibility Standards for Core document from last week. https://docs.google.com/document/d/1iySvDJ4duHYt6YlnnjnBNbU5LKAn1uRBMH8FKAfmswE/edit 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. https://docs.google.com/spreadsheets/d/1tOYzFn9vc7Ff4yGBmDajelrl7XMDUz4PR5H2lB4exI4/edit.
Next meeting will be in January 11, 2016 at 18:00 UTC
Hi accessibility folks! Thanks for all your hard work and contributions in 2015. Could you contribute few more minutes to fill in the 2015 contributor survey? It will help us establish some baselines around the contributor experience so that we can see how things change over time.
**This is being posted to all the Make teams, so if you subscribe to a bunch of p2s and keep seeing this post, know that you only need to fill the survey in once, not once per team.**
The survey is anonymous (so you can be extra honest), all questions are optional (so you can skip any that you don’t want to answer), and we’ll post some aggregate results by the end of January. It took testers 5-10 minutes to complete on average (depends how much you have to say), so I bet you could knock it out right after you read this post! 🙂
There are two sections of the survey. The first has questions about team involvement, recognition, and event involvement, and is pretty much what you’d expect from an annual survey (which teams did you contribute to, how happy are you as a contributor, etc).
The second section is about demographics so we can take a stab at assessing how diverse our contributor base is. All questions are optional, but the more information we have the better we can figure out what we need to improve. If there’s some information you’d rather not identify, that’s okay, but please do not provide false information or use the form to make jokes — just skip those questions.
The survey will be open until January 15, 2016. Whether you have 5 minutes now, or 10 over lunch (or whenever), please take the 2015 contributor survey. Thanks!
Note: I used polldaddy for the survey and I’m guessing there some accessibility issues. If any of you have trouble accessing the survey, please let me know what the issues are so I can pass it on to the polldaddy developer, and we’ll work out a way for your to respond in the meantime.
Here’s a collection of all the A11y resources I’ve found at WordPress.org sites (and two Google docs in use for drafting Handbook pages):
Make WordPress Accessible blog
Make WordPress Accessible> Accessibility Handbook
(Draft: outline for A11y Handbook) Accessibility Contributor Handbook
Make WordPress Accessible> Useful Tools
WordPress Accessibility> Theme Patterns
Docs Handbook> Handbooks Style and Formatting Guide> Accessibility
Theme Handbook> Accessibility
Theme Review Handbook> Accessibility
Theme Review Handbook> Accessibility> #resources
Theme Review Handbook> Accessibility> Resources
Theme Directory> accessibility-ready tag
Plugin Directory> WP Accessibility
Plugin Directory> Access Monitor
(Draft: guidelines for Plugins) WordPress A11y Code Standards
Accessibility code standards for WordPress core (similar to above)