I've been able to get my blog through Section 508 and Priority 1 and 2 of the WCAG accessibility guidelines using the "Cynthia says" validator at http://www.contentquality.com/.
It took two hacks:
- one previously mentioned, to modify index.php to put the
labeltag down inside the form (for the search form) and - a second hack in
wp-includes/template-functions-comment.php
I haven't seen the second hack mentioned. All it requires (on my configuration, ymmv) is to change line 40, the last line in comments_number():
// BC Hack
// echo $blah;
echo $blah . ' for ' . get_the_title();
That cures a fairly important Priority 2 check: not using the same text for more than one link. The repeated text had been "Comments (whatever)".
Where I'm crashing and burning is on two Priority 3 tests:
9.4 Create a logical tab order through links, form controls, and objects.
* Rule: 9.4.1 - All Anchor, AREA, BUTTON, INPUT, OBJECT, SELECT and TEXTAREA elements are required to use the 'tabindex' attribute.
o Warning - One or more Anchor, AREA, BUTTON, INPUT, OBJECT, SELECT and TEXTAREA elements do not use the 'tabindex' attribute.
9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.
* Rule: 9.5.1 - All Anchor, AREA, BUTTON, INPUT, LABEL, LEGEND, and TEXTAREA elements are required to use the 'accesskey' attribute.
o Warning - One or more Anchor, AREA, BUTTON, INPUT, LABEL, LEGEND, and TEXTAREA elements do not use the 'accesskey' attribute.
Does anybody know (a) what the heck this means and (b) a sensible way of curing them?
