Lectorra + 508 + JAWS = Disapointment

If you read Trivantis' own document on Lectora's 508 compliance you'll see more than a small number of places where Trivantis themselves say they are non-compliant or that the particular 508 issue is up to the developer to resolve.My guess is that the way Lectora displays a HTML page to an end user (if you look at the source code for a page you'll see a bunch of javascript functions that get called onload to build much of the page) will always mess screen readers.Andrew Poulos

Discussions have been disabled for this post