WordPress.org

Ready to get started?Download WordPress

Forums

Accessibility testing with Cynthia Says (5 posts)

  1. revbob
    Member
    Posted 9 years ago #

    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 label tag 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?

  2. revbob
    Member
    Posted 9 years ago #

    Oops, it's just a warning. But still, it might be useful to know what it means.

  3. Anonymous
    Unregistered
    Posted 9 years ago #

    I think you can safely ignore those. In a blog context where you may have several new links per post it just isn't practical to have tabindexes or accesskeys for *every single link*, though you may want to implement them for navigational links.

  4. revbob
    Member
    Posted 9 years ago #

    I went ahead and made a couple more changes so it would pass Bobby too. Since I didn't have a blog entry for today ;-) , I decided to blog everything I did: http://blog.crispen.org/archives/2004/09/17/accessibility-badges/.

  5. Anonymous
    Unregistered
    Posted 9 years ago #

    I have the same problem. How do you fix it?

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.