Accessibility Team Update: March 26, 2014

Meeting Time Change

We will be going back to a meeting time of 19:00 UTC next Wednesday, April 2.

Progress

The meeting this past Wednesday was interesting. Now we’re getting to the heart of the matter.

So far, we have compiled a keyboard-only report on most of 3.8 and have some data to rely on.

The first pattern we identified from the testing is poor visual focus in the Admin. @RianReitveld created a ticket dealing with keyboard focus. Better visual indication of focus on elements in the Admin (#27173). This ticket is now closed (fixed.) Thanks Rian!

Testing 3.9

We have to quickly change gears because 3.9 is due out in 19 days and we have to test and issue some tickets if we want to catch any errors. A list of items to concentrate on will help guide us.

Contact @AccessibleJoe for details if you want to help test 3.9.

WordCamp Websites and Accessibility

Howdy, accessibility team! Currently, WordCamp websites are not reliably accessible across the board, which is sad-making. We want to change this; can you help?

First, we’d like to make sure that the themes we make available for WordCamp organizing teams to customize with CSS are all accessible. The themes available for WordCamps to customize are:

Twenty Ten
Twenty Eleven
Twenty Twelve
Twenty Thirteen
Twenty Fourteen
WordCamp Base
WordCamp Base Redux

Can you tell us which of the above themes have accessibility issues, so we can make (or submit patches for) those fixes?

Second, we’d like to create a guide of baselines for CSS accessibility (contrast, etc) so organizers can know what expectations we have for official sites.

If you’re available and interested in helping WordCamp websites become more accessible, we’re incredibly grateful for your help.

#accessibility, #wordcamp

Digital Accessibility Centre Visit – Part 3: The Blind Perspective

This is the third post documenting a recent visit to Digital Accessibility Centre in Neath, South Wales organised by fellow team member Siobhan BamberThe first post can be found here, and the second post here.

Three of the staff from DAC gave us feedback on using the WordPress admin screens. Each of the three have a particular impairment, and the visit was a valuable opportunity to learn about ways we could improve WordPress for everyone.

In this post we take feedback from Carly who is totally blind. She showed us how she used a screen reader and gave us some great feedback on using the WordPress admin screens with a screen reader.

Continue reading

#accessibility, #assistive-technology, #feedback, #jaws-admin, #screen-reader, #testing, #trac-2

Digital Accessibility Centre Visit – Part 2: Poor Vision

This is the second post (of three) documenting a recent visit to Digital Accessibility Centre in Neath, South Wales organised by fellow team member Siobhan Bamber. The first post can be found here.

Three of the staff from DAC gave us feedback on using the WordPress admin screens. Each of the three have a particular impairment, and the visit was a valuable opportunity to learn about ways we could improve WordPress for everyone.

In this post we take feedback from Gary who has poor vision.

Continue reading

#accessibility, #colour-contrast, #feedback, #testing, #text-resize

Digital Accessibility Centre Visit – Part 1: Introduction, Keyboard and Dragon Testing

On February 25th 2014 I was honoured to visit the offices of the Digital Accessibility Centre in Neath, South Wales, UK. The trip was organised by fellow wpa11y team member Siobhan Bamber.

This post is the first in a series of three which summarise the feedback we received on using WordPress from three users with impairments. Our first session was with Becs who uses Dragon NaturallySpeaking (voice recognition software) and does keyboard accessibility testing.

 

Continue reading

#accessibility, #assistive-technology, #feedback, #keyboard, #voice-recognition

Hey guys I have posted my WordPress 3.8…

Hey guys…
I have posted my WordPress 3.8 Keyboard Screen testing results for the Users, Tools, and Settings sections.