I've already commented again on the respective tickets, but before the 72 hour response timeframe was proposed. I think that's fairly reasonable; give them 72 hours, or the theme will be suspended pending the fix.<div>
<br></div><div>Seriously, all they need to do for me to be happy is delete the tag from style.css, so this really should be easily accomplished within 72 hours.</div><div><br></div><div>Best,</div><div>Joe<br><br>On Monday, June 9, 2014, Srikanth Koneru <<a href="mailto:tskk79@gmail.com">tskk79@gmail.com</a>> 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>There would be no need to suspend those themes if they respond, suspending them will get them to respond or save effort for people who need those themes.<br>
</div>You are not being a bad guy by suspending them, you are helping people with disabilities.<br>
</div>Give them 72 hrs as Cais suggested and suspend them if there is no response.<br></div><div><br><br><div>On Tue, Jun 10, 2014 at 4:02 AM, Edward Caissie <span dir="ltr"><<a>edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">We suspend very few theme ... and I cannot think of a case where it wasn't easily justified.</div><div>
<span><font color="#888888"><br clear="all"><div>Edward Caissie<br>aka Cais.</div></font></span><div><div>
<br><br><div>On Mon, Jun 9, 2014 at 6:05 PM, Emil Uzelac <span dir="ltr"><<a>emil@uzelac.me</a>></span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Joe will take care of this and we will solve the issue without ugly suspensions :)<div><div><span></span><br><br>On Monday, June 9, 2014, Edward Caissie <<a>edward.caissie@gmail.com</a>> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I would say we can suspend a theme for using that particular tag incorrectly ... saying something is a fluid-layout when it is not versus saying something is a11y ready when it is not are two completely different ideas.<div>
<br></div><div>These authors have been advised once already, correct? I would send a second notification this issue needs to be addressed (another comment with a fair ... 72 hours? ... time limit to correct and/or respond to at least acknowledge they are aware of the issue and intend to correct it); otherwise, suspend the theme and be done with it. Any of the WPTRT admins have access to suspend themes if warranted, we just would prefer not to in most cases.</div>
<div><br></div><div>The available choices for a11y compliant themes is very limited, there is no reason whatsoever to dilute that pool with themes that do not follow the current guidelines.</div></div><div>
<br clear="all"><div>Edward Caissie<br>aka Cais.</div>
<br><br><div>On Mon, Jun 9, 2014 at 2:58 PM, Joe Dolson <span dir="ltr"><<a>design@joedolson.com</a>></span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Removing the wrong tag is absolutely the end goal; it's just that only the theme author can actually do that, so we're dependent on the theme author updating their theme to make that change. <br></div>
<div><div>
<div><br><br><div>On Mon, Jun 9, 2014 at 1:55 PM, Emil Uzelac <span dir="ltr"><<a>emil@uzelac.me</a>></span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div style="font-family:verdana,sans-serif">That was the plan :)</div></div><div><div><div><br><br><div>On Mon, Jun 9, 2014 at 1:54 PM, Bass Jobsen <span dir="ltr"><<a>bass@w3masters.nl</a>></span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div style="font-family:verdana,sans-serif">
But we can't suspend Themes based on wrong tag :)<br></div></div></blockquote><div><br></div></div><div>Maybe remove the wrong tag?</div><div><div><div><br></div><div> </div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div style="font-family:verdana,sans-serif"></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">
Emil</div><div style="font-family:verdana,sans-serif"><br></div></div><div><br><br><div><div><div>On Mon, Jun 9, 2014 at 10:43 AM, Joe Dolson <span dir="ltr"><<a>design@joedolson.com</a>></span> wrote:<br>
</div></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><div><div><div><div>On the Accessibility P2 group, we're starting to get occasional complaints about themes that have the 'accessibility-ready' tag but aren't really accessible. This is directly caused by the fact that at various points themes have had the tag added without being reviewed. <br>
<br>Is it possible to suspend themes that use the accessibility-ready tag without a review and approval? <br><br>If so, I'd like to have the following themes suspending pending updates to either fix their accessibility or remove the accessibility-ready tag:<br>
<br></div>Ward: <a href="http://wordpress.org/themes/ward" target="_blank">http://wordpress.org/themes/ward</a><br></div>NuvioElement Orange: <a href="http://wordpress.org/themes/nuvioelement-orange" target="_blank"></a></div>
</div></div></div></div></div></div></blockquote></div></div></blockquote></div></div></div></div></div></blockquote></div></div></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div>
</div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div><br><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><br>