[theme-reviewers] Accessibility Auditing of themes - next steps

[Joe Dolson]

The latest draft guidelines are now up on the Theme Review page;

http://codex.wordpress.org/Theme_Review#Accessibility

There shouldn't be any explicit contradictions between these guidelines and
other guidelines, although there are some edge cases where things that
would fail normal theme guidelines would be allowed by Accessibility
guidelines (specific example: HTML validation errors due to inclusion of
ARIA attributes); but I think that should easily fall into theme reviewer
prerogative to accept.

If any theme reviewers want to get trained into this, I'll be happy to do a
knowledge exchange - I'm not a practiced theme reviewer, but can definitely
share the accessibility knowledge I have.

Best,
Joe

====
2. Otto or Pross merge the Accessibility checks into Theme-Check
3. Otto whitelist the "accessibility-ready" tag in the tag filter in Extend
4. Otto edit Theme-Trac to apply "keyword=accessibility-ready" to tickets
for Themes with the "accessibility-ready" tag
5. Any one of the Theme Review admins create a new Accessibility Queue in
Theme-Trac. This is done, assuming the keyword is correct:
http://themes.trac.wordpress.org/report/9



On Wed, Mar 6, 2013 at 3:19 PM, Chip Bennett <chip at chipbennett.net> wrote:

> > Joe and/or I can look after this. We'll be working up the new content
> between us and then checking back with you for a final review.
>
> As far as I'm concerned: the Accessibility guidelines will be your group's
> baby. :) If there's anything conflicting with other Guidelines, we can deal
> with that. But otherwise, I'd rather your team, as the Accessibility
> experts, maintain that section. So, "final review" from our end won't
> consist of much.
>
> > Any chance of a compromise here? Could we "train up" a couple of
> interested and experienced theme reviewers to reduce the load? The last
> thing I want to do is slow down the review process because the a11y
> reviewers can't cope.
>
> Some form of cross-training is exactly what I had in mind. ;)
>
> Chip
>
>
>
> On Wed, Mar 6, 2013 at 4:15 PM, esmi at quirm dot net <esmi at quirm.net>wrote:
>
>> on 06/03/2013 20:47 Chip Bennett said the following:
>>
>>  1. Someone from your team edit the Theme Review Codex entry, to add the
>>> draft Accessibility guidelines:
>>> http://codex.wordpress.org/**Theme_Review#Accessibility<http://codex.wordpress.org/Theme_Review#Accessibility>
>>>
>>
>> Joe and/or I can look after this. We'll be working up the new content
>> between us and then checking back with you for a final review.
>>
>> <snip>
>>
>>
>>  Then, we have some decisions to make regarding workflow.
>>>
>>>  [...]
>>
>>  My preference would be to avoid the middle-man, and just have the
>>> Accessibility reviewers simply perform full Theme reviews. That way, the
>>> "accessibility-ready" tagged Themes could get shunted immediately into
>>> the
>>> Accessibility queue, reviewed once, and then resolved
>>> (approved/not-approved). But, that would really depend on workload.
>>>
>>
>> Oh - big workload alert! ;-) Right now, we're really light on bodies in
>> the a11y group and stretched terribly thin covering track, documentation
>> etc. Taking on a full theme review might be a bit too much long term unless
>> we can get more people involved.
>>
>> Any chance of a compromise here? Could we "train up" a couple of
>> interested and experienced theme reviewers to reduce the load? The last
>> thing I want to do is slow down the review process because the a11y
>> reviewers can't cope.
>>
>>
>> Mel
>> --
>> http://quirm.net
>> http://blackwidows.co.uk
>> ______________________________**_________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
>> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>>
>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>


-- 
==================

Did I help you with one of my plug-ins? Donations keep support possible!
http://www.joedolson.com/donate.php

==================

Joseph Dolson
Accessibility consultant and WordPress developer
http://www.joedolson.com
http://profiles.wordpress.org/joedolson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130314/9621dae9/attachment.htm>