Accessibility refers to making products usable for people with visual, auditory, motor, and other disabilities.
Examples of accessibility features for software products include screen reader support, text equivalents for graphics, keyboard shortcuts, and change of display colors to high contrast.
The current support for accessibility is detailed in the RoboHelp Accessibility Conformance Report (ACR).
The ACR describes accessibility compliance for RoboHelp according to Section 508, EN 301 549, and WCAG 2.0/2.1.
It can be used as a reference when creating accessible knowledge-based content with RoboHelp and is also provided for 508 compliance verification.
You can create output that is compliant with Section 508 for users who have visual or hearing impairments, mobility impairments, or other types of disabilities. You can also take steps at the design level to remove obstacles for people with disabilities viewing your Adobe RoboHelp projects.
These solutions support government agencies in meeting their users’ needs through Section 508 compliance, as well as companies who are committed to improving accessibility.
Many countries, including the United States, Australia, Canada, Japan, and countries in the European Union, have adopted accessibility standards based on those developed by the World Wide Web Consortium (W3C). W3C publishes the Web Content Accessibility Guidelines, a document that prioritizes actions designers should take to make web content accessible. For information about the Web Accessibility Initiative, see the W3C website at www.w3.org/WAI.
In the United States, the law that governs accessibility is commonly known as Section 508, which is an amendment to the U.S. Rehabilitation Act. Section 508 prohibits federal agencies from buying, developing, maintaining, or using electronic technology that is not accessible to those with disabilities. In addition to mandating standards, Section 508 allows government employees and the public to sue agencies in federal court for noncompliance.
Section 508 is part of the Rehabilitation Act of 1973 requiring that federal agencies develop, maintain, acquire, or use electronic and information technology to make the systems accessible to people with disabilities. The most recent (1998) version of Section 508 establishes enforceable, government-wide standards.
In general, an information technology system is accessible for people with disabilities if it can be used in various ways that do not depend on a single sense or ability. For example, users should be able to navigate with a keyboard, in addition to a mouse (not with a mouse only). Also, the visual and auditory elements of a user interface must accommodate both hearing-impaired and visually impaired users.
Screen readers or text-to-speech utilities (which read the contents of the active window, menu options, or text you have typed) and screen review aids translate onscreen text to speech or to a dynamic, refreshable, Braille display. This assistive technology can provide keyboard assistance or shortcuts, captions for speech and sound, and visual warnings such as flashing toolbars. Tools available include Windows Eye and JAWS.
For the latest information on creating and viewing accessible Adobe RoboHelp content, visit the Adobe RoboHelp Accessibility Overview page on the Adobe website.
Create an Adobe RoboHelp project using the Section 508 option to view and test the output. Generating the Adobe RoboHelp project updates source files containing information about your project and creates output files that you can publish for users. Read the tips for authoring and use the following procedure.
In RoboHelp, you can generate the following output:
For more information on generating output in RoboHelp, see Generate output.
In newer versions of RoboHelp, the output is Section 508-compliant.
If you are using RoboHelp, use these tips to create accessible web output, such as, Frameless and Responsive HTML.
For more information, see Accessibility best practices in Adobe RoboHelp.
A screen reader recites text that appears on the computer screen. It also reads non-textual information, such as button labels and image descriptions in the application, provided in accessibility tags or attributes.
RoboHelp offers limited support for assistive technologies (which includes screen readers and screen magnifiers).
Adobe RoboHelp supports the following screen readers:
Users can use the Tab and arrow keys to navigate through the pages. This helps users navigate elements on the page and read content using a screen reader.
Adobe RoboHelp supports 3:1 color contrast for User Interface controls and 4.5:1 for text-based content and graphics.
Visit Adobe RoboHelp Accessibility Conformance report to know the details of Adobe RoboHelp’s support for above capabilities.
Let’s look at the accessibility features that users can utilize based on their specific needs.
Adobe RoboHelp does not contain content which may trigger seizures.
Adobe RoboHelp strives to provide users with a User Interface that is clear and readable in accordance with WCAG 2.1 standards.
Adobe RoboHelp intends to be functional with limited reach by providing comprehensive support for keyboard users.
We've enhanced features that are related to accessibility. Most of the features are a part of the new improved, more Section 508-compliant User Interface. Some of them are:
There will be further enhancements to the following: