Generic
  

Xacta IA Manager Voluntary Product Accessibility Template

The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding the availability of commercial Electronic and Information Technology products and services with features that support accessibility. It is assumed that offerers will provide additional contact information to facilitate more detailed inquiries.

The first table of the Template provides a summary view of the section 508 Standards. The subsequent tables provide more detailed views of each subsection. There are three columns in each table.

Column one of the Summary Table describes the subsections of subparts B and C of the Standards. The second column describes the supporting features of the product or refers you to the corresponding detailed table, "e.g., equivalent facilitation." The third column contains any additional remarks and explanations regarding the product. In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product.

Date: November 12, 2014
Name of Product: Xacta IA Manager (formerly Xacta Web C&A)

Summary Table
Voluntary Product Accessibility Template

Criteria Supporting Features Remarks and explanations
Section 1194.21 Software Applications and Operating Systems     
Section 1194.22 Web-based internet information and applications  This subsection applies to Xacta IA Manager (formerly Xacta Web C&A).
Section 1194.23 Telecommunications Products   
Section 1194.24 Video and Multi-media Products   
Section 1194.25 Self-Contained, Closed Products   
Section 1194.26 Desktop and Portable Computers   
Section 1194.31 Functional Performance Criteria   

Section 1194.22

  Web-based Internet information and applications - Detail
  Voluntary Product Accessibility Template

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).Alt or title attributes are provided for images. If an image is purely decorative, the alt attribute is blank, as required by accessibility guidelines. Charts and graphs also include alt or title attributes describing their data, or they are accompanied by a textual legend.  
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.No multi-media (video, sound, animation, etc.) presentations are used in the application. 
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.All graphics using color to indicate different states (such as grayed-out buttons and active/inactive icons) have dynamic alt and title attributes that indicate their state. For example, the alt for a Save button reads “Save”, while the alt for a grayed-out button reads “Save Disabled”.  
(d) Documents shall be organized so they are readable without requiring an associated style sheet.The application uses an external style sheet, in which style rules are set up in a separate file. The application is readable without a style sheet. 
(e) Redundant text links shall be provided for each active region of a server-side image map.The application does not use server-side image maps. 
(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.The application does not use server-side image maps. 
(g) Row and column headers shall be identified for data tables.The application uses 508 compliant HTML techniques to cross-index row and column headers. Table header cells are assigned unique IDs, and their associated table cells use the HTML “headers” attribute to match them to the 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.The application uses 508 compliant HTML techniques to cross-index row and column headers. Table header cells are assigned unique IDs, and their associated table cells use the HTML “headers” attribute to match them to the headers.  
(i) Frames shall be titled with text that facilitates frame identification and navigationThe application does not make use of HTML frames.          Version 4.0 uses HTML “div” tags with CSS overflow techniques to create scrollable frame-like areas that do not require frame identification. To assistive technology they appear as seamless parts of a single, whole page. 
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.The application does not cause the screen to flicker. 
(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.The application is designed to follow 508 standards and to use only those interface techniques which are accessible, so that no alternative text-only pages are required.  
(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.Interface elements created by scripting languages are displayed using standard HTML accompanied by 508 compliant techniques wherever applicable, such as labels, alts, titles, and summary attributes, to facilitate screen reading technology. 
(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). No plug-ins are required. Some reference information, as well as the final published document generated by the application are created in .pdf format and require Adobe Acrobat Reader 5.0, which is a listed requirement of the software. A link to download Acrobat Reader is provided in the Resource page. 
(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.Form fields are readily accessed and make use of the <LABEL> tag. Inputs also have alt attributes which describe them. Form elements can be navigated to and interacted with using the keyboard. 
(o) A method shall be provided that permits users to skip repetitive navigation links. Named anchors and keyboard shortcuts are employed to facilitate skipping repetitive navigation. Links to named anchors within the main sections of the application precede the primary navigation elements and are among the very first elements to be described by screen readers when each page loads. Keyboard shortcuts are provided to easily jump to each named anchor and thus to each main navigation section of the application (top banner area, left navigation bar, main content area, top and bottom links). In addition, common interface elements such as Save, Reset, Cancel, Login, Logoff, Project List, Work Product List, and Preferences each have a unique keyboard shortcut assigned to them. All keyboard shortcuts are listed in the User’s Guide (provided in .pdf format) in the disability shortcuts appendix          

Continuum also includes WAI-ARIA navigation and landmark roles to designate and allow quick access to the following main sections: Banner (role=”banner”), primary navigation links (role=”navigation”), sidebar/left navigation bar (role=”navigation”), main application area (role=”main” and role=”application”). These landmarks are recognizable by many screen readers and allow users to skip repetitive navigation elements and jump directly to the desired area.

 
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.The application notifies users when they are about to be logged off due to long periods of inactivity. The same       notification popup provides a button which can be clicked to allow the user to stay logged in.