It's a little longish (*grin*), but I cannot think of anything that would convey the same ideals.<div class="gmail_extra"><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Wed, Nov 7, 2012 at 6:40 PM, Joe Dolson <span dir="ltr"><<a href="mailto:design@joedolson.com" target="_blank">design@joedolson.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, all -<br>
<br>
We've had some helpful feedback on the theme audit criteria for using<br>
an accessibility-ready tag; it's time to work on moving to the next<br>
stage.<br>
<br>
I'm proposing that the tag value should be 'accessibility-ready', as<br>
that, in my mind, best conveys the honest truth about a theme: that it<br>
can do everything in its power to be accessible, but cannot guarantee<br>
an accessible web site.<br>
<br>
Can we reach an agreement on this, so we can move forward on the next steps?<br>
<br>
Thanks!<br>
<div class="im HOEnZb">Joe<br>
<br>
=======<br>
Review: Chip's steps to implementation:<br>
1) Clearly defined requirements, ideally listed somewhere in the Codex<br>
2) Updated Tag Filter<br>
3) Identify accessibility guidelines that can be evaluated<br>
programmatically via Theme-Check where possible<br>
4) Identify accessibility guidelines that can be incorporated into the<br>
Theme Unit Test Data where possible<br>
5) Identify accessibility guidelines that can only be verified by a live person<br>
6) Set up Theme-Trac workflow to shunt Themes using the Accessibility<br>
tags into a separate queue<br>
7) Volunteers to review Themes in the Accessibility queue in Theme-Trac<br>
<br>
</div><div class="HOEnZb"><div class="h5">On Wed, Oct 24, 2012 at 8:59 AM, esmi at quirm dot net <<a href="mailto:esmi@quirm.net">esmi@quirm.net</a>> wrote:<br>
> on 24/10/2012 00:54 Kirk Wight said the following:<br>
><br>
>> Can you post an example/download of a theme that would meet all of these<br>
>> requirements, if you know of one? I have a hard time imagining how various<br>
>> sections would be implemented (Link Text, Keyboard Navigation and Skip<br>
>> Links are my first questions marks). Seeing actual code would really help<br>
>> imagining the work that would be involved in reviewing a theme of this<br>
>> nature.<br>
><br>
><br>
> Have a look at <<a href="http://blackwidows.co.uk/clients/wp/" target="_blank">http://blackwidows.co.uk/clients/wp/</a>><br>
><br>
> That's the ZenLite theme using the standard theme unit test data.<br>
><br>
> Or <<a href="http://edemo.quirm.net/" target="_blank">http://edemo.quirm.net/</a>> which is actually a demo/testing install for<br>
> the eShop plugin.<br>
><br>
> If you want to pull a theme apart locally,<br>
> <<a href="http://quirm.net/themes/billposter/" target="_blank">http://quirm.net/themes/billposter/</a>> is an interesting one as the unique<br>
> part of the read more link is moved offscreen in graphical browsers to<br>
> reduce screen clutter.<br>
><br>
> Then of course there's <<a href="http://quirm.net/" target="_blank">http://quirm.net/</a>>. I'm not absolutely guaranteeing<br>
> that all of my themes meet all of the guidelines but I am saying they darn<br>
> well should do. So if you notice a problem, do let me know. :-)<br>
><br>
> What I think we do need to get across is that accessible themes don't have<br>
> to be boring. They can still be graphically rich and aesthetically pleasing.<br>
><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>
> _______________________________________________<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>
<br>
<br>
</div></div><div class="im HOEnZb">--<br>
==================<br>
<br>
Did I help you with one of my plug-ins? Donations keep support<br>
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><br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div>