<p>What you're suggesting isn't possible. The tags that are displayed in extend are the tags the the author sets in his/her themes stylesheet, they can only be changed when the author updates the theme.</p>
<p>Jay </p>
<div class="gmail_quote">On Sep 27, 2012 9:21 PM, "Joe Dolson" <<a href="mailto:design@joedolson.com">design@joedolson.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm actually not recommending any approve/unapprove consideration due<br>
to accessibility; I'm actually recommending a completely separate<br>
process from theme review, which would provide access to modify tags<br>
within the theme repository according to accessibility issues.<br>
<br>
Since there is no existing theme review group with an access along<br>
those lines, I'm proposing this within the theme review group due to<br>
necessity - the make.accessibility group would be appropriate, but<br>
does not have any ability to effect anything within the theme<br>
directory.<br>
<br>
Thanks for responding!<br>
<br>
Best,<br>
Joe<br>
<br>
On Thu, Sep 27, 2012 at 3:14 PM, Edward Caissie<br>
<<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>> wrote:<br>
> Although the idea of addressing "accessibility" has its merits, the Theme<br>
> Review Team has no access to add, delete, or modify tags a theme author<br>
> chooses to use. The WPTRT reviewers should expect to validate the tags<br>
> applied are correct, but on their own it would be a tough call to<br>
> not-approve on a theme tag error by itself.<br>
><br>
><br>
> Cais.<br>
><br>
><br>
><br>
> On Thu, Sep 27, 2012 at 4:01 PM, Joe Dolson <<a href="mailto:design@joedolson.com">design@joedolson.com</a>> wrote:<br>
>><br>
>> So, this is my first post to the theme-reviewers list, so I hope I'm<br>
>> proposing this in the best possible place.<br>
>><br>
>> I've been in a number of discussions with people in the Accessibility<br>
>> and the WordPress communities about the need to improve accessibility<br>
>> in WordPress themes -- or, more specifically, improve the ability to<br>
>> locate accessible WordPress themes which have had vetting beyond an<br>
>> authorial claim of accessibility.<br>
>><br>
>> I know that the theme review team hardly has the time to review what<br>
>> they already do, let alone add an accessibility review -- and as much<br>
>> as I'd like it, I don't think that we're ready to impose accessibility<br>
>> as a requirement in order to publish a theme -- it wouldn't be<br>
>> practical or realistic.<br>
>><br>
>> I'd like to propose a way to improve the ability to find quality<br>
>> themes by establishing a team, working to a standard set of<br>
>> guidelines, which could review themes in the theme repository after<br>
>> they have been approved. This team would have the mission of assigning<br>
>> or removing accessibility related tags from themes.<br>
>><br>
>> This review team, tasked with identifying and labeling accessible<br>
>> themes, would create an imposition that the 'accessible' tag and<br>
>> related tags would be controlled. Authors could self label as<br>
>> accessible, but if it didn't meet review, the tag could be removed.<br>
>><br>
>> At least at this early stage, it could be a pretty straightforward triage:<br>
>><br>
>> 1) If theme tagged with accessible, a11y, wcag, etc. it gets a review to<br>
>> verify<br>
>> 2) Popular themes should be reviewed.<br>
>> 3) Other themes could be reviewed as time allowed or by request.<br>
>><br>
>> I would be happy to head up the process of establishing guidelines for<br>
>> reviewing themes and participate in the review and tagging of themes<br>
>> -- or to provide expert assistance to anybody else who wanted to take<br>
>> this on.<br>
>><br>
>> Obviously, this is largely my own concept, and can and should be<br>
>> modified to best fit the WordPress theme review workflow; which I'll<br>
>> admit to being more than a little ignorant about.<br>
>><br>
>> I don't want to create a substantial burden on either theme developers<br>
>> or reviewers, but any incremental progress in improving the ability to<br>
>> identify accessible WordPress themes in a consistent manner would be<br>
>> wonderful.<br>
>><br>
>> Best,<br>
>> Joe Dolson<br>
>> (Accessibility consultant and WordPress plug-in developer)<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>
> _______________________________________________<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>
<br>
--<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>
_______________________________________________<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>
</blockquote></div>