Momentum©

Voluntary Product Accessibility Template


Release Version 7.5 SP1
October 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. 14

5                        Section 1194.31 Functional Performance Criteria. 22

6                        Section 1194.41 Information, Documentation, and Support 30

 

 


 


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.1 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: October, 2017

Name of Product: Momentum Financials/Acquisitions

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

2.1                       Accessibility Summary

This VPAT applies to the 7.5.1 Release for Momentum, Performance Budgeting, and Vendor Self-Service (VSS).

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) with known exceptions.

Equivalent Facilitation:

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

Momentum has the following exceptions:

·         Some content is not keyboard accessible within Momentum. This includes the following: pagination, sorting, lock/group, and other controls for data tables, menu items, Browse buttons, and the editable table cells on the Contract File page. [MM-319, MM-1360, MM-1491, MM-1531, MM-1584, MM-8140, MM-8120, MM-8139, MM-8277]

·         Focus is not properly set after some actions (e.g. after a modal dialog is opened/closed, after interacting with a menu, etc.) [MM-1096, MM-1365, MM-1341, MM-1139, MM-1115, MM-1147, MM-7704, MM-8360]

·         There is an illogical tab order on some pages within the system. [MM-1566, MM-248, MM-1129, MM-221, MM-1572, MM-2182, MM-4424, MM-4638, MM-4743]

·         Keyboard users are able to tab to non-interactive elements on some pages, such as disabled fields or tables without interactive functionality. [MM-8345, MM-8278, MM-4341]

·         There are unnecessary tab stops on some items within the application. For example, keyboard users typically tab to the first column header within data tables even if it does not contain any interactive elements. [MM-478, MM-1541, MM-8285, MM-8144]

·         Table navigation commands are not explained to users on the Line Level Attachments modal dialog. Keyboard users therefore do not know how to edit cells within the table. [MM-8344]

·         There are some custom ARIA controls in Momentum that are keyboard accessible but do not fully follow the keyboard interaction described for the control in the WAI-ARIA Authoring Practices Guide (APG). For example, for some custom menu controls the user can access each menu item via tabbing but the APG indicates that these items should be accessed using the arrow keys. Similarly, there are some modal dialogs that can be closed by activating the “X” close button within the dialog but do not close when the Escape key is pressed. [MM-1354, MM-8359]

Performance Budgeting has the following exceptions:

·         Some text fields and radio buttons are not keyboard accessible and therefore cannot be populated. For example, the Layout Type field is not keyboard accessible on the Create Generic Budget Request page. [MM-823, MM-7940]

·         The calendar control is not fully keyboard accessible. This prevents the keyboard user from being able to navigate to the previous/next months and fully interact with the control. [MM-8228]

·         Focus is not managed correctly for some pages containing sort functionality. Pressing the Enter key from somewhere on the page can sometimes cause the Sort modal dialog to open unexpectedly. [MM-8257]

·         The tab order is not logical on some pages. For example, keyboard/screen reader users do not encounter fields in the correct order on the Attachment modal dialog. [MM-1516]

·         There are excessive tab stops for the buttons associated with the data table on the Formulated System Query (FSQ) Definition page. [MM-7926]

·         Table navigation commands are not explained to users for the FSQ Definition table. Keyboard users therefore do not know how to edit cells within the table. [MM-8259]

VSS has the following exceptions:

·         Some content is not keyboard accessible on the Create Referenced Invoice page and View Solicitation Orders page. This includes custom dropdown menus and checkboxes as well as the Lock/Group functionality on the tables. [MM-1212, MM-1164, MM-1126, MM-1295]

·         Table navigation commands are not explained to users for the Vendor Approval table. Keyboard users therefore do not know how to edit cells within the table. [MM-8309]

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

Momentum has the following exceptions:

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. [MM-1547, MM-1546, MM-1206, MM-1119, MM-1167, MM-1239, MM-1573, MM-1571]Performance Budgeting has the following exceptions:

·         The custom checkboxes on the Edit Budget Layout page disappear when HCM is applied. [MM-853]

VSS has the following exceptions:

·         The custom checkboxes on various pages (e.g. View Solicitation Orders, etc.) disappear when HCM is applied. [MM-1275, MM-1262, MM-1118]

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

In most cases, 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.

Momentum has the following exceptions:

·         Cursor focus is not visible when keyboard users tab to controls on certain pages, such as the radio buttons on the Purchase Query – Advanced Search page. [MM-1183]

·         Some list items and table elements are not visible but have tabindex=“0” defined, which places them incorrectly in the tab order. Since these items aren’t visible, the focus indicator disappears when they receive focus, causing keyboard users to not be able to see where their focus is at on the page. [MM-8345, MM-8278]

·         Focus is displayed using only color while tabbing to various controls (including certain cards, buttons, and table data cells)with a keyboard. [MM-8346, MM-8159, MM-1310]

VSS has the following exceptions:

·         Cursor focus is not visible when keyboard users tab to controls on certain pages, including the main navigation menu items in the global header. [MM-8306, MM-1055, MM-1296]

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

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 with known exceptions. 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.

Momentum has the following exceptions:

·         The accessible name, role, value, or property is incorrect and/or missing for some controls within Momentum. [MM-1294, MM-1124, MM-1304, MM-1168, MM-1111, MM-1492, MM-1485, MM-1204, MM-1266, MM-1279, MM-8356, MM-8348, MM-8347, MM-8361, MM-8287, MM-8284, MM-8277, MM-8144, MM-8133, MM-8132, MM-8131, MM-8120, MM-1095, MM-1120, MM-7923, MM-1570, MM-1237, MM-1349]

·         The state of the ‘Tile’ and ‘Grid’ buttons on the Inbox page is only conveyed visually using color. The accessible state for the buttons should reflect this as well. [MM-8142]

·         The selected tab within a tab panel is not semantically defined in the accessible state. [MM-479, MM-1336]

Performance Budgeting has the following exceptions:

·         The user menu in the top right corner of the Momentum banner is missing certain ARIA properties and attributes to ensure it is announced correctly to AT. [MM-801]

·         Some sort buttons associated with data tables in PB are missing the aria-sort property. [MM-8313]

VSS has the following exceptions:

·         The accessible name, role, value, or property is incorrect and/or missing for some controls within VSS. [MM-1152, MM-1326, MM-1225, MM-1241, MM-8124, MM-8311, MM-8315, MM-8324]

·         Fields should be programmatically disabled instead of read-only on the Lines Tab of the Create Referenced Invoice page. [MM-1284]

·         The menus in the Momentum banner are missing certain ARIA properties and attributes to ensure they are announced correctly to AT. [MM-1258, MM-1224]

·         The selected tab within a tab panel is not semantically defined in the accessible state. [MM-1267]

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

The application avoids using 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.

Momentum has the following exceptions:

·         There is insufficient color contrast for some elements within the application and some icons/controls use color alone to convey meaning. [MM-8346, MM-8343, MM-8323, MM-8159, MM-8151, MM-8142, MM-8134, MM-8131, MM-8130, MM-1306, MM-1179, MM-1263, MM-1086, MM-1325, MM-1136, MM-1310]

Performance Budgeting has the following exceptions:

·         There is insufficient color contrast for some controls within the application, including: the Go to top of page button, expand/collapse controls, and the breadcrumb trail. [MM-8147]

VSS has the following exceptions:

·         There is insufficient color contrast for some elements within the application and some icons use color alone to convey meaning. [MM-1210, MM-1187, MM-1172, MM-1160]

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

Momentum has the following exceptions:

·         On some pages form labels are missing or not properly defined. [MM-205, MM-1413, MM-1411, MM-1414, MM-1412, MM-262, MM-310, MM-1084, MM-245, MM-258, MM-234, MM-1282, MM-1265, MM-1202, MM-8067, MM-198, MM-203, MM-230, MM-260, MM-263, MM-282, MM-283, MM-306, MM-295, MM-415, MM-314, MM-8149, MM-8129, MM-1358, MM-6855]

·         Some fields have a form label defined but it is not unique or sufficiently descriptive of the field. [MM-311, MM-1122, MM-1056, MM-1142, MM-1045, MM-1561, MM-8356, MM-8135, MM-8136, MM-1080]

·         Programmatic focus is not set to error and confirmation messages on some pages when they appear. [MM-224, MM-235, MM-279, MM-7962, MM-8126, MM-8280]

·         Some radio buttons are not semantically grouped in a <fieldset> with a <legend>. [MM-211, MM-8221, MM-1090, MM-1250, MM-1528]

·         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. Please note that information related to the required field asterisks is documented in the Accessibility Statement located in Online Help. [MM-1352, MM-1232, MM-1522]

Performance Budgeting has the following exceptions:

·         On some pages form labels are missing or not properly defined. [MM-8201, MM-8263]

·         Some form labels in PB are not unique, including the multiple Add buttons on the same screen that perform different add functions. [MM-8265]

·         Some groups of related form controls are missing fieldset/legend markup. [MM-8222]

VSS has the following exceptions:

·         Some textboxes and other form fields are missing labels. [MM-8303, MM-8336]

·         Focus is not set to the list of errors on some pages. [MM-1288, MM-1093, MM-1076]

·         Some required fields are not properly distinguished, including those on the Vendor Approval screen. [MM-8304]

·         Some labels for form fields are not unique, such as the labels for the multiple Address fields on the Announcements page. [MM-8354, MM-1286]

 


 

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.

Momentum has the following exceptions:

·         Some meaningful icons are coded as CSS background images without a text equivalent. [MM-1569, MM-1553, MM-1545, MM-1527]

·         There is no text equivalent for graphics, images, or link icons on some pages. [MM-1323, MM-8343, MM-8139, MM-8130]

·         Some image/icon buttons are missing a descriptive text equivalent. [MM-8136, MM-8120, MM-1581, MM-1575, MM-1564, MM-1563, MM-1558, MM-1555, MM-1537, MM-1532, MM-1523, MM-1521, MM-1519, MM-1517, MM-1515, MM-1550, MM-4424, MM-1548]

VSS has the following exceptions:

·         Some icons/images are missing a text equivalent. [MM-1514, MM-1520]

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

Momentum has the following exceptions:

·         There is insufficient color contrast for some elements within the application and some icons/controls use color alone to convey meaning. [MM-8346, MM-8343, MM-8323, MM-8159, MM-8151, MM-8142, MM-8134, MM-8131, MM-8130, MM-1306, MM-1179, MM-1263, MM-1086, MM-1325, MM-1136, MM-1310]

Performance Budgeting has the following exceptions:

·         There is insufficient color contrast for some controls within the application, including: the Go to top of page button, expand/collapse controls, and the breadcrumb trail. [MM-8147]

VSS has the following exceptions:

·         There is insufficient color contrast for some elements within the application and some icons use color alone to convey meaning. [MM-1210, MM-1187, MM-1172, MM-1160]

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

Momentum has the following exceptions:

·         There is an incorrect or missing heading structure on some pages. [MM-1182, MM-1355, MM-1244, MM-8342, MM-8292]

·         List markup is missing or incorrect on some pages. [MM-1211, MM-1556, MM-1538, MM-1158, MM-1155, MM-286, MM-8349, MM-8296]

·         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). [MM-1543]

Performance Budgeting has the following exceptions:

·         There are issues with heading structure on some pages within PB. In some cases the headings are out-of-order and in other cases there are multiple <h1> headings when there should only be one. [MM-7921, MM-7922, MM-8194, MM-8197, MM-8258]

·         Some groups of buttons and other related items are not in an unordered list. [MM-810, MM-8137, MM-8365, MM-8366, MM-8367, MM-8368, MM-8369]

VSS has the following exceptions:

·         There are issues with heading structure on some pages within VSS. For example, there are some excess headings defined that are not needed. [MM-8302, MM-8335]

·         Some groups of buttons and other related items are not in an unordered list. [MM-1053, MM-1049]

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

Momentum has the following exceptions:

·         Some data tables are coded with two separate <table> elements in the code but are not patched together properly with ARIA and as a result screen readers do not announce the table contents properly. Also, in some cases, the incorrect ARIA table markup is being used (e.g. there is a role of 'rowheader' instead of role='row'). [MM-480, MM-1533, MM-8358, MM-1576, MM-1339, MM-8156, MM-6137]

·         Some data tables are missing a caption element or aria-labelledby to provide a heading/title for the table. In most cases, there is already text displayed above the table that could be used to provide this caption. [MM-1156, , MM-1490, MM-1094, MM-1097, MM-1344, MM-8301]

·         Some tables contain empty grid cells that should be removed. [MM-293] 

Performance Budgeting has the following exceptions:

·         The ARIA markup defined for the data tables within calendar controls is not implemented correctly. [MM-8228]

·         Some data tables are missing a caption element or aria-labelledby to provide a heading/title for the table. In most cases, there is already text displayed above the table that could be used to provide this caption. [MM-7933]

·         Some tables contain empty grid cells that should be removed. [MM-7932]

VSS has the following exceptions:

·         In some cases, incorrect ARIA table markup is being used (e.g. there is a role of 'rowheader' instead of role='row'). This causes screen software to announce the table incorrectly. [MM-8308, MM-1194]

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

Momentum has the following exception:

·         There are some iFrames missing title and name attributes. [MM-1565]

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

Supports

Adobe Acrobat Reader is the only other application that must be present on the client system to interpret Momentum report content (if Export to PDF is selected). According to the Adobe Acrobat Reader VPAT, Adobe Acrobat Reader sufficiently supports Section 508 Technical Standards 1194.21(a) through (l) with exceptions.

 

Momentum generates downloadable reports in Excel or HTML format. Momentum users must have full version of Excel or download the Excel Viewer (which is known to have Section 508 compliance issues) to view Excel report content (if Export to Excel is selected).

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

Momentum has the following exceptions:

·         On some pages form labels are missing or not properly defined. [MM-205, MM-1413, MM-1411, MM-1414, MM-1412, MM-262, MM-310, MM-1084, MM-245, MM-258, MM-234, MM-1282, MM-1265, MM-1202, MM-8067, MM-198, MM-203, MM-230, MM-260, MM-263, MM-282, MM-283, MM-306, MM-295, MM-415, MM-314, MM-8149, MM-8129, MM-1358, MM-6855]

·         Some fields have a form label defined but it is not unique or sufficiently descriptive of the field. [MM-311, MM-1122, MM-1056, MM-1142, MM-1045, MM-1561, MM-8356, MM-8135, MM-8136, MM-1080]

·         Programmatic focus is not set to error and confirmation messages on some pages when they appear. [MM-224, MM-235, MM-279, MM-7962, MM-8126, MM-8280]

·         Some radio buttons are not semantically grouped in a <fieldset> with a <legend>. [MM-211, MM-8221, MM-1090, MM-1250, MM-1528]

·         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. Please note that information related to the required field asterisks is documented in the Accessibility Statement located in Online Help. [MM-1352, MM-1232, MM-1522]

Performance Budgeting has the following exceptions:

·         On some pages form labels are missing or not properly defined. [MM-8201, MM-8263]

·         Some form labels in PB are not unique, including the multiple Add buttons on the same screen that perform different add functions. [MM-8265]

·         Some groups of related form controls are missing fieldset/legend markup. [MM-8222]

VSS has the following exceptions:

·         Some textboxes and other form fields are missing labels. [MM-8303, MM-8336]

·         Focus is not set to the list of errors on some pages. [MM-1288, MM-1093, MM-1076]

·         Some required fields are not properly distinguished, including those on the Vendor Approval screen. [MM-8304]

·         Some labels for form fields are not unique, such as the labels for the multiple Address fields on the Announcements page. [MM-8354, MM-1286]

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

Supports with Exceptions

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.

Momentum has the following exceptions:

·         The Skip Navigation link does not work correctly or is missing on some pages. [MM-1560, MM-1567, MM-200, MM-1072]

Performance Budgeting has the following exceptions:

·         The Skip Navigation link is broken on some pages because the target is set incorrectly. [MM-788, MM-8275]

VSS has the following exceptions:

·         The Skip Navigation link becomes visible when the keyboard user tabs to it but appears to be cut off based on its placement near the agency logo. [MM-1332]

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

Supports with Exceptions

In Momentum and Performance Budgeting, 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.

However, in VSS the session ends without prompting users to request additional time. [MM-1116]

 

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 18 and  the latest version of NonVisual Desktop Access (NVDA).

Momentum has the following exceptions:

·         Some elements are not announced at all 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. [MM-1335, MM-277, MM-487, MM-1321, MM-1109, MM-1346, MM-1328 , MM-1083, MM-1340, MM-112, MM-1540, MM-1467, MM-1544, MM-1549, MM-8183]

·         Some dynamic actions 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. [MM-1175, MM-1062, MM-1198, MM-1063, MM-1231, MM-1067, MM-1082, MM-8185, MM-8326]

·         Column headers are not sortable on the Inbox page while running JAWS 18 in IE11. [MM-8184]

·         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. [MM-1146, MM-1238, MM-1131, MM-1125, MM-1256, MM-1221, MM-477, MM-475, MM-1117, MM-1186, MM-488, MM-1579]

·         The ARIA role=”presentation” is improperly defined for list items in the main navigation menu and as a result the list markup is suppressed/not announced by the screen reader. [MM-1246]

·         Some links are not unique or meaningful outside of the context of the page. [MM-8157]

·         There are some empty links for the Site Map, Help, Sign Out, and Bookmark links in the header. [MM-371]

·         The HTML language attribute is not defined on some pages. [MM-8164]

Performance Budgeting has the following exceptions:

·         No confirmation is provided after selection of some controls or successful actions (e.g. sending an email from within the FSQ workflow). [MM-837, MM-8157]

·         Some links are not unique or meaningful outside of the context of the page. For example, there are number links (e.g. “500”) in the FSQ workflow. [MM-7936, MM-8163]

·         Some dynamic updates are not announced properly. For example, in the FSQ workflow the incorrect ARIA live region text is announced for some of the data tables. [MM-8117]

·         Programmatic focus is not always managed consistently when a page first loads in PB. [MM-8127]

Selection of a ‘Frequency of Execution’ radio button on the Batch Job Schedule page causes dynamic updates to occur upstream from the user’s place on the page. Because the updates occur upstream, the user may not be aware that they occurred. [MM-8229]

 

VSS has the following exceptions:

·         Some dynamic updates are not announced properly. For example, in the FSQ workflow the incorrect ARIA live region text is announced for some of the data tables. [MM-8310]

·         No confirmation is provided after some successful actions (e.g. selecting the Save button on the Vendor Approval page). [MM-8321]

·         Removed lines are not semantically conveyed on the Lines Tab of the Create Referenced Invoice page. [MM-1068]

·         The JAWS List of Form Fields includes fields that are not displayed visually on the System Settings page [MM-1290]

·         Some page titles are not meaningful. [MM-1189]

·         On some pages table markup is used to position information instead of CSS but the table is missing ARIA role=”presentation”. [MM-1121]

·         There is a “click here” link used on the Announcements page, which does not make sense to screen reader users outside of the context of the page. [MM-8338]

·         The breadcrumb trail does not follow the WAI- ARIA design pattern.  [MM-1176]

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

Momentum has the following exceptions:

·         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, expand/collapse icons are not visible, and font glyphs are missing fallback text. [MM-8150, MM-1568, MM-1557, MM-1554, MM-1545, MM-8118]

Performance Budgeting has the following exceptions:

·         Some tables cannot be scrolled horizontally in IE11 using the keyboard alone when pages are zoomed to 200%. To note: it works for keyboard users in Firefox due to an accessibility feature included in the browser that is not present in IE11. [MM-820]

·         The icon buttons that display for the primary navigation menu disappear when a user-defined style sheet is applied. [MM-8234]

VSS has the following exception:

·         The icon buttons that display for the primary navigation menu disappear when a user-defined style sheet is applied. [MM-8325]

 (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) with known exceptions.

In most cases, 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 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.

Equivalent Facilitation:

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

Momentum has the following exceptions:

·         Some content is not keyboard accessible within Momentum. This includes the following: pagination, sorting, lock/group, and other controls for data tables, menu items, Browse buttons, and the editable table cells on the Contract File page. [MM-319, MM-1360, MM-1491, MM-1531, MM-1584, MM-8140, MM-8120, MM-8139, MM-8277]

·         Focus is not properly set after some actions (e.g. after a modal dialog is opened/closed, after interacting with a menu, etc.) [MM-1096, MM-1365, MM-1341, MM-1139, MM-1115, MM-1147, MM-7704, MM-8360]

·         There is an illogical tab order on some pages within the system. [MM-1566, MM-248, MM-1129, MM-221, MM-1572, MM-2182, MM-4424, MM-4638, MM-4743]

·         Keyboard users are able to tab to non-interactive elements on some pages, such as disabled fields or tables without interactive functionality. [MM-8345, MM-8278, MM-4341]

·         There are unnecessary tab stops on some items within the application. For example, keyboard users typically tab to the first column header within data tables even if it does not contain any interactive elements. [MM-478, MM-563, MM-1541, MM-8285, MM-8144]

·         Table navigation commands are not explained to users on the Line Level Attachments modal dialog. Keyboard users therefore do not know how to edit cells within the table. [MM-8344]

·         There are some custom ARIA controls in Momentum that are keyboard accessible but do not fully follow the keyboard interaction described for the control in the WAI-ARIA Authoring Practices Guide (APG). For example, for some custom menu controls the user can access each menu item via tabbing but the APG indicates that these items should be accessed using the arrow keys. Similarly, there are some modal dialogs that can be closed by activating the “X” close button within the dialog but do not close when the Escape key is pressed. [MM-1354, MM-8359]

·         Cursor focus is not visible when keyboard users tab to controls on certain pages, such as the radio buttons on the Purchase Query – Advanced Search page. [MM-1183]

·         Some list items and table elements are not visible but have tabindex=“0” defined, which places them incorrectly in the tab order. Since these items aren’t visible, the focus indicator disappears when they receive focus, causing keyboard users to not be able to see where their focus is at on the page. [MM-8345, MM-8278]

·         Focus is displayed using only color while tabbing to various controls (including certain cards, buttons, and table data cells) with a keyboard. [MM-8346, MM-8159, MM-1310]

Performance Budgeting has the following exceptions:

·         Some text fields and radio buttons are not keyboard accessible and therefore cannot be populated. For example, the Layout Type field is not keyboard accessible on the Create Generic Budget Request page. [MM-823, MM-7940]

·         The calendar control is not fully keyboard accessible. This prevents the keyboard user from being able to navigate to the previous/next months and fully interact with the control. [MM-8228]

·         Focus is not managed correctly for some pages containing sort functionality. Pressing the Enter key from somewhere on the page can sometimes cause the Sort modal dialog to open unexpectedly. [MM-8257]

·         The tab order is not logical on some pages. For example, keyboard/screen reader users do not encounter fields in the correct order on the Attachment modal dialog. [MM-1516]

·         There are excessive tab stops for the buttons associated with the data table on the Formulated System Query (FSQ) Definition page. [MM-7926]

·         Table navigation commands are not explained to users for the FSQ Definition table. Keyboard users therefore do not know how to edit cells within the table. [MM-8259]

VSS has the following exceptions:

·         Some content is not keyboard accessible on the Create Referenced Invoice page and View Solicitation Orders page. This includes custom dropdown menus and checkboxes as well as the Lock/Group functionality on the tables. [MM-1212, MM-1164, MM-1126, MM-1295]

·         Table navigation commands are not explained to users for the Vendor Approval table. Keyboard users therefore do not know how to edit cells within the table. [MM-8309]

·         Cursor focus is not visible when keyboard users tab to controls on certain pages, including the main navigation menu items in the global header. [MM-8306, MM-1055, MM-1296]

 

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

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.