Guidance Needed on Adding ALT Text for WCAG 2.1 Compliance in Responsive HTML5 Output (RoboHelp 2026.03.13) Hi everyone,I’m currently working on improving the accessibility compliance of our documentation generated using Adobe RoboHelp (Version 2026.03.13).We have a significant amount of legacy content created over several years, and we’ve identified that many images across topics do not have ALT text defined. This is a concern from an accessibility standpoint, as it does not meet the requirements of World Wide Web Consortium WCAG 2.1 guidelines, particularly under text alternatives.Looking for guidance on the following:Best approach to remediation: What is the most efficient way to add ALT text to a large number of existing images? Are there any bulk editing options, scripts, or workflows within RoboHelp that can help streamline this process? Responsive HTML5 Output Compliance: We are using the Responsive HTML5 preset for publishing. Does this output type support WCAG 2.1 compliance by default? Or are there specific configurations/settings required to ensure accessibility compliance? Validation and Testing: What tools or screen readers do you recommend to validate accessibility compliance for RoboHelp outputs? I came across information suggesting that Frameless output and Microsoft HTML Help (.chm) may have certain built-in compliance advantages, but I’d like to better understand how Responsive HTML5 compares and what additional steps are needed.Any insights, best practices, or real-world experiences would be greatly appreciated!Thanks in advance for your support.

Participating Frequently

質問

Guidance Needed on Adding ALT Text for WCAG 2.1 Compliance in Responsive HTML5 Output (RoboHelp 2026.03.13)

Forum|Forum|4 days ago
March 27, 2026
返信数 3.
36 ビュー

Guidance Needed on Adding ALT Text for WCAG 2.1 Compliance in Responsive HTML5 Output (RoboHelp 2026.03.13)

Hi everyone,

I’m currently working on improving the accessibility compliance of our documentation generated using Adobe RoboHelp (Version 2026.03.13).

We have a significant amount of legacy content created over several years, and we’ve identified that many images across topics do not have ALT text defined. This is a concern from an accessibility standpoint, as it does not meet the requirements of World Wide Web Consortium WCAG 2.1 guidelines, particularly under text alternatives.

Looking for guidance on the following:

Best approach to remediation:
- What is the most efficient way to add ALT text to a large number of existing images?
- Are there any bulk editing options, scripts, or workflows within RoboHelp that can help streamline this process?
Responsive HTML5 Output Compliance:
- We are using the Responsive HTML5 preset for publishing.
- Does this output type support WCAG 2.1 compliance by default?
- Or are there specific configurations/settings required to ensure accessibility compliance?
Validation and Testing:
- What tools or screen readers do you recommend to validate accessibility compliance for RoboHelp outputs?

I came across information suggesting that Frameless output and Microsoft HTML Help (.chm) may have certain built-in compliance advantages, but I’d like to better understand how Responsive HTML5 compares and what additional steps are needed.

Any insights, best practices, or real-world experiences would be greatly appreciated!

Thanks in advance for your support.

frameexpert

Community Expert

As Jeff said, this may be something that could be scripted if you associated the image names with the desired ALT text in a spreadsheet. Please contact me offlist if you want to explore this further. rick at frameexpert dot com

www.frameexpert.com

Jeff_Coatsworth

Community Expert

Because (I imagine) every image is different & would require different ALT text be added to the source XHTML in the topics, that a bulk approach wouldn’t work. You might look to using a spreadsheet source to co-relate image file name with ALT text to be added and then use it as the source for a script to do that action. Somebody like @frameexpert is a guru with scripting.

As far as point #2 - you’d need to check RH’s accessibility page - I think they go into which outputs are better suited.

Point #3 - Google is probably your friend on this one.

Peter Grainge

Community Expert

1] The most efficient way is one by one as that is the only way. Sorry. No scripts etc.

2] To the best of my knowledge it is only Frameless templates that are compliant. See https://www.grainge.org/RoboHelp_Tour/rh2022/outputs/templates_online.htm?rhhlterm=compliance&rhsearch=compliance#:~:text=or%20export%20it.-,508%20and%20WCAG%20Compliance,-All%20frameless%C2%A0skins Note it is the default frameless templates that are compliant. Your content and any template customisation is another matter.

3] Sorry I can’t help you on external validation.

Where did you find that frameless and CHMs may have issues and what issues? Certainly I would expect CHMs to have issues as they are such an old technology, they haven’t been updated for over 20 years. Frameless though should only have issues if you content is not compliant, as above.

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

S

sidwrites作成者

Participating Frequently

Hello Peter!

Thank you for the reply.

I was taking help some help from https://chatgpt.com/share/69c644fc-8bac-8320-b6e5-270b8fa22700 and you can refer it here.

Jeff_Coatsworth

Community Expert

Your own chat says CHMs don’t work - and it says that your HTML5 output just needs polishing to make it compliant.

Looking for guidance on the following:

サインアップ

ソーシャルログイン

コミュニティへログイン

ソーシャルログイン

ファイルをウイルススキャンする。

このファイルはダウンロードできません