VPAT for IBM Endpoint Manager 9.1. VPAT Summary. VPAT Details. Section Software Applications and Operating Systems - Detail

Similar documents
For a detailed description of the parent features and benefits, please refer to the following URL:

For a detailed description of the parent features and benefits, please refer to the following URL:

Lectora 508 Compliance Document

Section Software Applications and Operating Systems - Detail

Rapid7 Nexpose: Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Summary Table for SolarWinds MFT Server

Adobe Experience Manager (AEM) 6.2 Forms - Output Voluntary Product Accessibility Template

Criteria Supporting Features Remarks and explanations Section Software Applications and Operating Systems. possible exceptions

Section 508 Evaluation Template

Section Software Applications and Operating Systems - Detail Voluntary Product Accessibility PageCenterX

Adobe Acrobat.com Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

Adobe LiveCycle Correspondence Management ES4 Voluntary Product Accessibility Template

VPAT Voluntary Product Accessibility Template. Summary Table

Adobe Experience Manager (AEM) 6.2 Forms Workbench Voluntary Product Accessibility Template

Blackboard Collaborate Voice Authoring. Voluntary Product Accessibility Template (VPAT)

Voluntary Product Accessibility Template

Adobe LiveCycle Reader Extensions ES3 Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

Voluntary Product Accessibility Template (VPAT )

Adobe Experience Manager (AEM) 6.2 Forms - Digital Signatures Voluntary Product Accessibility Template

Adobe Bridge CS5.1 Voluntary Product Accessibility Template

Adobe Business Catalyst Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

Adobe LiveCycle Digital Signatures ES3 Voluntary Product Accessibility Template

VPAT. Event Log Management v10 Accessibility. Version 1.3 of the VPAT Template

Adobe Experience Manager (AEM) 6.2 Forms - Reader Extensions Voluntary Product Accessibility

Wimba Voice VPAT. Date: March 25, 2008 Name of Product: Wimba Voice Tools version Contact for more Information:

Adobe Digital Publishing Solution for Windows Voluntary Product Accessibility Template

Note: This document describes normal operational functionality. It does not include maintenance and troubleshooting procedures.

VPAT. Voluntary Product Accessibility Template. Version 1.3. Summary Table VPAT. Voluntary Product Accessibility Template. Supporting Features

It should be noted that this document describes administrative access to Content Sharing Suite via the Web Admin UI.

Exhibit A. Voluntary Product Assessment Template SUMMARY TABLE. Section Software Applications and Operating Systems Applicable Partial Support

Adobe Story CC Plus Voluntary Product Accessibility Template

Adobe Experience Manager (AEM) 6.2 Forms - Server Administration Voluntary Product Accessibility Template

Summary Table Voluntary Product Accessibility Template

Schoology Voluntary Product Accessibility Template (VPAT)

Adobe Omniture Discover Voluntary Product Accessibility Template

Adobe LiveCycle Server Administration ES3 Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

Voluntary Product Accessibility Template (VPAT )

Adobe FrameMaker 12 Voluntary Product Accessibility Template

Adobe LiveCycle Rights Management ES3 Voluntary Product Accessibility Template

1.3 Wireless LAN Manager The Voluntary Product Accessibility Template for Aruba Networks Wireless LAN Manager Solution follows:

Adobe FormsCentral (Desktop Application) Voluntary Product Accessibility Template

Adobe CQ5.4 Voluntary Product Accessibility Template

VPAT Voluntary Product Accessibility Template. Version 1.3

Axway Voluntary Product Accessibility Template (VPAT)

Adobe Contribute 6.5 Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Google Forms. Summary Table. Date: 11/2014 Name of Product: Google Forms Point of Contact: Richard Wu. Criteria Supporting features Remarks

IP Office Contact Center 10.X Wallboard Voluntary Product Accessibility Template (VPAT)

1.2 Wireless Access Point

Note: This document describes normal operational functionality. It does not include maintenance and troubleshooting procedures.

VPAT for VMware vcloud Networking and Security 5.1

Adobe Dreamweaver CC Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

VMware vsphere Web Client 6.5 VPAT

Voluntary Product Accessibility Template

Adobe EchoSign Voluntary Product Accessibility Template

Science. Voluntary Product Accessibility Template: Section 508

Fusion 4 General Help VPAT

VOLUNTARY PRODUCT ACCESSIBILITY TEMPLATE (VPAT)

Voluntary Product Accessibility Template PowerBroker Identity Services

Voluntary Product Accessibility Template (VPAT )

Salesforce Lightning App Builder

VMware vsphere Update Manager 6.0 VPAT

VPAT FOR WINDCHILL 11.X

Section 508 Compliance (VPAT)

Adobe Bridge CS6 Voluntary Product Accessibility Template

SecurityCenter 508 Compliance

VMware vcenter Orchestrator 5.5 VPAT

Section Software Applications and Operating Systems Web Conferencing Service (WCS) Detail Voluntary Product Accessibility Template

VMware Virtual SAN with vsan Health Check Plugin 6.0 VPAT

Adobe Illustrator CC Voluntary Product Accessibility Template

Summary Table Voluntary Product Accessibility Template

VMware vcenter Site Recovery Manager 6.1 VPAT

VPAT Section 508 Voluntary Product Accessibility Template

Voluntary Product Accessibility Template (VPAT)

Voluntary Product Accessibility Template

Adobe RoboHelp 9 Voluntary Product Accessibility Template

Embarcadero Rapid SQL

VPAT Voluntary Product Accessibility Template Version 1.4

Adobe FrameMaker (2015 Release) Voluntary Product Accessibility Template

Adobe Illustrator CS5.1 Voluntary Product Accessibility Template

Adobe Fireworks CS6 Voluntary Product Accessibility Template

Voluntary Product Accessibility Template (VPAT)

Teamcenter Voluntary Product Accessibility Template. Summary Table Voluntary Product Accessibility Template

Voluntary Product Accessibility Template Retina Network Security Scanner

VPAT for View 5.1 Server

IP Office Contact Center R9.0 Supervisor User Interface Voluntary Product Accessibility Template (VPAT)

VPAT. Voluntary Product Accessibility Template. Version 1.3 *

Voluntary Product Accessibility Template PowerBroker for Mac

Voluntary Product Accessibility. Retina CS Enterprise Vulnerability Management

Supporting Features. 1.) All control features of Dragon Naturally Speaking 9 are Compliant. 2.) Dragon Tutorial is Compliant

VPAT (Voluntary Product Accessibility Template)

Adobe Campaign (15.12) Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Networx Universal. Supporting Features. Remarks and explanations. Criteria

Transcription:

06/19/2015 05:00:53 EDT Cal State Fullerton (CSUF) VPAT for IBM Endpoint Manager 9.1 VPAT comments: For a detailed description of the parent features and benefits, please refer to the following URL: http://www.ibm.com/software/tivoli/solutions/endpoint-manager/#features This VPAT applies to these offerings of IBM Endpoint Manager 9.1, not all offerings will contain all the features: IBM Endpoint Manager for Lifecycle Management v9.1, PID 5725C43 IBM Endpoint Manager for Security and Compliance v9.1, PID 5725C44 IBM Endpoint Manager for Patch Management v9.1, PID 5725C45 IBM Endpoint Manager for Power Management v9.1, PID 5725C46 IBM Endpoint Manager for Core Protection v9.1, PID 5725D25 IBM Endpoint Manager for Software Use Analysis v9.1, PID 5725F57 IBM Endpoint Manager for Mobile Devices v9.1, PID 5725F99 IBM Endpoint Manager for Server Automation v9.1, PID 5725H27 IBM Endpoint Manager for Datacenters v9.1, PID 5725Q67 VPAT Summary Criteria Status Remarks and Explanations Section 1194.21 Software Applications and Operating Systems Section 1194.22 Web-based Internet information & applications 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 Refer to Section 1194.21 in VPAT Details section below. Refer to Section 1194.22 in VPAT Details section below. Section 1194.31 Functional Performance Criteria Refer to Section 1194.31 in VPAT Details section below. Section 1194.41 Information, Documentation, and Support Refer to Section 1194.41 in VPAT Details section below. VPAT Details Section 1194.21 Software Applications and Operating Systems - Detail Criteria Supporting Features Remarks and Explanations (a) When software is designed to run on a system Does not support 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. While keyboard equivalents are available for some actions, focus issues cause problems tabbing, selecting and navigating throughout the dashboard panels, which in turn creates problems with screen reader JAWS reading labels and data. (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 - IBM Endpoint Manager 9.1: - IBM Endpoint Manager for Server Automation 9.1 - Keyboard equivalents are available for actions, however the focus goes to the show recently run actions combo box displayed in the Progress tab instead of reading the tab name Progress. But when the focus is on the search edit box and on using shift tab, offers label is read by screen reader JAWS. : Analytics - Keyboard accessibility

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. features built into the operating system are not interfered with. The left-hand console navigation, which is part of the main platform, does not properly handle focus with tab, shift-tab., creating navigation and screen reader JAWS reading issues. : Analytics (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. - A visual focus indicator that moves among interactive objects as the input focus changes is available. The left-hand console navigation, which is part of the main platform, does not properly handle focus with tab, shift-tab., creating navigation and screen reader JAWS reading issues. (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. : Analytics The following components meet this Semantic information on user interface objects is provided. Controls, objects, icons and images have a consistent associated label. The following components meet this criterion with - While Images are not used to represent program elements, Semantic information is provided about user interface objects. At Offers tab and Progress tab, list view's the columns (Title, Category, Status) is indicated with an 'arrow', on selecting it the offers get filtered. There is no label/instruction associated with this option and also screen reader JAWS does not read it. screen reader screen reader JAWS: List control headers are not being read by screen reader JAWS. : Analytics - Semantic information on user interface objects is provided.

Associated labels with controls, objects, icons and images used to identify programmatic elements, are consistent throughout the application, except for charts are graphic only. Semantic information on user interface objects is not always provided. Controls, objects, icons and images do not have a consistent associated label. (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. The following components meet this Controls, objects, icons and images have a consistent associated label. The following components meet this criterion with - At Offers tab and Progress tab, list view's the columns (Title, Category, Status) is indicated with an 'arrow', on selecting it the offers get filtered. There is no label/instruction associated with this option and also screen reader JAWS does not read it. screen reader screen reader JAWS: List control headers are not being read by screen reader JAWS. : Analytics - Associated labels with controls, objects, icons and images used to identify programmatic elements, are consistent throughout the application, except for charts are graphic only. Labels are not associate with controls, objects, icons and images throughout the application. (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. The following components meet this Text is provided through standard system function calls or through an API (application programming interface) which supports interaction with assistive technology. : Analytics

- Text through standard system function calls to support interaction with assistive technology is not provided at this time. - Text is not provided through standard system function calls or through an API (application programming interface) which supports interaction with assistive technology. - Text is not provided through standard system function calls or through an API (application programming interface) which supports interaction with assistive technology. (g) Applications shall not override user selected contrast and color selections and other individual display attributes. The following components meet this System settings for high contrast for user interface controls and client area content are supported. System settings for font, size, and color for user interface controls are inherited. The following components meet this criterion with - System settings for font, size, and color for user interface controls are inherited. System settings for high contrast for user interface controls and client area content are supported, but accessibility testing has not been performed. - System settings for high contrast for user interface controls and client area content are supported. Scrolling option is not provided when the font size is changed, due to this on Progress tab on selecting any Title/offer, in the resulting window 'OK' button was not visible. Screen reader JAWS: scrolling option is not provided when the font size is changed : Analytics - System settings for font, size, and color for user interface controls are inherited. System settings for high contrast for user interface controls and client area content is not supported at this time. (h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. - High contrast does not affect the Flex based dashboards. Flex based dashboards are unaffected by system font changes - System settings for high contrast for user interface controls and client area content are not supported. System settings for font, size, and color for all user interface controls are not inherited. Animation is not used.

: Analytics (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. The following components meet this Color is not used as an enhancement nor as a way to convey information or indicate an action. : Analytics (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. Supports: The use of blinking text, objects or elements has been avoided, reducing risk of seizures for users with photosensitive epilepsy. Does not support - IBM Endpoint Manager - Many charts use color as an enhancement or as a way to convey information or indicate an action. - Color is used as an enhancement and not as a way to convey information or indicate an action, but the accessibility testing has not been performed. Color customization is not supported. : Analytics The following components meet this Flashing or blinking text or objects are not used. : Analytics Not all forms allow people using assistive technology to access the information adequately.

: Analytics The following component does not apply to this - Application does not use electronic forms. Section 1194.22 Web-based Internet information and applications - Detail 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). - Non-text content that is presented to the user has a text alternative that serves the equivalent purpose. (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. - Text alternatives are not supported at this time. - Text alternatives are included in development, but accessibility testing has not been performed. No multimedia audio or video content is used. - Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (d) Documents shall be organized so they are readable without requiring an associated style sheet. - Color is used to distinguish a visual element, but accessibility testing has not been performed. Color is not used as the only visual means of conveying information, but accessibility testing has not been performed. - Disabled style sheets via view, page style, no style, and verify that functions are working.

- Ability to read web pages without style sheets is not supported at this time. - Development complete so that web pages are readable without requiring style sheets, but accessibility testing has not been performed. (e) Redundant text links shall be provided for each active region of a server-side image map. No image maps are used. (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. (g) Row and column headers shall be identified for data tables. Does not support No image maps are used. (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. (i) Frames shall be titled with text that facilitates frame identification and navigation. Does not support - Table cells and relationships between cells can not be programmatically determined. User needs to be able to associate data with a specific row or header, this isn't possible, for instance with Software Installation table. - Table cells and relationships between cells can not be programmatically determined at this time. - Development complete so that table cells and relationships between cells can be programmatically determined at this time, but accessibility testing has not been performed. - Table cells and relationships between cells can not be programmatically determined. User needs to be able to associate data with a specific row or header, this isn't possible, for instance with Software Installation table. - Table cells and relationships between cells can not be programmatically determined at this time. - Development complete so that table cells and relationships between cells can be programmatically determined at this time, but accessibility testing has not been performed. - A title and an accessible frame source are provided for each frame, provided in title bar.

- A title and an accessible frame source is not provided at this time. - A title and an accessible frame source are provided for each frame, but accessibility testing has not been performed. (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. (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. (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 use of blinking text, objects or elements has been avoided, reducing risk of seizures for users with photosensitive epilepsy. Supports: Alternatives to scripting language are provided, allowing users access to the content via keyboard and assistive technology. The following components meet this There is no Flashing Content. Does not provide a text only page. - Scripts are keyboard accessible. Expandable/hierarchical entries are accomplished with 'enter' key. No scripts are used. (m) When a web page requires that an applet, plugin 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). (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. No Applets, plug-ins, or non-html content. The following components meet this Form element labels can be programmatically determined. The following component does not meet this (o) A method shall be provided that permits users to skip repetitive navigation links. - Development complete so that form element labels can be programmatically determined, but accessibility testing has not been performed. - Methods are provided for skipping over navigation links to get to main content of page. Home, Reports, Management, Administrator links provide navigation.

- Method to skip to main content is not supported at this time. - Method to skip to main content are provided, but accessibility testing has not been performed. (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. No time response content. Section 1194.31 Functional Performance - Detail 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 exception: See the following for supporting features: - 1194.21 a, b, c, d, e, f, h, i, l - 1194.22 all The following components meet this criterion with - Client UI : Analytics (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 what are visually impaired shall be provided. Supports with exception: See the following for supporting features: - 1194.21 c, g, i, j, l - 1194.22 n The following components meet this The following components meet this criterion with - Client UI : Analytics

(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. Does not support: See the following for supporting features: - 1194.22 b, m The following component does not meet this (d) Where audio information is important for the use of the 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. (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. (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 exception: See the following for supporting features: - 1194.21 a, b - 1194.22 l, p - Client UI : Analytics - Client UI : Analytics - Scripts are keyboard accessible. Expandable/hierarchical entries are accomplished with 'enter' key. The following component meets this criterion with - Client UI

: Analytics Section 1194.41 Information, Documentation, and Support - Detail Criteria Supporting Features Remarks and Explanations (a) Product support documentation provided to endusers shall be made available in alternate formats upon request, at no additional charge. Supports with exceptio The following component meets this criterion with - Product Family Documentation - Text alternatives have been included for non-text content. Row and column headers are used to identify relationships between cells. Color is not used to convey information. Web pages do not contain anything that flashes more than three times in any one second period. Headings, sections, URL links, and a table of contents is used to provide navigation, but accessibility testing has not been performed. There are no image maps, time-based media or prerecorded video, live multimedia, Form elements, are not used in documentation. Style sheets are not used, scripts. No scripts or applets, plug-ins, or non- HTML content. No time limits. (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. (c) Support services for products shall accommodate the communication needs of endusers with disabilities. Does not support Supports: In addition to standard IBM help desk and support Web sites, IBM has established a TTY telephone service for use by deaf or hard of hearing customers to access sales and support services. The following component does not meet this - Product Family Documentation - Documentation on all accessibility features including keyboard access is not available. Disclaimer IBM provides this data for general information on an AS IS basis. For formal representations on particular proposals, please contact an IBM Client Representative or call the IBM Federal Information Call Center at 1-800-333-6705 or TTY: 1-800-IBM-3383. Any third-party components or technologies not developed by or licensed by IBM that may be packaged with or engaged by the use of this product are not included in this Section 508 assessment. Online Information Centers have been replaced by the IBM Knowledge Center - Hosted Edition service. To request the current accessibility status for the IBM Knowledge Center - Hosted Edition service, visit the IBM Product Accessibility information web page (https://www- 03.ibm.com/research/accessibility/requests/accvpat.nsf/bidxjs?OpenForm) and select the entry for IBM Knowledge Center - Hosted Edition.