Updates to WordPress theme accessibility guidelines

The accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)-ready guidelines for WordPress themes were updated today. There are no explicit changes to the requirements, but the order of the guidelines has been changed so that it corresponds more effectively to how it makes sense to run tests on the guidelines.

Additionally, I’ve added some information on how to run tests for each guideline into the guidelines, so that theme developers are more easily able to find information on how to self-test when they’re creating an accessibility-ready theme.

Review the guidelines.

#accessibility-ready, #themes-2

Theme Accessibility Meeting Notes

We had a great meeting to discuss the future of theme accessibility. You can review the complete transcript of the chat in Slack.

We discussed many of the aspects of what it will take to make accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) a requirement for themes – it’s a long process, but we agreed that this is possible. We started by discussing where the most appropriate place is to publish our kick off article, which is going to give three examples of areas where theme authors can improve the accessibility of their themes immediately. It will be published either on Make/Themes or here on Make/Accessibility, followed by an extensive effort to share in the community.

Next we discussed the fledgling repository for WordPress-specific code examples for accessibility. The repository already exists at GitHub, so it’s just a matter of writing code and organizing it. David Kennedy will take the lead on developing that resource.

Moving on, we discussed how to organize theme accessibility information and advice into the Theme handbook structure. We concluded that a conversation about how that fits in is needed, and I’ll have that with Tammie Lister before we decide exactly what those documents will be, as well as moving the existing Accessibility guidelines around in the theme reviewer’s handbook.

Morten Rand-Hendriksen reviewed the original plan sketched out at the community summit to give people who weren’t there a basic understanding of the conversation.

This brought up a conversation about future handling of the ‘accessibility-ready’ tag and how we should share information in the WordPress theme repository about whether a theme has been reviewed for accessibility. Right now, it’s fairly moot given the small number of themes that have been reviewed, but by the time accessibility becomes a requirement, it will be important to start labeling, to take the onus off end-users to discover whether their theme will allow them to meet their country’s legal requirements for accessibility.

Both these issues will need to be proposed to the theme review team, so we’ll be working on writing a precise proposal that can be taken to that team and be voted on. The important thing with the proposal is clarity.

Finally, we discussed theme reviewer training. I’ll set up a date with Tammie to work through the process with her, but will ultimately need to do something that’s less one-on-one, either through a detailed written document or a video training resource. This training process would be greatly helped by having the code repository fleshed out, so that those code examples are available to reviewers and theme developers.

#accessibility-ready

Draft guide for accessibility-ready reviewers

To go along with the accessibility-ready guidelines, I’ve been working on a document to help people who want to help perform accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) reviews on themes. This document is targeted at members of the accessibility team who want to help support the review process by checking themes for accessibility.

Please provide comments, so I can edit them into the most helpful guide they can be!

Theme Accessibility Guide for Reviewers

#accessibility-ready, #themes-2

Update on accessibility-ready theme tag

We’re gradually working the kinks out of the process. There was an oversight in the automated process that added the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)-ready keyword to themes, so that only new themes were automatically getting the keyword, and not updated themes that added it. That’s been fixed, which will improve our ability to note themes that need to go through the review process.

There’s a lot of support for the process, and the theme review team is invested in making this work, but I could use some backup in actually doing the reviews. Even if you don’t have the accessibility background, let me know if you’re interested: I’m happy to provide training to make sure you’ve got the knowledge it takes to do this review.

#accessibility-ready, #themes-2

Want to participate in reviewing WordPress themes for…

Want to participate in reviewing WordPress themes for the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)-ready tag? There’s a tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. keyword for that! Themes awaiting an accessibility-ready review.

#accessibility-ready, #themes-2

IRC Meeting: December 4, 2013

Discussion about Analysis of what gets into the alt and title attributes when adding an image into a page/post by @grahamarmfield. Excellent work.

Discussion about what is needed to move Create new tag: accessible-ready @sams suggested that we should find an owner and get it in as soon as 3.9 development opens. He also suggested that we look at the patch in #21442 to see what’s needed.

Though we have had some new recruits to the team in the last week, we are still woefully understaffed compared to the speed, breadth, and depth of WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development. We will continue to contribute where we can and are looking for more team members with deeper coding skills to help move some of the issues along.

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

I’ve been chatting with Chip Bennett via the…

I’ve been chatting with Chip Bennett via the Theme Review list about the Theme Audit guidelines. With his feedback (which was from the theme author and reviewer perspective, and very valuable) and the feedback from the comments on my previous post, I’ll be working on the next version with a variety of changes of various types. He’s going to be proposing some changes to the general guidelines that will obviate the need for a couple of the elements in the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) audit guidelines.

#accessibility-ready, #theme-audit