<p dir="ltr">Absolutely. I'll get on it. </p>
<div class="gmail_quote">On Apr 12, 2014 1:22 PM, "Chip Bennett" <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I would much favor remediation - either tag removal or verification of accessibility requirements - rather than suspension.<div><br></div><div>Joe, can you guys perform accessibility reviews for the already-live Themes, and post the review comments in the most recent ticket for each? That will let us know what - if any - remediation is required.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Apr 12, 2014 at 2:17 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</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">Any theme that has the a10y (too many typos) tag and is not actually complying to the guidelines can easily be suspended until they either meet the guidelines or remove the tag ... but I am not certain such a harsh approach would be best.</div>
<span><font color="#888888">
</font></span><div class="gmail_extra"><span><font color="#888888"><br clear="all"><div>Edward Caissie<br>aka Cais.</div></font></span><div><div>
<br><br><div class="gmail_quote">On Sat, Apr 12, 2014 at 2:15 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">
<p dir="ltr">I think it might be time to follow up. If there weren't so many missed themes, I wouldn't be concerned, but with no real recourse to mediate the themes that aren't reviewed, we need something more automated to pick up on this. </p>
<div><div>
<div class="gmail_quote">On Apr 12, 2014 1:00 PM, "Chip Bennett" <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Otto is a busy guy; I tend not to bug him too frequently about those sorts of things. :) So, yeah; I never followed up on it.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Apr 12, 2014 at 1:52 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"><div dir="ltr"><div><div>But there are several themes that were approved without ever getting the keyword, so it's not happening every time. <br>
<br></div>This was something that Otto had said he was creating. Conversation was Feb. 10th. Chip requested:<br>
<br>"Would it be possible to have Theme-Trac add a ticket keyword - "<span>accessibility</span>-<span>ready</span>" - to tickets for Themes that have the "<span>accessibility</span>-<span>ready</span>" keyword? That would save us the step of having to rely on the reviewer to add the ticket keyword manually.<br>
<br>Note: the <span>accessibility</span> reviewers will be using a report that currently relies on the "<span>accessibility</span>-<span>ready</span>" ticket keyword:<br><a href="https://themes.trac.wordpress.org/report/9" target="_blank">https://themes.trac.wordpress.org/report/9</a>"<br>
<br></div><div>Otto responded that he'd do it tomorrow, at the time, but I don't know where it went from there.<br></div><div><br></div>Best,<br>Joe<br></div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">
On Sat, Apr 12, 2014 at 11:46 AM, Srikanth Koneru <span dir="ltr"><<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</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>no i see the autogenerated keywords all the time and that's why i cc Joe.<br></div>but they are added after assigning the ticket to myself.<br></div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">
On Sat, Apr 12, 2014 at 10:14 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">I've thus far gotten no feedback on auto-generating trac keywords based on keyword tags.<div><br></div><div>It's still a manual process. Reviewers need to be aware of the presence of the "accessibility-ready" tag. If you're unsure how to handle it, please ask.</div>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Apr 12, 2014 at 12:30 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"><div dir="ltr"><div>The process for handling this still isn't working quite right, I think - there are 4 themes with the accessibility-ready tag that haven't gone through the review process, to the best of my knowledge. <br>
<br><a href="http://wordpress.org/themes/ward" target="_blank">http://wordpress.org/themes/ward</a><br><a href="http://wordpress.org/themes/infinite" target="_blank">http://wordpress.org/themes/infinite</a><br><a href="http://wordpress.org/themes/nuvioelement-orange" target="_blank">http://wordpress.org/themes/nuvioelement-orange</a><br>
<a href="http://wordpress.org/themes/nuviofuturemag-red" target="_blank">http://wordpress.org/themes/nuviofuturemag-red</a><br><br></div>What can we do about themes that were missed in this process? I thought there was supposed to be some automated keywords added for accessibility-ready themes, but that doesn't seem to be happening, or at least not consistently.<br>
<br>Best,<br>Joe<br><div><br></div></div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">On Sat, Apr 12, 2014 at 11:22 AM, 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">Once Themes are live, they are... live. At that point, if they claim "accessibility-ready" and aren't, then we're falsely advertising to end users. So, yes: Themes that claim "accessibility-ready' have to pass accessibility review before being made live.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Sat, Apr 12, 2014 at 12:08 PM, Srikanth Koneru <span dir="ltr"><<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<div dir="ltr">Do themes have to pass accessibility-ready test during the initial review or do they get checked for that after they go live?<br></div>
<br></div><div>_______________________________________________<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>
<br></div></blockquote></div><br></div>
<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>
<br></blockquote></div><br><br clear="all"><br></div></div><div>-- <br><div dir="ltr">==================<br>Joseph Dolson<br>Accessibility consultant & 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></div>
</div></div>
<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>
<br></blockquote></div><br></div>
</div></div><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>
<br></blockquote></div><br></div>
</div></div><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>
<br></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">==================<br>Joseph Dolson<br>Accessibility consultant & 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></div>
</div>
</div></div><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>
<br></blockquote></div><br></div>
<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>
<br></blockquote></div>
</div></div><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>
<br></blockquote></div><br></div></div></div>
<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>
<br></blockquote></div><br></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>