Momentum©

Voluntary Product Accessibility Template


Release
Version 7.3
July 2015

 

PROPRIETARY AND CONFIDENTIAL

This commercial computer software is delivered with Restricted Rights to the Government. Use, reproduction, or disclosure is subject to the restrictions set forth in the FAR, DFAR, or other license provisions referenced in the contract. Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted.

COPYRIGHT

© 1997-2015 CGI Federal Inc. All rights reserved.

The Momentum® software is the copyrighted work of CGI Federal Inc., its related entities and/or its suppliers. Use of the software is governed by the terms of the end user license agreement, if any, which accompanies or is included with the software.

Unless CGI Federal explicitly gives you permission within a license agreement accompanying the software, you may not copy, modify, distribute, display, license, or sell the software or any of its components.

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of CGI Federal.

PATENT

The software is protected by United States Patent Nos. 6,343,279; 6,532,450; and 6,910,021.

 

 

Table of Contents

1            About the Voluntary Product Accessibility Template. 1

1.1         Document Structure. 1

1.2         Sources and References. 1

2            Summary. 3

2.1         Accessibility Summary. 3

3            Section 1194.21 Software Applications and Operating Systems. 4

4            Section 1194.22 Web-based Internet Information and Applications. 7

5            Section 1194.31 Functional Performance Criteria. 10

6            Section 1194.41 Information, Documentation, and Support 12

 

 


 


1                            About the Voluntary Product Accessibility Template

CGI Federal is dedicated to providing solutions that are accessible to people with disabilities. Section 508 of the Rehabilitation Act requires federal agencies to provide disabled employees and members of the public access to electronic and information technology that is comparable to the access available to others.

CGI Federal provides this Voluntary Product Accessibility Template (VPAT) to clarify support for accessibility criteria and to assist Federal contracting officials (or other buyers) in making assessments regarding products and services.

1.1                       Document Structure

Section 2.1 lists which application and version to which this VPAT applies. The table in Section 2.2 of the VPAT provides a summary view of the Section 508 subsections. The tables in subsequent sections provide more detailed views of each subsection.

Each table contains three columns. In the summary table, the first column describes the subsections of subparts B and C of the Section 508 Standards; in the detail tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product using one or more of the following recommended phrases: Supports, Supports with Exceptions, Supports through Equivalent Facilitation, Supports when Combined with Compatible AT, Does Not Support, Not Applicable, and Not Applicable – Fundamental Alteration Exception Applies. The third column contains examples from the application as well as any notes or clarifications regarding the product or interpretation.

1.2                       Sources and References

The general structure and content of this document follows from the version of the template provided by the Information Technology Industry Council. At the time of this writing, a copy of that document is available at http://www.itic.org/public-policy/accessibility.  

 

The responses in Sections 2, 3, 4, 5, and 6 use the language recommended by the Information Technology Industry Council's VPAT FAQ, available at http://www.itic.org/index.php?submenu=Resources&submenu=Resources&src=gend ocs&ref=vpat&category=resources.

The responses provided in Section 3 are based on the interpretations available from the United States Access Board  at http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/guide-to-the-section-508-standards/software-applications-and-operating-systems-1194-21. Similarly, the responses provided in Section 4 are based on the explanations available at http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/guide-to-the-section-508-standards/web-based-intranet-and-internet-information-and-applications-1194-22.

2                            Summary

Date: July 24, 2015

Name of Product: Momentum Financials/Acquisitions

Contact for More Information: Momentum.Support@cgifederal.com

2.1                       Accessibility Summary

Criteria

Supporting Features

Remarks and Explanations

Section 1194.21 Software Applications and Operating Systems

Supports

Please see section 3 for details.

Section 1194.22 Web-based Internet Information and Applications

Supports

Please see section 4 for details.

Section 1194.23 Telecommunications Products

Not Applicable

Momentum Financials/Acquisitions is not a telecommunications product.

Section 1194.24 Video and Multi-media Products

Not Applicable

Momentum Financials/Acquisitions is not a video or multi-media product.

Section 1194.25 Self-Contained, Closed Products

Not Applicable

Momentum Financials/Acquisitions is not a self-contained closed product.

Section 1194.26 Desktop and Portable Computers

Not Applicable

Momentum Financials/Acquisitions is not a desktop or portable computer.

Section 1194.31 Functional Performance Criteria

Supports

Please see section 5 for details.

Section 1194.41 Information, Documentation and Support

Supports

Please see section 6 for details.

 


 

3                            Section 1194.21 Software Applications and Operating Systems

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.

Supports through Equivalent Facilitation

The sitemap page provides equivalent functionality as the application menu, which cannot be navigated via the keyboard alone.

(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.

Supports

The application does not disrupt or disable any operating system or browser accessibility features.

(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.

Supports

The application provides various forms of indicating current focus, including the standard text input cursor and border highlighting for widgets as well as background highlighting for widget labels and menu items.

(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.

Supports

The application provides industry-standard accessibility information (such as LABEL tags and ALT attributes) for user interface elements.

(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.

Supports

The application uses icons and status indicators consistently.

(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.

Supports

The application displays textual information using standard HTML.

(g) Applications shall not override user selected contrast and color selections and other individual display attributes.

Supports

The application provides color and style settings, consisting of preconfigured themes.

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

Supports

The application provides a plain text version of information represented by an animation.

(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.

Supports

The application does not use color as the only means of conveying information. For example, if a field value is required, the application prefixes the field’s label with an asterisk of configurable color.

(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.

Supports

The application allows the user to adjust colors for all text-based onscreen elements. When selecting colors, the application provides numerous options that can produce varying ranges of contrast.

(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.

Not Applicable

The application does not use flashing or blinking elements.

(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.

Supports

The application allows full access to form elements using the keyboard and provides keyboard shortcuts to buttons that result in the submission of the form. In addition, the application provides field element information to assistive technology via LABEL tags with FOR attributes.

 


 

4                            Section 1194.22 Web-based 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).

Supports

The application provides text equivalents for all non-text elements via the use of HTML ALT attributes.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Not Applicable

The application does not use 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.

Supports

The application does not use color as the only means of conveying information. For example, if a field value is required, the application prefixes the field’s label with an asterisk of configurable color.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

Supports

While the application uses style sheets, removing the style sheets does not prohibit the application from functioning. In addition, the application does not override user-defined style sheets.

(e) Redundant text links shall be provided for each active region of a server-side image map.

Not Applicable

The application does not use 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.

Not Applicable

The application does not use image maps.

(g) Row and column headers shall be identified for data tables.

Supports

The application uses standard HTML tags (THEAD and TH) to identify headers and standard HTML attributes (SCOPE) to correlate data cells to headers.

(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.

Not Applicable

The application does not use multiple logical levels of headers.

(i) Frames shall be titled with text that facilitates frame identification and navigation

Supports

The application provides ID, NAME, and TITLE attributes for each frame to assist with identification and navigation.

(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 application does not use flashing or blinking elements.

(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

The application does not require a text-only page to meet the provisions of this part.

(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.

Supports

The application provides functional information via the use of the TITLE and ALT attributes

(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

The application does not require an applet or plug-in present on the client system to interpret page content.

(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.

Supports

The application allows full access to form elements using the keyboard as well as provides keyboard shortcuts to buttons that result in the submission of the form. In addition, the application provides field element information to assistive technology via LABEL tags with FOR attributes.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Supports

The application allows the user to skip repetitive navigation links. In addition, on data entry screens, the application defaults the current focus to the first user-editable input field.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Supports

After a system-configurable timeout period, the application asks the user if more time is needed. If the user confirms the question, the application resets the timeout period and the user may continue working.

 

Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4


 

5                            Section 1194.31 Functional Performance Criteria

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.

Supports

The application supports assistive technology (such as screen readers) for blind or visually impaired users.

(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 who are visually impaired shall be provided.

Supports

The application supports assistive technology (such as screen readers) for blind or visually impaired users.

(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

Not Applicable

The application does not use sound.

(d) Where audio information is important for the use of a 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.

Not Applicable

The application does not use sound.

(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.

Not Applicable

The application does not require the user to speak.

(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.

Supports

The application supports keyboard navigation as well as the use of assistive technologies (such as StickyKeys in Microsoft Windows).

 


 

6                            Section 1194.41 Information, Documentation, and Support

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

Supports

The application help documentation is provided in HTML format. Additional formats can be provided upon request.

(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.

Supports

The application help documentation and install guides include sections on the accessibility features of the product, in HTML format. Additional formats can be provided upon request.

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

Supports

Application support is available via email and telephone.