|
|
[an error occurred while processing this directive]
|
|
|
|
| Novell BorderManager 3.8 |
| Product Accessibility Status (VPAT) |
|
| Accessibility Statement |
|
|
Date: January 04, 2003
Name of Product: BorderManager
Version: 3.8
Contact for more Information: http://www.novell.com/products/bordermanager/
This document is intended to aid customers in their performance of market research on the availability of products that meet their accessibility needs, including compliance with legal requirements.
Customers should refer to the "Current as of" date found at the bottom of this page. Once an updated document is posted, previous documents should not be considered accurate or valid.
|
|
 |
summary information |
|
|
|
| Criteria |
Supporting Features |
Remarks and Explanations |
| Section 1194.21 Software Applications and Operating Systems |
Code modifications have been made to the product to meet these standards subject to the remarks in the details below. |
|
| Section 1194.22 Web-based internet information and applications |
Code modifications have been made to the product to meet these standards subject to the remarks in the details below. |
|
| Section 1194.23 Telecommunications Products |
Not Applicable |
|
| Section 1194.24 Video and Multi-media Products |
Not Applicable |
|
| Section 1194.25 Self-Contained, Closed Products |
Not Applicable |
|
| Section 1194.26 Desktop and Portable Computers |
Not Applicable |
|
| Section 1194.31 Functional Performance Criteria |
Support for these standards is provided as described in the remarks in the details below. |
|
| Section 1194.41 (a) Information, Documentation and Support |
Support for these standards is provided as described in the remarks in the details below. |
|
|
|
|
Section 1194.21 Software Applications and Operating Systems |
|
|
|
| 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. |
Supported with Exceptions |
Some administrative functions may require use of the mouse |
| (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 |
|
| (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 Exceptions. |
Focus may be ambiguous when performing some administrative functions |
| (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. |
This feature has not been tested. |
|
| (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 |
|
| (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 |
|
| (g) Applications shall not override user selected contrast and color selections and other individual display attributes. |
Not Supported |
|
| (h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. |
Supported |
|
| (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 with Exceptions |
On a small number of screens, Novell Client Firewall uses color exclusively to log issue severity and status |
| (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. |
Not Applicable |
|
| (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. |
Not Applicable |
|
| (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. |
This feature has not been tested |
|
|
|
|
Section 1194.22 Web-based internet information and applications |
|
|
|
|
Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4.
| 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 with Exceptions |
|
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Not Applicable |
|
| (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 |
|
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supported |
|
| (e) Redundant text links shall be provided for each active region of a server-side image map. |
Not Applicable |
|
| (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 |
|
| (g) Row and column headers shall be identified for data tables. |
Row and column headers are not identified in tables, and there is no workaround for this limitation. |
Data tables are used only in a small subset of administrative and tracking features. |
| (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. |
Data cells and header cells are not marked, and there is no workaround. However, they are used only in a small subset of the overall product. |
|
| (i) Frames shall be titled with text that facilitates frame identification and navigation |
Supported |
Underscores may be included in descriptive names, titles of hidden frames may be read by screen readers |
| (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 |
|
| (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 |
|
| (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. |
Supported |
While clearly indicating function, associated text may in some cases be ambiguous. |
| (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). |
Not Applicable |
|
| (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. |
Supported with Minor Exceptions |
In some cases, input controls may not be clearly associated with labels and other textual cues. |
| (o) A method shall be provided that permits users to skip repetitive navigation link |
Supported |
Frames are used to isolate navigation from content elements. In some cases, users who navigate with the keyboard must tab through lists manually from the beginning to get to their data. One option for avoiding these tasks is to use the browser’s text search function to skip 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 |
|
*Web-based administration for this product is provided through Novell's iManager administration framework. For further detail on iManager's accessibility features, see the iManager VPAT.
|
|
|
Section 1194.31 Functional Performance Criteria |
|
|
|
| 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. |
Supported |
Supported (via compatibility with operating system accessibility features and third-party screen reader utilities)
The performance of a screen reader, when used in conjunction with this product, is subject to the actual functionality and limitations of the chosen screen reader as well as the actual functionality and limitations of the underlying operating environment and its user interface mechanisms. |
| (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. |
Supported |
Supported (via compatibility with operating system accessibility features and third-party screen reader utilities)
The performance of a screen reader, when used in conjunction with this product, is subject to the actual functionality and limitations of the chosen screen reader as well as the actual functionality and limitations of the underlying operating environment and its user interface mechanisms. |
| (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 |
Not Applicable. |
Not Applicable |
| (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. |
Not Applicable |
| (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. |
Supported |
| (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. |
Not Applicable. |
Supported (via compatibility with operating system accessibility features and third-party accessibility utilities) |
|
|
|
|
|
