PowerMapper
PowerMapper
OnDemand Suite VPAT - Voluntary product accessibility template
| Criteria | Supporting Features | Remarks and explanations |
|---|---|---|
| Section 1194.21 Software Applications and Operating Systems | Supported | See below for VPAT |
| Section 1194.22 Web-based Internet Information and Applications | Supported | See below for VPAT |
| Section 1194.23 Telecommunications Products | Not Applicable | Not a telecommunications product |
| Section 1194.24 Video and Multi-media Products | Not Applicable | Not a video or multi-media product |
| Section 1194.25 Self-Contained, Closed Products | Not Applicable | Not a self-contained, closed product |
| Section 1194.26 Desktop and Portable Computers | Not Applicable | Not a desktop or portable computer |
| Section 1194.31 Functional Performance Criteria | Supported | See below for VPAT |
| Section 1194.41 Information, Documentation, and Support | Supported | See below for VPAT |
| Criteria | Supporting Features | Remarks and explanations |
|---|---|---|
| (a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. |
Supported with exceptions The web application supports all standard user interface keyboard features of the browser user interface. |
Third-party plugins such as Flash and Java may not be accessible, when inaccessible third-party sites are displayed in the web app (e.g. sites being tested for accessibility typically have accessibility problems). With some combinations of third-party content and plugin (particularly older plugins) the tab order skips over them
completely, so form controls within them require a mouse. |
| (b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. | Supported | Supports tabbing, Mouse Keys, Sticky Keys, Filter Keys and Toggle Keys. |
| (c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes. | Supported | The web app uses standard HTML markup, which support browser accessibility APIs to expose the location of the focus indicator and its interface elements to assistive technologies. |
| (d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text. | Supported | The web app uses standard HTML markup, which support browser accessibility APIs to expose this information to assistive technologies. The web app also supports the W3 ARIA standard to communicate role, state, and property information to assistive technologies. |
| (e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. | Supported | |
| (f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. | Supported | The web app uses standard HTML markup, allowing assistive tech to navigate web pages character-by-character using standard assistive tech keyboard shortcuts. |
| (g) Applications shall not override user selected contrast and color selections and other individual display attributes. | Supported |
The web app respects the user's settings, and allows use the browser Zoom feature, and other system accessibility features such as high contrast. |
| (h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Supported | The only animated feature is the progress bar displayed during scans. |
| (i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | Supported | The application does not use color as the only way to convey information, indicate actions, prompt responses, or distinguish visual elements. |
| (j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. | Supported |
The application respects the user's settings, and allows the user to override the display settings of web-page authors who have used inaccessible font colors and sizes via a Zoom feature. In addition to high contrast, and other system accessibility features, the application obeys the system font size. |
| (k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. | Supported | The application does not use flashing or blinking text in its user interface. |
| (l) When electronic forms are used, 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 | The application uses standard HTML form markup, allowing assistive tech to calculate the accessible name for each form field. |
| 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 |
The application provides text equivalents for all non-text items. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Supported |
The application does not contain any multimedia presentations. |
| (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 | The application never uses color as the sole way to present information. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Supported | Pages are constructed using semantic HTML allowing them to function with or without stylesheets. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | Supported | The application doesn't use 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 | The application doesn't use server-side and only uses client-side image maps for site maps. |
| (g) Row and column headers shall be identified for data tables. | Supported |
Where data tables are used they are marked up with headers the work in current screen readers (JAWS, NVDA, VoiceOver). |
| (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 | Tables where two logical levels of headers exist are marked up accordingly. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation. | Supported | When FRAMEs or IFRAMEs are use they have a TITLE attribute that identifies purpose and orients user. |
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Supported |
No pages cause flicker. Note that the product may detect flickering graphics on sites and web pages being tested. |
| (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. | Supported | All pages comply with the other 1194.22 provisions, so text-only equivalents are not required. |
| (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 | All content controlled by JavaScript is accessible via the keyboard and to screen reader users. |
| (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). | Supported | No pages require plug-ins 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 | All online forms are marked up using HTML features that provide access to Assistive Technology. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Supported | Skip links are provided on every page, and the main content is always preceded by an H1 allowing users to skip using heading levels. |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Supported | No timed responses are required. |
| Criteria | Supporting Features | Remarks and explanations |
|---|---|---|
| (a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided. | Supported | The application uses semantic HTML which allows browser accessibility APIs to expose this information to screen readers. The application is tested with JAWS and NVDA on Windows, and VoiceOver on OSX and iOS. |
| (b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people what are visually impaired shall be provided. | Supported | The application supports assistive technology such as screen readers and screen magnifiers, as well as the browser Zoom feature. |
| (c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided. | Supported |
The application does not require audio for operation.
|
| (d) Where audio information is important for the use of the product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. | Supported | The application does not use audio for notifications. |
| (e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided. | Supported | No modes of operation require user speech |
| (f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. | Supported | The application supports keyboard accessibility through browser keyboard shortcuts, access keys and tab order to all significant features so use of a mouse is not required. Keyboard-only text selection is supported via caret browsing. |
| Criteria | Supporting Features | Remarks and explanations |
|---|---|---|
| (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. | Supported |
The help system is available in HTML. Alternate formats are available from our web site at no additional charge. |
| (b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. | Supported | The built-in help system includes an Accessibility section detailing keyboard shortcuts and other accessibility features. |
| (c) Support services for products shall accommodate the communication needs of end-users with disabilities. | Supported |
Support options are listed at https://www.powermapper.com/support/. Options include email support and phone support. |
This document is for informational purposes only. POWERMAPPER SOFTWARE MAKES NO WARRANTIES, EXPRESS IMPLIED OR STATUTORY, IN THIS DOCUMENT. This document represents the current view of PowerMapper Software at the date of publication. Because we must respond to changing market conditions, it should not be interpreted to be a commitment on the part of PowerMapper Software, and PowerMapper Software cannot guarantee the accuracy of any information presented after the date of publication.