1 Reply Latest reply on Jul 27, 2010 10:59 PM by Willam van Weelden

    ADA Fixes for Robohelp: Frames & CSS Issues


      Fellow Robohelpers:


      I am attempting to resolve a set of major issues within Robohelp 8


      a) Frames are not properly named in Robohelp 8. Is anyone aware with which files to change (post generation or pre-generation of outputs) to rename Frames so the visually impaired user is clearly informed which frame they are on


      b)When you disable CSS, the navigational elements (frames) become a jumble. They do not function correctly (TOC, Index, Search) since Robohelp is heavily CSS dependent and hides objects (text fields, the various left hand navigational elments) behind CSS.


      Any reccomendations how to resolve these, or insights as to how to make Adobe aware of this! I have been reaching out to them about this for quite some time! I am hoping capturing a workaround for at least a) will make the tool one step closer to ADA compliance (screen reader compliance)