Lectorra + 508 + JAWS = Disapointment

CDC_Joe wrote:

Andrew- I'm starting to lean towards your opinion, but I'll wait to see what support and their 508 specialists have to say about this, but we're having issues with JAWS reading order also. (But maybe I didn't check the "read everything in order" checkbox in some menu.) I'll go through your list and add my comments too... - buttons being read as visited when they aren't Yup- that happens.- buttons (and images with onclick actions) not reacting to the Enter key Yup- try the space bar- that for some reason works for us.The space bar doesn't work for us.- no real way to have a button which when clicked on resizes all the text - no way to add access keys For access keys, are you referring to keystrokes that trigger either actions or links or something?For that, we haven't had any issues- the one thing you need to realize is that JAWS by default blocks all other keystroke commands, so if you program custom ones, you need to tell your users to deactivate the JAWS ones. (Which as I understand, JAWS is violating § 1194.21(b) "Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer."Good point but why do things work as expected when I hand code a page?[COLOR>- rudimentary table support- no way to add HTML "accessibility" tags to elements What do you mean by this? Alt tags?Tags like acronym, scope, title...- focus not being given to the actual window content without users having to tab past IE's chrome - no external stylesheets that users can replace with their own. Yea. That's a bummer one.- Lectora inexplicable use of fixed font sizes What do you mean by this? Our experience is that inside Lectora, say you're using 12 pt arial- but when you generate html, it appears to be more like 13.5 pt arial. (The same thing happens for Powerpoint) Its now "normal" practice to use proportional fonts.- having to jump through hoops to add "skip to content" functionality This is actually easier with 2007- just use the On Show, Go To, Current Page, Scroll to: (object name right at the top of the content area) Yes, but I'm "forced" into putting all the navigation in a long line at the top of the icon tree.- generally, only being able to define a tabbing sequence by the actual relative location of the icons - how HTML published pages get a title (in the browser's title bar) that matches the actual file name rather than what was set for the project. Yea, that would be nice to define the exact name of the published pages easier. - no apparent support for accelerator keys... So far none of the non-trivial projects we've built with Lectora 2007 are close to approval from our group certifies project that rely on assistive technology. I doubt that approval ever be possible with Lectora 2007.Andrew Poulos