yahgrp at poplarware.com
Fri May 1 16:11:20 GMT 2009
Well, I would agree with you on all counts. The WP back end is clearly
in violation of the WCAG... But what should we do about it?
The first thing to do would probably be WP Powers that Be to commit to
making WP's back end WCAG compatible, or at least to agree that if it
isn't, it's a serious bug. The next step would be to identify the
actual WCAG violations, which would probably require an expert on
accessibility (rather than someone like me making guesses) doing an
Then of course, to fix the issues, which we can all participate in and
is probably doable. For instance, the separate "Media" page allows you
to upload a file and edit the caption, etc., all without use of
proof of concept, it's there).
Austin Matzko wrote:
> task, then it's a bug.
> * The WP requirements page says nothing about having a
> * From the first paragraph, the WP features page trumpets its W3C
> standards-compliance . By failing to gracefully degrade in older
> clients, WP violates the W3C "Web Content Accessibility Guidelines"
> * WP hurts its potential market share by excluding those who must
> follow accessibility guidelines for their site.
>  http://wordpress.org/about/requirements/
>  http://wordpress.org/about/features/
>  http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/#gl-new-technologies
Jennifer Hodgdon * Poplar ProductivityWare
Drupal, WordPress, and custom Web programming
More information about the wp-hackers