WebAIM - Web Accessibility In Mind

E-mail List Archives

Captivate questions


From: Alan Zaitchik
Date: Nov 25, 2015 1:53PM

I'm taking the liberty of reposting an earlier note which didn't trigger any responses, to see if I can get a response from someone with hands-on experience with Captivate 9. I apologize for the noise, but I really need some input. The marketing information on the web is unclear at best, maybe misleading.
Original post:
I've been unable to get a very clear answer about the following, and I hope that someone on this list has direct personal experience that can put my mind at ease.
A customer has insisted that we develop in Captivate 9, despite well-known (or at least reputed) shortcomings of C9 regarding accessibility. After our team developed a few screens I ran them through various tests and I believe that we have the following 508 non-compliance results. But perhaps we just do not know enough about C9 ? That's why I am hoping someone will read this and respond with what we have to do in order to satisfy accessibility requirements in general or 508 requirements in particular- or say "no way- cannot be done!"

What I have found:

1. No skip links are possible.
2. No H1... H6 headings detected by browser accessibility toolbars (tests). Screen reader (JAWS, NVDA) could not list headings.
3. ONCLICK events defined for TOC elements- and I think elsewhere, too- cannot be given a Role attribute.
4. Lists are apparent only as visually formatted elements but are not processed as lists by screen reader
5. Tables cannot be given headings (column and row headings) and screen reader cannot navigate tables as tables nor announce headings when reciting data cells.

Any and all real answers are welcome! I keep finding marketing-quality information about these matters, but I would like to hear from someone with hands-on experience, if that's possible.
Thanks in advance,