<br><div class="gmail_quote"><div class="gmail_quote">2009/8/10 Alastair Campbell <span dir="ltr"><<a href="mailto:alastc@gmail.com" target="_blank">alastc@gmail.com</a>></span><div class="im"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
The accessibility of an app like Wordpress is quite a wide ranging<br>
challenge, I guess it's best to pick areas and try and improve the<br>
core coding? I would struggle to find time to do a proper review (as<br>
Joe Clark did a few years ago<br>
(<a href="http://joeclark.org/access/webaccess/WordPress-ATAG-evaluation.html" target="_blank">http://joeclark.org/access/webaccess/WordPress-ATAG-evaluation.html</a>).<br>
The admin area and accessibility guidelines have moved on since then,<br>
so that probably isn't relevant anymore.<br>
<br></blockquote></div></div><br>WordPress has moved on, and so has both the understanding of accessibility and the guidelines themselves.<br><br>The three sets of guidelines we really need to focus on are:<br><br>ATAG (specifically the backend) <a href="http://www.w3.org/WAI/intro/atag" target="_blank">http://www.w3.org/WAI/intro/atag</a>;<br>
WCAG 2 (both frontend and backend) <a href="http://www.w3.org/WAI/intro/wcag" target="_blank">http://www.w3.org/WAI/intro/wcag</a>;<br>WAI-ARIA (again, applies to both frontend and backend) <a href="http://www.w3.org/WAI/intro/aria" target="_blank">http://www.w3.org/WAI/intro/aria</a><br>
<br>Ironically, since Joe wrote that evaluation, WordPress has gone backwards in some areas, despite making up a lot of ground in others. <br>It would be great to do a new evaluation against the current guidelines - this could help provide focus for this group.<br>
<font color="#888888">
<br>Lynne<br><br><br>
</font></div><br>