Momentum©

Voluntary Product Accessibility Template


Release Version 7.5
April 2017

 

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-2017 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. 9

5                        Section 1194.31 Functional Performance Criteria. 15

6                        Section 1194.41 Information, Documentation, and Support 20

 

 


 


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 ‘Reporting Conformance to ICT Accessibility Standards’, available at https://www.itic.org/dotAsset/00943b29-0586-4a9b-bd20-371fc5fb59f2.pdf .

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: April, 2017

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 with Exceptions

Please see section 3 for details.

Section 1194.22 Web-based Internet Information and Applications

Supports with Exceptions

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 with Exceptions

Please see section 5 for details.

Section 1194.41 Information, Documentation and Support

Supports with Exceptions

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 with Exceptions

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

Defect(s) have been created for the exceptions:

·         DEV-558457, DEV-558287, DEV-560620 (MM-248), DEV-559239, DEV-568249, DEV-567212, DEV-567169   – There is an illogical tab order on some pages within the system. 

·         DEV-559268, DEV-559114, DEV-558282, DEV-558464, DEV-558460, DEV-558423 - Focus is not properly set after a pagination selection is made for a data table or when exiting menus on some pages. Some radio buttons are also missing a visual focus indicator, making it difficult for sighted keyboard users to track focus.

·         DEV-558202 (MM-319) - Some content is not keyboard accessible on the Purchase Query (Basic Search) page.

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 with Exceptions

In most cases, the application does not disrupt or disable any operating system or browser accessibility features.

Defect(s) have been created for the exceptions:

·         DEV-541933 (MM-281), DEV-558276, DEV-558467, DEV-567273, DEV-567279, DEV-568255, DEV-567174  –Some issues occur when Windows High Contrast Mode (HCM) is applied, including: mega menu dropdown icons are not visible, form fields are not distinguishable, some tab states are not distinguishable, focus cannot be tracked on some pages, and expand/collapse icons are not visible.

(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 supports a visible on-screen indication of the currently focused user interface component; the visible focus indicator moves between interactive user interface components as the input focus changes.

Focus is programmatically exposed so Assistive Technologies (AT) can track focus and focus changes.

The application itself also 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 HTML attributes) for user interface elements that are recognized by AT software. When custom web user interface components/widgets are used, development is aligned with the best practices from the W3C’s Accessible Rich Internet Applications (ARIA) specification.

·         DEV-559227, DEV-558651, DEV-558251 (MM-208), DEV-558441, DEV-559064, DEV-568231, DEV-567260, DEV-567157, DEV-567155, DEV-567153, DEV-567151 – The accessible name and role is incorrect and/or missing for some form fields and links.

(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 which is available to the browser, operating system, and AT.

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

Not Applicable

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

Not Applicable

The application itself does not provide a way to adjust color or contrast settings for foreground, background, or other elements. Users may accomplish that by utilizing the capability of the operating system.

(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 with Exceptions

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 HTML attributes.

Defect(s) have been created for the exceptions:

·         DEV-559017 (MM-205), DEV-558207 (MM-262), DEV-558204 (MM-310), DEV-558436, DEV-558993 (MM-245), DEV-559003 (MM-258), DEV-559146 (MM-234) – On some pages there are orphaned form labels, missing form labels, and/or multiple form labels.

·         DEV-534801 (MM-311), DEV-559159, DEV-558451 – Some fields do not have a unique form label.

·         DEV-558414, DEV-534761, DEV-558798 (MM-224), DEV-558216 (MM-235), DEV-558209 (MM-211)– Some fields and error messages are not coded properly and therefore are not announced correctly by the JAWS screen reader.

·         DEV-558796 - Required fields are not defined on the Attachment Upload pages.

 


 

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 with Exceptions

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

Defect(s) have been created for the exceptions:

·         DEV-534725 (MM-275), DEV-559213 - Some meaningful icons are coded as CSS background images and therefore are not conveyed to screen reader users, users who apply HCM, or a user-defined style sheet (USS).

·         DEV-558643 – There is no text equivalent for the link icons on the Links page.

·         DEV-568200 – The QA Header’s favorites icon buttons are missing accessible names

 

(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 with Exceptions

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.

Defect(s) have been created for the exceptions:

·         DEV-559217, DEV-559215, DEV-558645, DEV-558426, DEV-558946, DEV-558195, DEV-558410, DEV-568225, DEV-568027, DEV-567237, DEV-567135 - There is insufficient color contrast for some elements within the application, including expand/collapse links, close icons, document reference modal, some form labels and controls, and text on the Purchase Query page.

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

Supports with Exceptions

The application does not override user-defined style sheets. Defect(s) have been created for the exceptions:

·         DEV-558408, DEV-558791, DEV-558647, DEV-559219, DEV-559133, DEV-558948, DEV-558197, DEV-568227, DEV-568202, DEV-568037, DEV-567250, DEV-567137 – There is an incorrect or missing heading structure on some pages.

·         DEV-534725 (MM-275) –Cascading style sheets (CSS) must be enabled in the web browser for the application to work properly. As a best practice, the application will be developing a message in the browser indicating the content is best viewed with CSS enabled and advising the user to enable CSS (if it is detected that CSS is completely disabled).

·         DEV-534761, DEV-558789 - Required field instructions are missing on some pages within the application informing users of how required fields are indicated. In addition, there are some cases where the required field asterisks are not included within the form label for the field.

·         DEV-559221, DEV-541565, DEV-541540, DEV-558793, DEV-567139, DEV-568229 - List markup is missing or incorrect on some pages.

·         DEV-558400, DEV-559020 – In some cases, field set/legend markup is missing or marked incorrectly.

(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 with Exceptions

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

Defect(s) have been created for the exceptions:

·         DEV-562515 (MM-293) – Some tables contain empty grid cells that should be removed.  

·         DEV-562227 (MM-480) – In some cases, incorrect ARIA table markup is being used (e.g. there is a role of 'rowheader' instead of role='row').

·         DEV-559142, DEV-558979, DEV-558199, DEV-559223 - Some data tables are missing a caption element.

(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 contain data tables with multiple logical levels of headers.

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

Supports with Exceptions

In most cases, the application provides ID, NAME, and TITLE HTML attributes for each frame to assist with identification and navigation.

Defect(s) have been created for the exceptions:

·         DEV-534742- There are some iFrames missing title and name attributes.

(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 HTML 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 with Exceptions

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 HTML attributes.

Defect(s) have been created for the exceptions:

·         DEV-559017 (MM-205), DEV-540936 (MM-344), DEV-540966 (MM-344), DEV-540970 (MM-344), DEV540850 (MM-344), DEV-558207 (MM-262), DEV-558204 (MM-310), DEV-558436, DEV-558993 (MM-245), DEV-559003 (MM-258), DEV-559146 (MM-234), DEV-568206, DEV-567143, DEV-567289 – On some pages there are orphaned form labels, missing form labels, and/or multiple form labels.

·         DEV-534801 (MM-311), DEV-559159, DEV-558451, DEV-567145, DEV-568204 – Some fields do not have a unique or meaningful form label.

·         DEV-558414, DEV-534761, DEV-558798 (MM-224), DEV-558216 (MM-235), DEV-558209 (MM-211) – Some fields and error messages are not coded properly and therefore are not announced correctly by the JAWS screen reader.

·         DEV-558796, DEV-568208, DEV-567253 - Required fields are not defined on some pages.

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

Defect(s) have been created for the exceptions:

·         DEV-559225, DEV-558649, DEV-558229, DEV-560628 (MM-200), DEV-567149 – The Skip Navigation link does not work correctly or is missing on some pages.

(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 with Exceptions

The application supports Assistive Technology (such as screen readers) for blind or visually impaired users. Testing was performed using Internet Explorer (IE) 11 paired with Job Access With Speech (JAWS) versions 16 and 17,  the latest version of NonVisual Desktop Access (NVDA), and the latest version of Window-Eyes.

Defect(s) have been created for the exceptions:

·         DEV-559235, DEV-559241, DEV-559087, DEV-558803, DEV-558653, DEV-558327, DEV-562184 (MM-477), DEV-562211 (MM-475), DEV-568039, DEV-568241, DEV-568237 – Some layout tables within the application are missing ARIA role=”presentation”, which means that screen readers may improperly announce those layout tables as data tables.

·         DEV-562203 (MM-482), DEV-559237, DEV-559207, DEV-559150, DEV-559079, DEV-558362, DEV-558257, DEV-562222 (MM-484), DEV-562220 (MM-483), DEV-562218 (MM-472), DEV-559071, DEV-558325, DEV-562207 (MM-479), DEV-558455, DEV-568243, DEV-568210 – Some dynamic actions and tab states are not immediately conveyed to screen reader users. For example, when the screen reader user activates the Maximize/Minimize option within a summary table, they do not hear an audible confirmation that the table has been maximized or minimized. 

·         DEV-559233 - Sorted column headers are missing the aria-sort attribute to assist screen reader users with understanding the sort status of the column.

·         DEV-559229, DEV-558314, DEV-560701 (MM-486), DEV-562209 (MM-487),  DEV-568233, DEV-568044, DEV-567287, DEV-567210, DEV-567159, DEV-567163, DEV-568047, DEV-567263 – Some elements are not announced or announced incorrectly by screen readers. For example, some buttons are announced simply as their access key value (e.g. “alt+g”) instead of the button name. 

·         DEV-559264 (MM-279)– Confirmation messages are not announced properly when the Acquire, Save or Release buttons are activated on the Inbox page. 

·         DEV-568245, DEV-568213, DEV-568049, DEV-567265 – Some pages have W3C HTML Validation errors

·         DEV-567205 - List Markup Suppressed with Role of Presentation on the navigation Menu

·         DEV-567208 - The parent controls in the navigation are missing the aria-haspopup and aria-hascontrols attributes.

·         DEV-568235, DEV-567161 – Item Links and button are not unique or meaningful on some pages

·         DEV-567165 - Sortable Columns not conveyed semantically on the Statement Reconciliation page

(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 with Exceptions

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

Defect(s) have been created for the exceptions:

·         DEV-534725 (MM-275) – Some issues occur when a user-defined style sheet is applied, including: mega menu dropdown icons are not visible, read-only form fields are not distinguishable, and expand/collapse icons are not visible.

·         DEV-558271 - Information in the summary table of the Purchase Query page is cut off at 200% zoom.  

(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 with Exceptions

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

Defect(s) have been created for the exceptions:

·         DEV-558457, DEV-558287, DEV-560620 (MM-248), DEV-559239, DEV-568249, DEV-567212, DEV-567169   – There is an illogical tab order on some pages within the system. 

·         DEV-562214 (MM-478) – There is an unnecessary tab stop in the first column header cell on some summary tables within the application.

·         DEV-559268, DEV-559114, DEV-558282, DEV-558464, DEV-558460, DEV-558423, DEV-568253, DEV-568215, DEV-568063, DEV-567214, DEV-567172 - Focus is not properly set after a pagination selection is made for a data table or when exiting menus on some pages. Some radio buttons are also missing a visual focus indicator, making it difficult for sighted keyboard users to track focus.

·         DEV-558202 (MM-319), DEV-568247, DEV-568068, DEV-567268, DEV-567167 - Some content is not keyboard accessible on the Purchase Query (Basic Search) page, QA Header Accounting Line, Settings page, calendar icon, and Statement Reconciliation page.

Equivalent Facilitation:

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

 

 

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.

 

The application includes reports that can be exported to multiple formats: Word files, PDF files, Excel files, CSV files, and HTML.

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

The Accessibility chapter confirms Momentum’s commitment to providing an accessible product and contains the following information:

·         A statement on what Section 508 is

·         Information on how to report any accessibility issues encountered while using the application

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

Supports

Momentum provides support services that are available and capable of accommodating the communication needs of users with disabilities. Application support is available via email and telephone.