Voluntary Product Accessibility Template

Similar documents
Section Software Applications and Operating Systems - Detail Voluntary Product Accessibility VPSX. Level of Support & Supporting Features

Snap Server Manager Section 508 Report

Summary Table for SolarWinds Web Help Desk

Voluntary Product Accessibility Template Blackboard Learn Release 9.1 April 2014 (Published April 30, 2014)

Summary Table for SolarWinds Web Help Desk

vcenter Operations Manager Administration 5.0 Online Help VPAT

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

Serena Software Voluntary Product Accessibility Report. Summary Table

TRI Oracle Empirica Trace Statement of Conformance

Xerox DocuMate 3125 Document Scanner

Voluntary Product Accessibility Report

SECTION 508 COMPLIANCE

VPAT Voluntary Product Accessibility Template Version 1.3

Supporting Features. Supports with Exceptions. Supports with Exceptions. Supports

Summary Table Voluntary Product Accessibility Template

Health Enterprise Medicaid Management Information System

VPAT. Voluntary Product Accessibility Template. Version 1.3

Nuance PDF Converter Enterprise 8

icohere Products and Section 508 Standards Voluntary Product Accessibility Template (VPAT )

Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

Adobe Flash Player 11.9 Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Adobe Flash Player 11.2 Voluntary Product Accessibility Template

Summary Table. Voluntary Product Accessibility Template

Contact for more Information: or

Voluntary Product Accessibility Template (VPAT)

VPAT Voluntary Product Accessibility Template

Voluntary Product Accessibility Template (VPAT)

Avaya Speech Analytics Desktop Client 2.0

VPAT. Voluntary Product Accessibility Template. Version 1.3

VPAT Summary. VPAT Details. Section Web-based Internet information and applications - Detail

VPAT. Voluntary Product Accessibility Template. Version 1.3

Summary Table Voluntary Product Accessibility Template

Echo360 Voluntary Product Accessibility Template

Wyse Winterm Thin Clients -- Accessibility Information

VPAT. Voluntary Product Accessibility Template. Version 1.3

Voluntary Product Accessibility Template (VPAT) Policy & Information

CDC UNIFIED PROCESS PROCESS GUIDE

Voluntary Product Accessibility Template

Voluntary Product Accessibility

Sony External USB Floppy Disk

Voluntary Product Accessibility Template

Wyse Winterm Thin Clients -- Accessibility Information

Section 508 Compliance - Voluntary Product Accessibility Template (VPAT)

Supporting Features*

Summary Table VPAT Voluntary Product Accessibility Template

Page 1 of 16. VPAT Voluntary Product Accessibility Template. Version 1.0

Section A: CURRICULUM, INSTRUCTIONAL DESIGN AND STUDENT ASSESSMENT

Table of Contents. Provided by the Social Security Administration Section 508 Program

HSU Accessibility Checkpoints Explained

Summary Table Voluntary Product Accessibility Template

not a Web- based application. not self-contained, closed products. Please refer to the attached VPAT Please refer to the attached VPAT

3.3 Web Content Policies and Guidelines

VPAT for Apple MacBook Pro (Late 2013)

WESTERN KENTUCKY UNIVERSITY. Web Accessibility. Objective

Summary Table Voluntary Product Accessibility Template

Apple G5. Standards Subpart Software applications and operating systems. Subpart B -- Technical Standards

Software Application & Operating Systems Checklist

Basics of Accessible Design

Avaya DECT R4 Telephones Models 3720, 3725, 3740, 3745 and 3749

Accessibility. Accessibility. Web sites should be designed to ensure that

VPAT 1 Product: Call Center Hearing Aid Compatible (HAC) Headsets Operated with Amplifier Models M12, MX10, P10, or SQD:

VPAT for Apple ipad Air 2

SRCSB General Web Development Policy Guidelines Jun. 2010

Summary Table Voluntary Product Accessibility Template

IP Office Contact Center R9.0 Interactive Voice Response Voluntary Product Accessibility Template (VPAT)

Summary Table Voluntary Product Accessibility Template. Criteria Supporting Features Remarks and explanations

WCAG 2 Compliance With Flash

Avaya Model 9608 H.323 Deskphone

Website Accessibility Under Title II of the ADA

Summary Table Voluntary Product Accessibility Template

Summary Table Voluntary Product Accessibility Template

Summary Table Voluntary Product Accessibility Template

( t- ""'J'''YICES'OS~

Creating Accessible Web Content with Dreamweaver

WCAG 2.0 Checklist. Perceivable Web content is made available to the senses - sight, hearing, and/or touch. Recommendations

WCAG 2.0 Checklist (Detailed)

How to Develop Accessible Linux Applications

Summary Table Voluntary Product Accessibility Template. Not Applicable- Not a web-based application. Supports. Not Applicable

Avaya 9600 Series IP Telephones Voluntary Product Accessibility Template (VPAT)

Avaya Model 2410 and 2420 Digital Telephones Voluntary Product Accessibility Template (VPAT)

Federal Aviation Administration. Enterprise BPMS Requirements. Version 1.7

Creating and Maintaining Accessible Websites with SiteCM

PDF Accessibility Overview

How To Use A Web Page With A Wheelchair On A Pc Or Mac Or Mac (For Seniors)

Developing accessible portals and portlets with IBM WebSphere Portal

Blackboard Web Community Manager WCAG 2.0 Support Statement February 2016

Easy Guide to Building No Barrier Web Sites

Web Content Accessibility Guidelines 2.0 Checklist

Avaya Model 1408 Digital Deskphone

SAS/GRAPH Network Visualization Workshop 2.1

July 2012 Version 1.0. Section 508 Compliance Test Process for Microsoft Word Documents

February 2014 Version 3.3. DHS Section 508 Compliance Test Process for Applications

Using Parasoft SOAtest to Verify Section 508 and WAI WCAG Web Accessibility Requirements

Universal Design and Ethical Practices for Designing. Bryan Ayres, M.Ed., ATP, Director Technology & Curriculum Access Center Easter Seals Arkansas

Web Accessibility Tools: InFocus & LIFT for DreamWeaver

Web Accessibility Report

Accessibility-MiVoice-Business.docx Page 1

Adobe Conversion Settings in Word. Section 508: Why comply?

Transcription:

Date: April 25, 2014 Product Name: BI Office Version 5.2 Vendor Company Name: Pyramid Analytics Vendor Contact Name: Peter Sprague (peter@pyramidanalytics.com)

Summary Table Explanations Section 1194.21 Software Applications and Operating Systems with See Detailed Comments Below and Accessibility Statement Section 1194.22 Web-based Internet Information and Applications with through Equivalent Facilitation See Detailed Comments Below and Accessibility Statement 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 Section 1194.41 Information, Documentation and Support Page 2 of 9

Section 1194.21 Software Applications and Operating Systems - Detail (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. with with with with Explanations Some keyboard only functionality exists, but not entirely supported. Won t disrupt features outside of sandbox, but will ignores accessibility settings outside of sandbox. The client application can create accessible output. Creation of accessible content limited by mouse only navigation. Client analyst can configure accessible output upon request. No defined on-screen indication of the current focus. However, wizards have cursors and current focus and are keyboard accessible. Visualization feature provides alternate grid to provide identity, operation and state of the element for AT. Allows end-user to alternate between visualization and grid. Page 3 of 9

(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. Supported consistent use of images used as status indicators/elements. Does not use operating system to display text. But font, color and size can be set by end user for display of data output. Won t disrupt features outside of sandbox, but will ignores accessibility settings outside of sandbox. The client application can create accessible output. Client analyst can configure accessible output upon request. No data or information is conveyed by animation. Purely decorative and can be disabled. End user can choose to use contextual highlighting. User configurable. all colors. Status indicator present for Report Publication Tool. Fades in and out less than 2 Hz. Doesn t blink. Search box and Wizard text fields not accessible. Page 4 of 9

Section 1194.22 Web-based Internet information and applications - Detail (a) A text equivalent for every nontext element shall be provided (e.g., via "alt", "longdesc", or in element content). (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. (d) Documents shall be organized so they are readable without requiring an associated style sheet. (e) Redundant text links shall be provided for each active region of a server-side image map. (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. (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 (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Support w/ through Equivalent Facilitation Explanations Visualizations are dynamic SVG images and does not allow for alt text. No Multimedia present. Color used to denote information in visualizations. However, end-user can build a view compliant with this provision. Row and column headers are identified in both HTML and non-html client. Row and column headers are identified in all export formats. Status indicator present for Report Publication Tool. Fades in and out less than 2 Hz. Doesn t blink. Page 5 of 9

(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. (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). (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. (o) A method shall be provided that permits users to skip repetitive navigation links. (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. through Equivalent Facilitation with Not applicable The client application can create accessible output in Excel and PDF file formats. Application security features requires scripts to be enabled. Plugins for MS Silverlight provided. Plugin for Adobe Reader needs to be added. This is a hybrid application that is client hosted, but viewed through a browser. Not typical web application environment in which to deploy a Skip Nav. No timed responses present. Page 6 of 9

Section 1194.31 Functional Performance Detail (a) At least one mode of operation not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided. (b) At least one mode of operation 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. (c) At least one mode of operation 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 (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. (e) At least one mode of operation 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 not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. through Equivalent Facilitation through Equivalent Facilitation with explanations Export to PDF or Excel available for alternate viewing with Assistive Technology. All information can be presented as a grid with a configurable font, color and point size. Use of a mouse required to create the data visualizations. Can export reports via email in accessible Excel or PDF formats. Page 7 of 9

Section 1194.41 Information, Documentation and Support Detail (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge (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 end-users with disabilities. explanations Documentation in 508 compliant HTML available. Accessibility Statement will be posted online with detailed information about accessibility features and limitations of this application. TTY compatible support available. Page 8 of 9

APPENDIX A Suggested Language for Filling out the VPAT In order to simplify the task of conducting market research assessments for procurement officials or customers, ITIC (Information Technology Industry Council) has developed suggested language for use when filling out a VPAT. You may choose to employ all or some of the language below. Once you determine what language you intend to use, we recommend that use is consistent throughout all of your VPATs. Use this language when you determine the product fully meets the letter and intent of the. with Use this language when you determine the product does not fully meet the letter and intent of the, but provides some level of access relative to the. through Equivalent Facilitation Use this language when you have identified an alternate way to meet the intent of the or when the product does not fully meet the intent of the. when combined with Compatible AT Use this language when you determine the product fully meets the letter and intent of the when used in combination with Compatible AT. For example, many software programs can provide speech output when combined with a compatible screen reader (commonly used assistive technology for people who are blind). Does not Support Use this language when you determine the product does not meet the letter or intent of the. Use this language when you determine that the do not apply to the specific product. - Fundamental Alteration Exception Applies Use this language when you determine a Fundamental Alteration of the product would be required to meet the (see the access board standards for the definition of "fundamental alteration"). Page 9 of 9