Question
508 compliance woes
I'm using Robohelp X3 on the pc platform.
508 compliance has become a priority issue for my employer. I have a large (1500 page) WebHelp file and have spent the past few weeks adding alt tags, language tags, table summaries, etc.
Yesterday I compiled the Webhelp and selected the 508 compliant option. Ran the compiled help through our compliance tool and what a disaster.
The problem I am having is with the files Robohelp generates to run the Help - the frame sets, the icons it adds in the table of contents, and the scripts Robohelp inserts. Framesets are not titled, frames are not named, alt tags are non-existent, noscript tags and language tags are not used - these are all Level One violations. I have scoured the help files to discover how to repair these files, but there appears to be no method other than opening up each of the "w" files and doing the fixes manually - the fact that the tasks have to be repeated with every compile is a strong indicator (hah) that RH is NOT rendering 508 compliant help.
Has anyone else run into a similar situation? Would switching to the X5 version solve this little problem? Is there someplace in RH where I can go to configure these "w" pages ONCE instead of manually repairing each file after every compile? RH Help tells me to doubleclick on the frameset to open the frameset dialog or call it from the file menu -- it's not on the file menu and the pages I need to open aren't accessible inside RH.
Thanks
Russ
508 compliance has become a priority issue for my employer. I have a large (1500 page) WebHelp file and have spent the past few weeks adding alt tags, language tags, table summaries, etc.
Yesterday I compiled the Webhelp and selected the 508 compliant option. Ran the compiled help through our compliance tool and what a disaster.
The problem I am having is with the files Robohelp generates to run the Help - the frame sets, the icons it adds in the table of contents, and the scripts Robohelp inserts. Framesets are not titled, frames are not named, alt tags are non-existent, noscript tags and language tags are not used - these are all Level One violations. I have scoured the help files to discover how to repair these files, but there appears to be no method other than opening up each of the "w" files and doing the fixes manually - the fact that the tasks have to be repeated with every compile is a strong indicator (hah) that RH is NOT rendering 508 compliant help.
Has anyone else run into a similar situation? Would switching to the X5 version solve this little problem? Is there someplace in RH where I can go to configure these "w" pages ONCE instead of manually repairing each file after every compile? RH Help tells me to doubleclick on the frameset to open the frameset dialog or call it from the file menu -- it's not on the file menu and the pages I need to open aren't accessible inside RH.
Thanks
Russ
AdChoices