[theme-reviewers] accessibility-ready and suspensions

[Edward Caissie]

We suspend very few theme ... and I cannot think of a case where it wasn't
easily justified.

Edward Caissie
aka Cais.


On Mon, Jun 9, 2014 at 6:05 PM, Emil Uzelac <emil at uzelac.me> wrote:

> Joe will take care of this and we will solve the issue without ugly
> suspensions :)
>
>
> On Monday, June 9, 2014, Edward Caissie <edward.caissie at gmail.com> wrote:
>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> Edward Caissie
>> aka Cais.
>>
>>
>> On Mon, Jun 9, 2014 at 2:58 PM, Joe Dolson <design at joedolson.com> wrote:
>>
>> 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.
>>
>>
>> On Mon, Jun 9, 2014 at 1:55 PM, Emil Uzelac <emil at uzelac.me> wrote:
>>
>> That was the plan :)
>>
>>
>> On Mon, Jun 9, 2014 at 1:54 PM, Bass Jobsen <bass at w3masters.nl> wrote:
>>
>>  But we can't suspend Themes based on wrong tag :)
>>
>>
>> Maybe remove the wrong tag?
>>
>>
>>
>>
>> Emil
>>
>>
>>
>> On Mon, Jun 9, 2014 at 10:43 AM, Joe Dolson <design at joedolson.com> wrote:
>>
>> 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.
>>
>> Is it possible to suspend themes that use the accessibility-ready tag
>> without a review and approval?
>>
>> If so, I'd like to have the following themes suspending pending updates
>> to either fix their accessibility or remove the accessibility-ready tag:
>>
>> Ward: http://wordpress.org/themes/ward
>> NuvioElement Orange: http://wordpress.org/themes/nuvioelement-orange
>> NuvioFutureMag Red: http://wordpress.org/themes/nuviofuturemag-red
>> Madeini: http://wordpress.org/themes/madeini
>> Infinite: http://wordpress.org/themes/infinite
>>
>> Ward has had the review, but it took place after the theme went live and
>> has not been updated; Infinite has recently uploaded an update that removes
>> the tag, but it hasn't been approved yet.
>>
>> Best,
>> Joe
>>
>>
>> --
>> ==================
>> Joseph Dolson
>> Accessibility consultant & WordPress developer
>> http://www.joedolson.com
>> http://profiles.wordpress.org/joedolson
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20140609/8081686f/attachment.html>