WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: mouseover/hover and keyboard accessible expandablemenu?

for

From: Jason Megginson
Date: Nov 6, 2009 11:00AM

>I can only put in writing my 508 findings and the client has to decide
>hence my query.

>This brings up another issue. Unfortunately to most developers 508 in
>an intellectual issue, and if a page passes any of the 508 validators,
>then the page is accessible, but many of these validators do not check
>for AJAX, jquery and other functionality that is commonly used, other
>than manually checking pages, are there any validators addressing
>these issues.

>How to tell a client in fact that this passes the validator but is not
>usable or accessible to those with major mobility and visual issues?

Hi Nancy,

There is only so much that can be tested automatically. Not all of the
Section 508 paragraphs can be tested with validators. In addition, the
functional performance criteria of Section 508 (Subpart C) should never be
overlooked and should be included in your analysis. From my experience,
many people have the misconception that accessibility is a blind issue or
a "JAWS" issue.

Manual testing and Assistive technology testing are necessary elements to
a testing methodology. If there is equivalent facilitation to inaccessible
drop-down menus, document it accordingly. I think the several examples
provided in this thread are enough to help you reach the idea of
equivalent access. My advice is to develop the most "accessible" approach
to satisfy the technical and functional requirements based on your current
design.


Jason Megginson