I've addressed this issue briefly in the book I'm currently slaving over.
Basically, I think DynAPI is a wash when it comes to accessibilty. The
contents of menus and so on are too tightly integrated with the widget UI
code.
The quickie acid test is to turn off all JS and CSS support in your browser
and hit your page. Any DHTML should collapse into a pile of unstyled DIVs
and SPANs and so on. DynAPI (v. 1 and 2.x) probably fails this test, as it
relies almost completely on JS-generated DIV elements.
It's probably easier to simply create an alternate version of the site for
screen readers, rather than try to make DynAPI behave!
scottandrew
------
scott andrew lepera
[EMAIL PROTECTED]
web stuff: www.scottandrew.com
music stuff: www.walkingbirds.com
Richard Bennett wrote:
As you might be aware, sometime round now the new US Accessibility Laws come
into force, see this article:
http://www.alistapart.com/stories/politics/
That means that those of us doing dev work for US gov instancies using
DynAPI might have a problem, as Dynapi breaks just about all accessibility
rules there are.
Basically it means that people *not* using a normal browser, or mouse or
keyboard must be able to get the information they need from a US gov
website.
So screenreaders for the blind should work, keyboard navigation should be
possible etc
If there are others with ideas on how to set up a US law compatible site
using Dynapi we might be able to put together some kind of blueprint
regarding the do's and don'ts.
Also, it might be advisable to include a clause in our license stating that
Dynapi is not suitable for deployment on sites that fall under the
accessibility laws as-is.
Cheers,
Richard Bennett
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
