Oxygen XML WebHelp VPAT
Introduction
Updated: 07/30/2018
Contact for more information:
Oxygen XML WebHelp Responsive plugin was designed to adhere to the U.S. Government Section 508 accessibility standards. This document describes the accessibility features that address the Section 508 Standards. This VPAT (Voluntary Product Accessibility Template) is an informational tool developed by industry and government to help facilitate the understanding of compatibility issues under Section 508.
Summary Table
1194.22 Web-based intranet and internet information and applications.
| Criteria | Supporting Features | Remarks and Explanations |
(a) A text equivalent for every non-text element shall be provided
(e.g., via “alt”, “longdesc”, or in element
content). | Supported with exceptions | The process that produces the WebHelp Responsive accessible output uses
information extracted from the DITA topics. It is the technical writer's
responsibility to write accessible-friendly DITA topics.The developers who customize the WebHelp output are responsible for ensuring
that the template they customize conforms to this criterion. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Supported with exceptions | WebHelp Responsive plugin offers support to transfer multimedia objects (video,
audio) from DITA topics to the generated HTML pages. Technical writers are
responsible for ensuring that they use multimedia objects that conform to this
criterion. |
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | Supported with exceptions |
|
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Supported | The WebHelp Responsive output is readable without requiring any
stylesheet. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | Not applicable | The product contains no server-side image maps. |
| (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. | Supported with exceptions | Technical writers can insert image maps in DITA topics. They are responsible
for specifying the information required to generate accessible image maps. |
| (g) Row and column headers shall be identified for data tables. | Supported with exceptions | Technical writers can insert tables in DITA topics. They are responsible for
inputting the information required to generate accessible tables. |
| (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. | Supported with exceptions | Technical writers can insert tables in DITA topics. They are responsible for
inputting the information required to generate accessible tables. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation. | Not applicable | The WebHelp Responsive output does not use frames. |
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Not applicable | The screen does not flicker with frequencies greater then 2 Hz and lower than
55 Hz. |
| (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. | Not applicable | Accessibility provisions in WebHelp Responsive output can be provided without
requiring a separate text-only version. |
| (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. | Supported with exceptions | The developers who customize the WebHelp output are responsible for ensuring
that the template they customize conforms to this criterion. |
| (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with 1194.21(a) through (l). | Not Applicable | This product does not use any plugins or applets. |
| (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. | Supported with exceptions | The developers who customize the WebHelp output are responsible for ensuring
that the template they customize conforms to this criterion. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Supported | |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Not applicable | WebHelp Responsive output does not require a timed response as part of its core
functionality. |
Note: This VPAT pertains only to the HTML output generated by the WebHelp Responsive plugin as shipped and not to any customization. It specifically applies to version 20.1 or above and it does not apply to any versions prior to this.
Supported Platforms
All accessibility tests have been carried out in the following environment:
- NVDA (NonVisual Desktop Access) version 2018.1.1 with Firefox version 60.0.1 and Chrome version 66.0.3359.181.
- Windows 10 Narrator with Microsoft Edge browser.
However, this does not mean that WebHelp Responsive-generated output has any issue with other modern, standards-compliant browsers and alternative screen reader solutions. In any case, if you encounter any accessibility-related issue while using WebHelp Responsive generated output, contact the Oxygen support team. All accessibility issues are treated with utmost attention.
This document is for informational purposes only. SYNCRO SOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
