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

Title Attributes Galore

The patches for Trac ticket 24766 are slated for addition to WordPress 3.7. This is great news for assistive technology users who have been forced to wade through a sea of unnecessary title attribute verbiage. But we need to ensue that the patches cover all unnecessary title attributes and that those deliberately excluded from the patches do not present any accessibility issues.

Currently, the excluded methods, functions and scripts are:

  • the_author_posts_link()
  • rss.php
  • wp_fullscreen_html()
  • get_adjacent_post_rel_link()
  • _walk_bookmarks()
  • get_image_tag()
  • the_shortlink()

Continue reading

#tabbing, #trac-2, #ui

IRC Meeting: August 7, 2013

A very busy & productive meeting. We’ve identified two high priority areas that we’d like to focus on in the next couple of months.

Continue reading

#media-manager, #meetup, #trac-2, #ui

Accessible Polls and Surveys

We are always looking at ways to increase feedback from disabled users of WordPress. The more we know about the issues that people face every day, the more we can advocate for positive changes.

We also appreciate that it can be very daunting to post a comment on a blog like this one. So we would like to look at using short surveys and simple polls as a way of allowing people to give us their feedback as simply and as easily as possible. That, however, raises a whole new set of potential problems. We need to ensure that whatever tools we do use are as accessible as possible.

This where you come in.

Please tell us about any accessible survey and poll applications that you know of.

#feedback

IRC Meeting: July 17, 2013

Long time no meetup update! Our regular IRC meetings have still been taking place every Wednesday at 19:00 UTC But we’ve been so busy that it’s been hard to stop and provide updates.

Last night’s meeting focused on how to gain a better insight into the real problems that some WordPress users face every day. We also discussed ways to increase the flow of information from those users so that we can advocate high priority changes on their behalf. We’ll be posting about some of our ideas and asking for your help shortly.

#wordpress-ui log for July 17, 2013

#meetup

Next IRC Meetup

Just a quick reminder that the next IRC meetup will be on Wednesday, 26 June at 19:00 UTC in #wordpress-iu.

Everyone welcome!

If you have never attended an WordPress IRC meetup before, you can find all of the details you will need to join in the Codex’s IRC page.

One topic for discussion is likely to be the development of a proposed accessibility statement for WordPress. To whet your appetite and give you an idea of what we could aim for longer term, have a look at Drupal’s accessibility statement.

#core-2, #development, #meetup

Should We Be Dropping the Role Attribute in Twenty Thirteen Yet?

Your feedback is requested on Trac Ticket 24629.

Cited example: Should the Twenty Thirteen drop the use of the role attribute on the HTML5 nav element on the grounds that the element, by definition, has the role of navigation? Or should role="navigation" be retained in order to support technologies that are not yet HTML5 aware?

My own opinion that the role attribute should be retained for the time being in order to support the widest range of technologies. Dropping it would offer only a marginal benefit in reducing page bloat. Please do weigh in with your opinions on the ticket.

#a11y-audit, #html5, #trac-2

IRC Meeting: May 22, 2013

Another small but busy IRC meeting on #wordpress-ui where discussion focused on assessing the translate.wordpress.org site for possible accessibility issues.

If you have a little spare time, please do try to contribute to the site feedback request. Any observation — no matter how small — is valuable. If you need some ideas on what to look for, please check out our Site Feedback Guide.

#wordpress-ui log for May 22, 2013.

#meetup, #testing

Site Feedback Request

We have been approached by the folks over at translate.wordpress.org. They are keen to ensure that it is accessible as possible and would like our help to identify any problems with the current site.

So please take a little time, between May 17 & May 31, to have a look at translate.wordpress.org and give us your feedback via comments on this post. In order to support you and provide some structure to the feedback, we’ve prepared a Site Feedback Guide that should help.

We look forward to your contributions.

#feedback, #screen-reader, #testing

IRC Meetings

Just a quick post to remind everyone that we are still holding a weekly IRC meeting in #wordpress-ui every Wednesday at 19:00 UTC.

The meeting on May 1 covered the variations in form handling across different screen readers as well as a recent issue reported with the Jetpack plugin. As a result of the latter discussion, we now have a representative on the Jetpack Beta Group and Trac ticket #1710 has been created.

#wordpress-ui log for May 1, 2013.

On the May 8 meeting, discussion centred on the draft Site Feedback Guide. The guide is intended to both add structure to any site feedback as well as provide some support for non-technical disabled users who would like to join in. We hope to test the guide out later this month.

#wordpress-ui log for May 8, 2013.

#meetup, #plugin