Lectorra + 508 + JAWS = Disapointment

These are questions for Trivantis... I'd suggest sending them to support@trivantis.com.My guess is their responses will be:-how do you add a londesc to an element? Longdesc is not a requirement for 508 compliance. You can add additional metadata to an element by adding in an "invisible" text field that's read after the element. (Invisible= 1 point font same color as bg)- how do you get all question types to work with style sheets turned off? Not all questions are 508 compliant. (Drag drop for example.)- is using a text box a good idea for a table column header? Uh... sure?- how does lectora allow for a "text-only page, with equivalent information or functionality"? Lectora allows this by allowing you to create it yourself.- what method does lectora provide to skip repetitive navigation? Yeah it can be done but it certainly isn't an ideal way to author with lectora. What about a skip nav hyperlink created the same way as you'd create one in html? How's this different from say, Dreamweaver?Lectora makes it easier by allowing you to create a varable so you don't have to click skipnav on every page.- how do you allow the element with focus to automatically highlight. Good Question. But how would a visual highlight benefit blind users, for example.Have you found a usability lab that will certify a non-trivial course built with lectora as being suitable for people who rely on assistive technologies? Good Luck with that... It will be difficult to find a company to certify this sort of thing, because by placing their stamp on it, they become LEGALLY on the hook. (Or at least this is how I'm aware if it.)And last and not least, how (after you've written custom javascript and found tedious-to-author workarounds to some issues) hand over a course to lectora novices to maintain? We write no custom javascript, and hand over the complete Lectora source over to the client. Having novices edit them has exactly the same risk of disaster as having a novice web developer edit a dreamweaver-based course. This is a non-issue in my opinion. The skill of editors is not a lectora issue. And as a developer, if you know that novices are going to be maintaining the course, it is your responsibility to design the course with that in mind. Keep the complicated stuff out and make sure to include documentation. But that's just a professionalism thing in my opinion.But then again what do I know?