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: August 22, 2012
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.21
Software Applications and Operating Systems - Detail
Voluntary Product Accessibility Template

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.

   

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

   

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

   

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

   

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

   

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

   

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

   

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

   

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

   

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

   

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

   

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

   
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 and title attributes are provided for all images and input boxes.

 

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

Alt text is provided for active regions of 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.

Alt text is provided for active regions of 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. (<TH> tags with ID attributes, <TD> tags with HEADERS attributes.)

 

(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. (<TH> tags with ID attributes, <TD> tags with HEADERS attributes.)

 

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

The application does not make use of HTML frames. Some areas of the application scroll using <DIV> tags with scrollable overflow attributes to mimic frames, but they are not HTML frames.

 

(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. The application makes use of HTML links to named anchors within its navigation interface to allow users to skip repetitive navigation links. 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). These anchors are placed in logical locations of the interface such that they are among the first elements encountered each time the application screen refreshes. All keyboard shortcuts are listed in the application’s reference manual.   
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. No timed responses are required in the application.