or Summary Table Voluntary Product Accessibility Template

Similar documents
Snap Server Manager Section 508 Report

Summary Table for SolarWinds Web Help Desk

Summary Table for SolarWinds Web Help Desk

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

Xerox DocuMate 3125 Document Scanner

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

Voluntary Product Accessibility Report

vcenter Operations Manager Administration 5.0 Online Help VPAT

Contact for more Information: or

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

TRI Oracle Empirica Trace Statement of Conformance

Summary Table Voluntary Product Accessibility Template

Nuance PDF Converter Enterprise 8

SECTION 508 COMPLIANCE

Voluntary Product Accessibility Template

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

Summary Table. Voluntary Product Accessibility Template

Serena Software Voluntary Product Accessibility Report. Summary Table

VPAT. Voluntary Product Accessibility Template. Version 1.3

Voluntary Product Accessibility Template

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

VPAT. Voluntary Product Accessibility Template. Version 1.3

VPAT Voluntary Product Accessibility Template

VPAT Voluntary Product Accessibility Template Version 1.3

Health Enterprise Medicaid Management Information System

VPAT. Voluntary Product Accessibility Template. Version 1.3

Avaya Speech Analytics Desktop Client 2.0

Adobe Flash Player 11.9 Voluntary Product Accessibility Template

Adobe Flash Player 11.2 Voluntary Product Accessibility Template

Summary Table Voluntary Product Accessibility Template

Voluntary Product Accessibility Template (VPAT)

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

VPAT. Voluntary Product Accessibility Template. Version 1.3

VPAT. Voluntary Product Accessibility Template. Version 1.3

Wyse Winterm Thin Clients -- Accessibility Information

Voluntary Product Accessibility Template (VPAT) Policy & Information

Sony External USB Floppy Disk

Voluntary Product Accessibility Template (VPAT)

Wyse Winterm Thin Clients -- Accessibility Information

Voluntary Product Accessibility

Echo360 Voluntary Product Accessibility Template

CDC UNIFIED PROCESS PROCESS GUIDE

Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

Supporting Features*

Section 508 Compliance - Voluntary Product Accessibility Template (VPAT)

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

Summary Table VPAT Voluntary Product Accessibility Template

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

Summary Table Voluntary Product Accessibility Template

Software Application & Operating Systems Checklist

VPAT for Apple MacBook Pro (Late 2013)

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

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

Summary Table Voluntary Product Accessibility Template

Section A: CURRICULUM, INSTRUCTIONAL DESIGN AND STUDENT ASSESSMENT

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

VPAT for Apple ipad Air 2

HSU Accessibility Checkpoints Explained

Avaya Model 9608 H.323 Deskphone

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

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

SRCSB General Web Development Policy Guidelines Jun. 2010

Summary Table Voluntary Product Accessibility Template

Summary Table Voluntary Product Accessibility Template

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

WCAG 2.0 Checklist (Detailed)

Summary Table Voluntary Product Accessibility Template

3.3 Web Content Policies and Guidelines

How to Develop Accessible Linux Applications

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

PDF Accessibility Overview

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

Avaya Model 1408 Digital Deskphone

SAS/GRAPH Network Visualization Workshop 2.1

Website Accessibility Under Title II of the ADA

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

WESTERN KENTUCKY UNIVERSITY. Web Accessibility. Objective

Web Content Accessibility Guidelines 2.0 Checklist

Creating Accessible Web Content with Dreamweaver

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

Basics of Accessible Design

Microsoft Migrating to PowerPoint 2010 from PowerPoint 2003

MiniView Micro USB Plus 2-Port KVM Switch with Built-in KVM Cables and Audio Support. Installation Manual (GCS632U)

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

Accessibility-MiVoice-Business.docx Page 1

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

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

Migrating to Excel 2010 from Excel Excel - Microsoft Office 1 of 1

Creating and Maintaining Accessible Websites with SiteCM

Intelledox Designer WCA G 2.0

Asset Track Getting Started Guide. An Introduction to Asset Track

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

Microsoft PowerPoint 2010

Blackboard Web Community Manager WCAG 2.0 Support Statement February 2016

Acrobat X Pro Accessible Forms and Interactive Documents

Developing accessible portals and portlets with IBM WebSphere Portal

Hands-On Lab: WSUS. Lab Manual Expediting WSUS Service for XP Embedded OS

Microsoft PowerPoint Tutorial

Transcription:

Date: 11/14/2007 Name of Product: Microsoft Visual Studio Team System 2008 Team Foundation Server Microsoft Visual Studio Team System 2008 Team Suite Microsoft Visual Studio Team System 2008 Architecture Edition Microsoft Visual Studio Team System 2008 Development Edition Microsoft Visual Studio Team System 2008 Test Edition Microsoft Visual Studio Team System 2008 Database Edition Microsoft Visual Studio Team System 2008 Load Agent Microsoft Visual Studio 2008 Professional Edition Microsoft Visual Studio 2008 Standard Edition For more Information: http://msdn.microsoft.com/vstudio or http://www.microsoft.com/enable Summary Table Voluntary Product Accessibility Template Criteria Supporting Features Remarks and explanations Section 1194.21 Software Applications Supported. Please refer to the attached VPAT and Operating Systems Accessibility Section 1194.22 Web Accessibility Supported. Please refer to the attached VPAT Visual Studio 2008 is not primarily considered a Web-based internet information and applications product. Visual Studio 2008 is used, however, to build Web-based and other types of applications. Section 1194.23 Telecommunications Products Visual Studio 2008 is not considered a telecommunications product. Section 1194.24 Video and Multi-media Products Visual Studio 2008 is not a multimedia product. Section 1194.25 Self-Contained, Closed Products Visual Studio 2008 is not a self-contained product. Section 1194.26 Desktop and Portable Computers Visual Studio 2008 is not a desktop or portable computer. Section 1194.31 Functional Performance Supported. Please refer to the attached VPAT Criteria Section 1194.41 (a) Information, Documentation and Support Supported. Please refer to the attached VPAT

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. Visual Studio 2008 includes support for accessing almost all functions using only the keyboard with minor exceptions. Supported with exceptions: Visual Studio 2008 enables individuals to customize their desktop elements, including resizing and rearranging toolbars and menus, choosing color, size, sound, and format options. Visual Studio 2008 supports large fonts in the title bar, toolbars and most dialogs. It fully supports operating system accessibility features including StickyKeys, FilterKeys, MouseKeys, Serial Keys, and Toggle Keys. It also supports Online Help and the ability to automatically reset options. New accessibility macros in Visual Studio 2008 allow users to quickly change the Visual Studio font size to match OS font size. Visual Studio 2008 does not include full support for accessing all functions using only the keyboard; however, equivalent functionality can usually be achieved via the keyboard through other mechanisms. For example, DataTips are a feature designed to allow easy debugging access to variables by mousing over variable names in the text editor. While it is possible to access debugging information about variables using other methods accessible using only the keyboard, DataTips do not have keyboard shortcuts. There is a subset of SDK tools that does not fully support all functionality from the keyboard. Visual Studio 2008 does not disrupt or disable accessibility features of the operating system with a few caveats. For instance, there are a small number of issues with enabling large fonts where dialog boxes are cut off. As another example, DataTips are designed to give pop-up information about variables when the user mouses over them in the editor. Screen readers interpret the DataTip pop-up as graphics instead of reading them as text. Full debugging information is still available via other methods, but users may have difficulty accessing that information by using DataTips. There is a subset of the SDK tools that

(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. Visual Studio 2008 provides a well-defined onscreen indication of the current focus that moves among interactive interface elements as the input focus changes with a few exceptions. Visual Studio 2008 provides support for this requirement with minor exceptions. does not fully implement MSAA. In some Setup dialogs as well as some of the complex dialog boxes focus is not clearly visible. In a few other dialogs, focus becomes difficult to see in High Contrast mode. Some dialogs and user interface elements are not sufficiently exposed for Assistive Technology to identify. For example, no information is provided to screen readers to help users select a color when using the ColorPicker dialog. However, colors can be set using numeric color values in other dialogs where Assistive Technology is supported. (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. Visual Studio 2008 provides textual information through operating system functions for displaying text at required minimum levels with minor exceptions. Visual Studio 2008 does not override user selected contrast and color selections or display attributes with minor exceptions. Visual Studio 2008 supports this requirement with minor exceptions. For example, the Visual Studio editor does not honor the Windows font size settings, but a user can easily set larger font sizes in the Visual Studio options dialog, or change the DPI settings from the system. Visual Studio 2008 provides excellent support for the appropriate Keyboard Repeat Rate or Display Settings (color) with minor exceptions. There are issues, for example, with the device explorer dialog box font size when set to High Contrast mode. Also, a few dialogs and

windows do not properly support High Contrast mode. But new accessibility macros in Visual Studio 2008 allow users to quickly toggle the editor into true High Contrast mode. There is a set of SDK tools that does not fully honor system font sizes; however, in most cases these tools do support system DPI changes. (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. Visual Studio 2008 does not override user selected contrast and color selections or display attributes with minor exceptions. Some dialogs do not display properly when using some display settings. For example, the device emulator background does not change when in High Contrast Black mode. Also, some designers do not display in high fidelity when using fewer than 24-bit color depth. (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 This functionality does not apply to Visual

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). (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 Fully Supported: Visual Studio 2008 provides a text equivalent for every non-text element.

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

Section 1194.31 Functional Performance Criteria - Detail Voluntary Product Accessibility Template 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. (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. (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 (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 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 Visual Studio 2008 provides functionality that Visual Studio 2008 provides functionality that Visual Studio 2008 also includes new macros which aid the user in setting font size, setting High Contrast mode, maximizing all tools windows, and other similar functions. Visual Studio 2008 provides functionality that

require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. Visual Studio 2008 provides functionality that Note to AT Users: Upon the release of software upgrades, there is often a lag between the software release date and the time it takes for some Assistive Technology vendors to upgrade their software and device drivers to support the new releases. The vendor s porting timeframe may be a factor in determining when you decide to upgrade to take advantage of new features. Microsoft provides the software code within its products to make those products ready for the AT devices and works closely with AT vendors in an effort to decrease time to market for new versions of AT products. Microsoft encourages both end users and purchasers of AT to contact their AT vendor to determine the current compatibility of their AT with Microsoft products.

Section 1194.41 (a) Product Support Documentation Section 1194.41 (b) Accessibility and Compatibility Features Section 1194.41 Information, Documentation, and Support - Detail Voluntary Product Accessibility Template Supported Supported Documentation is provided in digital format for customers on the web and available for no-charge download at http://msdn2.microsoft.com/ptbr/vstudio/default.aspx Visual Studio 2008 includes Help File documentation listing accessibility and compatibility features. An individual may access and view Help File topics online or may select a topic for print. 1194.41 (c) Support Services Supported The Microsoft Customer Support Services Help Desk is familiar with such features as keyboard access and other options important to people with disabilities. Microsoft offers a teletypewriter (TTY) service for customers who are hearing impaired. For assistance in the United States, contact Microsoft Technical Support on a TTY at 1-800-892-5234. This service is available Monday through Friday 5:00 A.M. to 9:00 P.M. and 5:00 A.M. to 3:00 P.M. Saturday PST. For more information, to find a center near you, go to http://www.microsoft.com/enable/centers/washingt on.aspx or http://www.microsoft.com/enable/centers/ For information on additional support services, visit the Microsoft Accessibility Web site at http://www.microsoft.com/enable/products/support.asp x

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. 2005 Microsoft Corporation. All rights reserved. Microsoft, Active Accessibility, Microsoft Press, MSDN, Visual Studio, Visual Basic, Windows, and the Windows logo are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Revised 10/19/2009 Microsoft regularly updates its websites and provides new information about the accessibility of products as that information becomes available.