Voluntary product accessibility template for Forefront TMG
Applies To: Forefront Threat Management Gateway (TMG)
This document presents the voluntary product accessibility template for Forefront TMG.
Product information
Date: |
April 2008 |
Name of product: |
Microsoft® Forefront™ Threat Management Gateway (TMG) |
See for more information: |
Forefront TMG Web site (https://go.microsoft.com/fwlink/?LinkId=116228) or Microsoft Accessibility Web site (https://go.microsoft.com/fwlink/?LinkId=154509) |
Summary table
| Criteria | Supporting features | Remarks and explanations |
|---|---|---|
Section 1194.21 Software applications and operating systems |
Refer to the included voluntary product accessibility template (VPAT) detail table |
Refer to the attached VPAT detail table |
Section 1194.22 Web-based Internet information and applications |
Refer to the attached VPAT detail table |
Refer to the attached VPAT detail table |
Section 1194.23 Telecommunications products |
Not applicable |
Not applicable |
Section 1194.24 Video and multimedia products |
Not applicable |
Not applicable |
Section 1194.25 Self-contained, closed products |
Not applicable |
Not applicable |
Section 1194.26 Desktop and portable computers |
Not applicable |
Not applicable |
Section 1194.31 Functional performance criteria |
Refer to the attached VPAT detail table |
Refer to the attached VPAT detail table |
Section 1194.41 Information, documentation and support |
Refer to the attached VPAT detail table |
Refer to the attached VPAT detail table |
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 that has a keyboard, product functions can be run from a keyboard where the function itself or the result of performing a function can be discerned textually. |
Supported with minor exceptions |
In Windows® operating systems, Forefront TMG supports accessibility features, including StickyKeys, FilterKeys, MouseKeys, High Contrast, and more. The following are exceptions to this:
|
(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. |
Supported |
None |
(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. |
Supported with minor exceptions |
This is supported throughout the product. One area that might be confusing to customers is focus transfer to the Forefront TMG central pane when traversing the navigation tree. Use F6 in order to return the focus to the tree. |
(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. |
Supported with minor exceptions |
This is supported throughout the product. The text on the last screen of some wizards may not be read automatically without being requested. The full node name in the Forefront TMG management console may not be read without assistive technology. Opening the shortcut menu by using the keyboard causes a screen reader to read. All shortcut menu actions are also available and readable from the Forefront TMG task pane. The text on the network template diagram cannot be read by assistive technology. Descriptive text provided with the diagram can be read. |
(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. |
Supported |
None |
(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. |
Supported |
None |
(g) Applications shall not override user-selected contrast and color selections and other individual display attributes. |
Supported with minor exceptions |
Contrast and color selections are fully supported throughout the product. However, there are a number of pages that contain black text by default, which cannot be read if the background is set to black (in some high-contrast modes):
This issue can be resolved by configuring font color settings in Windows Internet Explorer® (In Microsoft IE 6, click Tools, click Internet Options, and then on the General tab, click Colors.) |
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. |
Not applicable |
None |
(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. |
Supported |
None |
(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. |
Supported |
None |
(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. |
Supported |
None |
(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 with minor exceptions |
Use of assistive technology is supported in the product. There are instances where users using screen reader technology, such as the Narrator tool, may experience minor difficulty:
|
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). |
Supported |
None |
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Not applicable |
None |
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. |
Supported |
Reports include a text table with numerical data for non-color dependent viewing of this information. |
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supported |
None |
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Not applicable |
None |
(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. |
Not applicable |
None |
(g) Row and column headers shall be identified for data tables. |
Supported |
None |
(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. |
Not applicable |
None |
(i) Frames shall be titled with text that facilitates frame identification and navigation. |
Supported |
None |
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. |
Supported |
None |
(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. |
Not applicable |
None |
(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. |
Not applicable |
None |
(m) When a Web page requires that an applet, plug-in, or other application be present on the client system in order to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). |
Not applicable |
None |
(n) When electronic forms are designed to be completed online, 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 |
None |
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Support with minor exceptions |
Users who navigate reports with the keyboard must use the TAB key in order to move through lists manually from the beginning to get to their data. To avoid this, in Internet Explorer, users can click Edit, and then click Find (on This Page) to go to known terms on the Web page. |
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Not applicable |
None |
Section 1194.31 Functional performance criteria - 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 have low vision shall be provided. |
Supported |
Commonly used assistive technologies, such as screen readers, can be used with Forefront TMG. Therefore, user vision is not required for using the core functionality of the product. Users of assistive technology should contact their assistive technology vendor in order to assess the compatibility of a specific technology with Microsoft products and to learn how to adjust their settings in order to optimize interoperability. |
(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 have low vision shall be provided. |
Supported |
Users of Windows operating systems can use the Accessibility Options in Control Panel in order to access Microsoft Magnifier and High Contrast settings in order to enlarge the screen display. An assistive aid may also be used. |
(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. |
Supported |
None |
(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. |
Not applicable |
None |
(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. |
Not applicable |
None |
(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. |
Supported |
None |
Section 1194.41 Information, documentation, and support - detail
| Criteria | Supporting features | Remarks and explanations |
|---|---|---|
(a) Product Support Documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. |
Supported |
Product documentation is available on the product CD, on the Web, and in .doc format for specific case studies. White papers, related to product practices and implementation, are also available. Standard Microsoft practices for documentation have been adhered to, including alternative text for graphics and accessible text by readers for users that have low vision. Documentation sets are also available in printed form from Microsoft Worldwide Fulfillment. Product documentation can be found on https://www.microsoft.com (https://go.microsoft.com/fwlink/?LinkId=116257). |
(b) Accessibility and compatibility features. 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. |
Supported |
Documentation for Forefront TMG includes an accessibility topic, which summarizes the accessibility options and shortcuts. Forefront TMG also uses Windows Server® 2008 accessibility features, which are documented in Windows Help, and the Microsoft Management Console accessibility features, which are documented in Forefront TMG Help. |
(c) Support Services for products shall accommodate the communication needs of end-users with disabilities. |
Supported |
Microsoft Product Support Services is familiar with such features as keyboard access and other options important to people with disabilities. Microsoft offers a teletype/telecommunication device (TTY/TDD) service for deaf or hard-of-hearing customers. For assistance in the United States, contact Microsoft Product Support Services on a TTY/TDD device at 1-425-635-4948. This service is available between 06:00 (6:00 A.M.) and 18:00 (6:00 P.M.) Pacific Time, Monday through Friday. Information about additional support services is available at the Microsoft Help and Support Web site (https://go.microsoft.com/fwlink/?LinkId=154510). |
This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2008 Microsoft Corporation. All rights reserved.
Microsoft, Forefront, Internet Explorer, Windows, and Windows Server are trademarks of the Microsoft group of companies.
All other trademarks are property of their respective owners.