I agree with the others, a sample theme (even a Child-Theme) would be quite helpful in reviewing how the process/code may be reviewed.<br><br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Wed, Oct 24, 2012 at 2:20 AM, Vicky Arulsingam <span dir="ltr"><<a href="mailto:vicky.arulsingam@gmail.com" target="_blank">vicky.arulsingam@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Great job Joe!<div><br></div><div>I don't have any objections to the outlined process flow but a real life example of all the things we need to be on the look out for would be great.</div><div><br></div><div>Regarding the color contrast, is it okay to use this tool: <a href="http://snook.ca/technical/colour_contrast/colour.html" target="_blank">http://snook.ca/technical/colour_contrast/colour.html</a></div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div><br></div></font></span><div><span class="HOEnZb"><font color="#888888">Vicky</font></span><div><div class="h5"><br><br><div class="gmail_quote">On Wed, Oct 24, 2012 at 5:12 AM, 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">So, my last message on this fell silently to the earth...so, here goes again.<br>
<br>
Mel and I have worked on a basic theme audit document with the<br>
requirements for being approved<br>
for an accessibility related tag. That document can be seen here, in draft form.<br>
<br>
<a href="http://make.wordpress.org/accessibility/theme-accessibility-audit-draft-proposal/" target="_blank">http://make.wordpress.org/accessibility/theme-accessibility-audit-draft-proposal/</a><br>
<br>
Obviously, some questions require resolution from this group to be<br>
able to finalize the document.<br>
<br>
The specific next steps seem to be:<br>
<br>
1) Reach consensus that these audit guidelines are acceptable and achievable.<br>
2) Determine the text of the tag -- I'd suggest 'accessibility-ready'<br>
is a good one; but I'm open-minded.<br>
3) Update Tag Filter<br>
<br>
Best,<br>
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>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
</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>