The Last 3 Weeks in WPa11y!

Accessibility Tickets in 4.8

These are the current accessibility related tickets slated for the 4.8 release:

  • #35566 removes the title attribute in the tag cloud widget
  • #38768 adds the site title as the alt attribute to the custom logo

WordPress 4.8 introduces a few new media widgets as well as the ‘Nearby Events’ widget. Testing should continue to be sure that new accessibility issues aren’t introduced.

Future Releases

If you would like to have an impact on future WordPress releases join us during our bug scrubs! During bug scrubs we go through the “awaiting review” and “future release” reports.
Gutenberg Editor

The Gutenberg Editor is slated for a big reveal at WordCamp Europe.
Let’s keep testing for accessibility related issues as development continues.

You can find installation instructions here: https://github.com/WordPress/gutenberg/blob/master/CONTRIBUTING.md

Note that it is not a conventional plugin so there are some specific steps to follow.
Accessibility Tasks

There are several ongoing tasks with the goal to improve accessibility in the Admin area.

  • Proximity
  • Add widgets screen
  • Menu screen

Widgets and menu screen

It’s not a secret that there are many issues in the Add Widgets and Menu screens. What to do? @juliemoynat has suggested some improvements in this ticket: https://core.trac.wordpress.org/ticket/40677

Proximity

In web design, the principle of proximity states that related items should be placed close together. By the same token, if things are spaced farther apart they appear to have less relation to one another.

This principle is so powerful, that it overrides similarity of color, shape, and other factors that might differentiate a group of objects.

Proximity is especially critical for users with low vision. It will even be addressed in the next draft of the WCAG guidelines! https://w3c.github.io/low-vision-a11y-tf/requirements.html

An initial ticket has been created, feel free to join in! https://core.trac.wordpress.org/ticket/40822

#weekly-meetings

Team Chat Summary August 10, 2015

New Structure Proposed

Rian Rietveld wrote a proposal on how to structure our work better and plan ahead longer and we discussed it. What follows is examples from the proposal.

Goals and Issues

This will be a separate page on make/accessibility and also a main menu item. It gives an overview of our goals for the accessibility of WordPress, the work we (want to) do, how this is organized, how we test, a roadmap for the next year and how we track the progress of issues we are working on. An example of the roadmap for release 4.4:

Release 4.4 (December 2015, Scott Taylor)
  • Finish still open issues focus from 4.3
  • Semantic heading structure Admin
  • The customizer
  • Handbook
  • Twenty Sixteen (?)

Central Ideas

Some central ideas also included in the proposal are keyboard focus, work on the handbook, color contrast, system to better follow tickets including splitting up tickets among team members on which to concentrate, and continue to develop code pattern library. Much more is included in the proposal and for now we will continue to work on the proposal to make it a more formal document to cover our activities over the next year.

We also talked about the fact that having a planning document to refer to does not obviate the need to address all new features since there is a tight turn around towards the end of a cycle because that’s when the features going into the release are announced. If we don’t follow all new features we might miss one or more that advance to release at the very end.

When we have it shaped up we will add the planning documentation to this blog in the form of pages and sub-pages to make it a community resource.

#accessibility-team-meetup, #team-reps, #weekly-meetings

Accessibility Team Meeting July 6, 2015

H1 in the admin

For 4.3 there will be an H1 in the admin. #31650: Missing H1 heading in the admin. Assistive technology users look for the H1 for way finding. Though there is the page title, when AT separates out elements such as links, lists, and headings, the info needs to be there too. Two weeks ago we ran this by Mika Epstein @Ipstenu and she helped us understand heading levels and plugins. Mika spot checked some plugins and it showed that they are using H2 and her opinion is that “we can post about that in make/plugins to try and spread the word.” Thanks Mika. More work will be done on the rest of the hierarchy.

Main Open Tickets

We also briefly discussed:

  • #31661: Quicktags: Can’t add them using just a keyboard in IE,
  • #26601: Inappropriate content in headings on admin screens,
  • #32152 List table: sortable column headers accessibility,
  • #26601: Inappropriate content in headings on admin screens, and
  • #31336: Customizer: separate navigation from options UI for better UX by removing accordion behavior.

#accessibility, #team-reps, #weekly-meetings

Accessibility Team Update: May 1, 2015

Weekly Meeting Change

This week during the Wednesday meeting we decided that the Monday testing meeting is now where the action is so we decided to stop having the Wednesday meeting. On Monday, May 4, we will all meet in the #accessibility channel in Slack at 18:00 UTC. We are also using Slack throughout the week to work on tickets and patches, ask questions, and discuss anything that comes up. First register for the WordPress forums and then follow the steps on the WordPress chat instruction page to get set up. Then find your way to #accessibility. See you there!

#team-reps, #weekly-meetings

I’ve only just realised that Admin Bar links…

I’ve only just realised that Admin Bar links contain tabindexes. That’s bad enough but they’re not really in an intuitive/logical order. Can they be removed in a future version?

WordPress 3.3 is coming up on RC1 meaning…

WordPress 3.3 is coming up on RC1 (meaning it’s close to launch). We tried to catch as many accessibility issues as we could, but chances are we missed things. If anyone would be willing to run 3.3 beta through the paces and report back on how it does/what fixes need to be made, that would be great. If you’re not set up with an svn install, you can download the beta tester plugin to put the beta on a test site.

#3-3

Changed a couple of settings Must fill in…

Changed a couple of settings:

  • Must fill in name and email, but removed the ‘must have previously approved’ setting so now comments go live immediately instead of waiting to be moderated.
  • Close comments on posts older than 14 days old. Comments go unnoticed, and no action gets taken. Hopefully discussions can get to agreement within 2 weeks (well before, if we’re lucky) and the resolution can make its way over to the appropriate trac ticket.

Do people think it is better for the…

Do people think it is better for the dashboard menus down the left side to work as described in A, B, or C:

  • A. Tabbing goes from top-level item to its subs and cycles through them, then proceeds to the next top-level item, etc., and hitting Enter/Return acts as clicking on the link to whatever item you’ve tabbed to; or
  • B. Tabbing goes from top-level item to top-level item, and hitting Enter/Return ‘opens’ the subs and then you can tab through them?
  • C. A more accessible suggestion that we haven’t thought of?

Please leave your vote/suggestion/comments in a reply to this post IF you work professionally in the accessibility field OR you need to access WordPress without a mouse/trackpad/rollerbar/other mouse-like input device (generally due to disability). If you don’t fit in one of these categories: while your opinion is valuable, it’s not the one we’re looking for at this particular time. So regular designers, developers, and users, please don’t distract from the pros and the target population on this thread. If you are an accessibility pro and have not introduced yourself on this blog before, or a keyboard access/screen reader user, please add a note about your qualifications/experience (for pros) or your typical setup/environment (for users — which screen reader, do you use keyboard shortcuts in addition to tabbing etc) so that we can put your suggestions in context. Thanks.

P.S. Please don’t derail the conversation by using this thread to suggest other features.

#dashboard-menu, #tabbing

http wordpress org support topic how to reorder…

https://wordpress.org/support/topic/how-to-reorder-items-in-custom-menu-without-dragging

#jaws-admin

Try to figure out why it was considered…

Try to figure out why it was considered necessary to add the title of an image as a title attribute to the image markup when inserting images into a post. Whose idea was that? The image’s title attribute serves no real purpose for sighted users but creates a whole load of completely unwanted noise for some screen reader users. Additionally, the title attribute is completely inaccessible to sighted non-mouse users.

So what’s the point of it?

#images