<div dir="ltr">sufficient reason to go not-approved even for themes that don't have that tag?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 21, 2014 at 2:56 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"><div dir="ltr"><div><div>I think it would be awesome if being accessibility-ready were to become sufficient reason to go not-approved -- however, given the availability of reviewers with the right skill set, I'm not sure that's practical right now. <br>
<br></div>I think that phasing the accessibility ready conditions in with an ultimate goal of making them required might be reasonable. In that case, the goal throughout would be to help reviewers develop the skill set to make those judgements.<br>
<br>It's absolutely true that many aspects of accessibility are subjective -- we've made the intentional goal of making the theme review requirements as explicit as possible, so that most things are not as open to subjective judgement as they could be.<br>
<br></div><div>Theme check, unfortunately, is pretty impractical for this. I did write a set of theme check class extensions about a year ago (<a href="http://make.wordpress.org/accessibility/2013/02/13/progress-report-theme-review-guidelines-for-accessibility/" target="_blank">http://make.wordpress.org/accessibility/2013/02/13/progress-report-theme-review-guidelines-for-accessibility/</a>) but they were never picked up.<br>
<br></div><div>The problem there is that Theme Check checks the source code, not the output -- in order to implement an effective theme check for accessibility, we need to be processing the DOM, because that's the body of code that actually interfaces with accessibility APIs. <br>
<br></div><div>I've thought about writing something for that -- but haven't had the time for it.<br><br></div><div>Although in general terms it's impossible to fully automate an accessibility check, it may actually be possible (or at least more complete) when you're working with a predefined data set for the content of the site. I'll have to think about that. <br>
</div><div><br></div><div>Best,<br>Joe<br></div></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Mon, Jan 20, 2014 at 3:13 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Mon, Jan 20, 2014 at 2:38 PM, Joe Dolson <<a href="mailto:design@joedolson.com" target="_blank">design@joedolson.com</a>> wrote:<br>
</div><div>> Any admin have a reason to think that should stay as is? The work flow<br>
> doesn't exist, so I don't think it's practical. The review needs to be done<br>
> at a point where the theme author can resubmit with accessibility fixes or<br>
> without the accessibility-ready tag, I think.<br>
<br>
<br>
</div>Let's try it from another angle:<br>
<br>
- Should a theme having the accessibility-ready tag, but having some<br>
accessibility problems, be sufficient reason for not-approved, at this<br>
moment in time?<br>
<br>
In short, do we actually have enough reviewers capable of performing<br>
an accessibility review to make this a mandatory requirement? Do we<br>
have a document to teach people how to perform such a review? Do we<br>
have written standards? Better yet, can those standards be turned into<br>
objective tests that we can add to Theme-Check?<br>
<br>
The field of accessibility seems a bit subjective to me. I have read<br>
the documents and all the stuff at the make blog on the topic, and I<br>
still feel that I would not be qualified to determine what is<br>
"accessible" or not.<br>
<br>
We need some form of standards and people willing to review to those<br>
standards in order to make this sort of thing a "required" step.<br>
Otherwise we end up with people stuck in the queue forever because<br>
nobody's around to do the review for them.<br>
<span><font color="#888888"><br>
-Otto<br>
</font></span><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>
</div></div></blockquote></div><br><br clear="all"><br></div></div><div class="im">-- <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">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>