The latest draft guidelines are now up on the Theme Review page; <br><br><a href="http://codex.wordpress.org/Theme_Review#Accessibility">http://codex.wordpress.org/Theme_Review#Accessibility</a><br><br>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. <br>
<br>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. <br><br>Best,<br>
Joe<br><br>====<br><div>2. Otto or Pross merge the Accessibility checks into <span class="il">Theme</span>-Check</div><div></div><div>3. Otto whitelist the "accessibility-ready" tag in the tag filter in Extend</div>
<div></div><div>4. Otto edit <span class="il">Theme</span>-Trac to apply "keyword=accessibility-ready" to tickets for <span class="il">Themes</span> with the "accessibility-ready" tag</div><div></div>
<div>5. Any one of the <span class="il">Theme</span> Review admins create a new Accessibility Queue in <span class="il">Theme</span>-Trac. This is done, assuming the keyword is correct:</div>
<div><a href="http://themes.trac.wordpress.org/report/9" target="_blank">http://<span class="il">themes</span>.trac.wordpress.org/report/9</a><br></div><div><br></div><br><br><div class="gmail_quote">On Wed, Mar 6, 2013 at 3:19 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="im">> <span style="font-family:arial,sans-serif;font-size:13px">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.</span><div>
<span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></div><div><span style="font-family:arial,sans-serif;font-size:13px">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.</span></div>
<div class="im">
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">> </span><span style="font-family:arial,sans-serif;font-size:13px">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.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></div><div><span style="font-family:arial,sans-serif;font-size:13px">Some form of cross-training is exactly what I had in mind. ;)</span></div>
<span class="HOEnZb"><font color="#888888">
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Chip</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 6, 2013 at 4:15 PM, esmi at quirm dot net <span dir="ltr"><<a href="mailto:esmi@quirm.net" target="_blank">esmi@quirm.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">on 06/03/2013 20:47 Chip Bennett said the following:<div><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1. Someone from your team edit the Theme Review Codex entry, to add the<br>
draft Accessibility guidelines:<br>
<a href="http://codex.wordpress.org/Theme_Review#Accessibility" target="_blank">http://codex.wordpress.org/<u></u>Theme_Review#Accessibility</a><br>
</blockquote>
<br></div>
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.<br>
<br>
<snip><div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Then, we have some decisions to make regarding workflow.<br>
<br>
</blockquote></div>
[...]<div><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My preference would be to avoid the middle-man, and just have the<br>
Accessibility reviewers simply perform full Theme reviews. That way, the<br>
"accessibility-ready" tagged Themes could get shunted immediately into the<br>
Accessibility queue, reviewed once, and then resolved<br>
(approved/not-approved). But, that would really depend on workload.<br>
</blockquote>
<br></div>
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.<br>
<br>
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.<div>
<div><br>
<br>
Mel<br>
-- <br>
<a href="http://quirm.net" target="_blank">http://quirm.net</a><br>
<a href="http://blackwidows.co.uk" target="_blank">http://blackwidows.co.uk</a><br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>==================<br><br>Did I help you with one of my plug-ins? Donations keep support possible! <a href="http://www.joedolson.com/donate.php" target="_blank">http://www.joedolson.com/donate.php</a><br>
<br>==================<br><br>Joseph Dolson<br>Accessibility consultant and WordPress developer<br><a href="http://www.joedolson.com" target="_blank">http://www.joedolson.com</a><br><a href="http://profiles.wordpress.org/joedolson" target="_blank">http://profiles.wordpress.org/joedolson</a>