Taking Steps for More Accessible Themes

We’ve been working with the Theme Review team to coordinate sharing more information about making themes accessible, with an eye towards the goals in our Accessible Themes Roadmap. The first step in that roadmap has been published today, Three Easy tips for Accessible Theming, published at the Make/Themes blog.

Read it, share it, and most of all, build accessible themes for WordPress!


WordPress 3.6 alpha Testers

You might want to consider installing the MP6 plugin to get a sneak preview of the new user interface. Thus far, I’ve noted 3 areas of concern:

  1. The contrast on “Collapse Menu” needs to be pushed up a little to #888
  2. Post revision comparisons. Not sure I’m comfortable with red-on-red and green-on-green. At present, the contrasts are way too low at 2.7:1 (heck — even I’m having problems reading the texts).
  3. Ditto the text for inactive plugins on the Plugins page with only a contrast ratio of 2.8:1. And absolutely no way to “highlight” (increase the contrast) on the text without a mouse.

#3-6, #core-2, #ui

Accessibility for Theme Developers: First Draft Complete

I think I’ve finally finished! *gasp* Thank you to everyone who provided earlier feedback and jogged my memory.

Is there anything on the completed page I need to re-word or explain in more detail?

As previously, please post all feedback here rather than on the draft page itself.

#documention, #theme

Accessibility for Theme Developers

As part of the larger WordPress documentation project, I’ve put together a very rough first draft of an accessibility section for the theme developers’ handbook. It still needs a lot of fleshing out as I’m approaching this from the perspective of someone who doesn’t know anything about web accessibility. So I feel that we need to not only tell theme developers what to do but how and why.

That said, is the draft missing anything major — bearing in mind that we do not want to overwhelm theme developers?

#feedback, #theme

Don’t “Let It Snow ” How Autoplays Can…

Don’t “Let It Snow.” How Autoplays Can Disable Visitors to Your Website

#animation, #sound

Aaron Jorbin is suggesting that the new Twenty…

Aaron Jorbin is suggesting that the new Twenty Thirteen should be designed and built “accessibility first”. He outlines exactly what he means by this in What I want to see in the Twenty Thirteen theme. I think this is an initiative we should all support 100%.

#theme, #twentythirteen

Accessibility for Non-Technical Site Owners

As part of the new User handbook being created over at
Supporting Everything WordPress, I’ve put together an introduction to web accessibility.

This is intended to be far less technical and in-depth than its companion page in the Codex. The intent is to get site authors thinking about how they add content rather than just the final look of their pages.

On that basis, I’ve just focused on using headings, images and links as well as general readability.

http blog rrwd nl 2012 03 23 how…

How accessible is the WordPress CMS for a blind content manager

Some interesting issues brought up by a blind…

Some interesting issues brought up by a blind user on the wordpress,org support forums: https://wordpress.org/support/topic/plugin-dantotube-some-accessibility-fix-suggestions