IRC Meeting: September 25, 2013

Most of the time was spent discussing https://core.trac.wordpress.org/ticket/21334 3.7, grahamarmfield->helen, closed, Row actions are not always keyboard accessible. Helen Hou joined us for the discussion.

1. When mouse hovers over a page/post row in main Pages/Posts screen ‘quick links’ appear. Suggesting that they also are made available for keyboard-only users and screen reader users.

2. When using the QuickEdit panel the time/date controls have separate tabindex and no labels. Suggesting that the tabindex be removed from those controls, and that labels be used.

Discussion centered around the need to reduce verbosity for screen reader users, while still making the controls available to them.

It was decided to test the latest build and come back with a recommendation.

#accessibility, #meeting-notes, #team-reps

Feedback on #21334: Row actions are not always keyboard accessible

I’ve made two commits so far to address the fact that row actions (that is, edit/quick edit/trash under each post’s title) only show on hover. I have two questions regarding this that I could your expertise on:

1. In terms of CSS, this is controlled by the visibility property. My understanding has been that visibility: hidden does not get read by screen readers. If this is the case, then we may want to use an alternative method for show/hide. Are these row actions currently in a state where they are useful to screen readers or are they better off not being read (for now)?
2. Right now the keyboard tabbing will only trigger them to show when in the same cell. Should this expand to whenever focus is within the row? I believe visually it is when hovering on the table row.

Thanks!

#core-2, #feedback

IRC Meeting: September 18, 2013

Accessibility Statement Final Draft

“Accessibility is the degree to which a product, device, service, or environment is available to as many people as possible.” Cynthia Waddell

WordPress is founded on the principles of an inclusive community and democratization of publishing. The development of WordPress, based on standards and best practices, offers a constantly improving environment with flexibility and choice. We promise to always work toward creating an environment accessible to as many people as possible, inclusive of technology and ability.

We want community involvement and welcome feedback. Your comments help us enhance the accessibility of WordPress.

Resources

End Accessibility Statement

Projects To Be Followed

During the remainder of the meeting we discussed the projects we believe should be followed by the WordPress Accessibility Team. We agreed that we have too few people on the team to follow all these projects, but we compiled the following list.

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

IRC Meeting: September 11, 2013

We edited an accessibility statement.

At the head of the statement is a quote by Cynthia Waddell: “Accessibility is the degree to which a product, device, service, or environment is available to as many people as possible.”

[Then comes the statement:]

WordPress is founded on the principles of an inclusive community and democratization of publishing. The development of WordPress, based on standards and best practices, offers a constantly improving environment with flexibility and choice. We promise to always work toward creating an environment accessible to as many people as possible, inclusive of technology and ability.

[The statement is followed by resources and contact information.]

Resources are available if you would like to learn more about WordPress accessibility.

We want community involvement and welcome feedback. Your comments help us enhance the accessibility of WordPress.

[Contact us here, and here, etc.]

#accessibility, #meetup, #team-reps

IRC Meeting: September 4, 2013

Yesterday’s meeting focused almost entirely on developing a global accessibility statement for WordPress. It was decided that the statement should be broad in nature, and that it will generally support accessibility with links to more specific information that this group maintains.

The voluntary accessibility theme check process was mentioned, that process is nearly ready to launch.

Much thanks to Mel Pedley @esmi for her guidance and leadership as team representative for the past 18 months. I will now serve as team representative.

You can also contact us with words of encouragement or feedback on Twitter @WPAccessibility.

#meetup, #team-reps

IRC Meeting: August 28, 2013

The main focus of the meeting ( and the group) was still on one of our primary objectives — the development of a global accessibility statement for WordPress. After reviewing Drupal’s accessibility statement again, it was decided to begin work on drafting our own statement that can then be presented to the wider community for discussion.

Continue reading

#meetup, #team-reps