Accessibility work at WordCamp Nijmegen

@tacoverdo announced at the start of WordCamp Nijmegen that the Twitter hashtag #WCNMGN needed to be capitalised for screen reader users. And a lot of people did, thank you!

Work on the Contributors day

  • @choongsavvii worked with @jrf on the keyboard accessibility of the main menu in @obenland pointed out that this part is not open source and it’s can’t be fixed by changing the CSS only. To be continued.
  • @travel_girl worked on the new Handbook
  • @rianrietveld was table lead and gave an intro to a group of people about the basis of Accessibility
  • @maartenleenders and @jaapwiering worked on trac tickets labeled accessibility. Finding it hard to choose a ticket, as most tickets are discussed for a long time and it’s difficult to get into this fresh in such a short time as om the contributors day.

Ideas from the Hallway tracks

Automated a11y testing

This topic came up again and again. @jrf (Juliette Reinders Folmer) gave a talk “The Biggest WP Core Patch Ever” about trac ticket 41057, upgrading core to the coding standards. And after that talk I had many discussions about integrating accessibility in all the automated testing we do. For core, but also for themes in the repository and for plugin and theme development in WordPress.

After the Handbook is in good shape, I think we need to pick this up as focus for the Accessibility Team. This will probably be begin next year. @jrf and @spacedmonkey want to help and there are probably more people and companies we can ask to help.

Which tickets are easy to pick up

Before a WordCamp contributors day we need a better list of tickets and issues for developers to work on. That have a very specific clear solution and not a debate of years without conclusion.


Help @boemedia with her research on the usability of the Admin by filling out her survey.


Update on WordCamp accessibility planning

I had a great conversation with Andrea Middleton at WordCamp Minneapolis this weekend, and we’re making some plans to work on the core accessibility features that WordCamp organizers will need to pay attention to in building their sites.

Some of the key tasks will include working through the accessibility issues in the base themes available for WordCamp organizers to build from, providing some documentation to help organizers know what design standards they need to meet, and doing some basic training on checking their work.


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