Novell Identity Manager 4
Novell, Inc.
The purpose of the Voluntary Product Accessibility Template, or VPAT, is to assist Federal contracting officials and other buyers in making preliminary assessments regarding the availability of commercial "Electronic and Information Technology" products and services with features that support accessibility. It is assumed and recommended that offerers will provide additional contact information to facilitate more detailed inquiries.
The first table of the Template provides a summary view of the section 508 Standards. The subsequent tables provide more detailed views of each subsection. There are three columns in each table. Column one of the Summary Table describes the subsections of subparts B and C of the Standards. The second column describes the supporting features of the product or refers you to the corresponding detailed table, "e.g., equivalent facilitation." The third column contains any additional remarks and explanations regarding the product. In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product.
|
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 shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. |
Supported |
|
|
(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 |
|
|
(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 |
|
|
(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. |
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. |
Not Applicable |
|
|
(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 |
|
|
(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. |
Supported |
|
|
(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* |
*Some convenience controls in forms may require the use of a mouse,but they are not required for completion of the form. Forms are customizable and can be tailored to the needs of the users. |
Return to the top of the page.
|
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 with exceptions |
Text equivalent provided for every non-text element with the exception of buttons within the Compliance section. |
|
(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. |
Not Applicable |
|
|
(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. |
Supported |
|
|
(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 Supported |
Data cells and header cells in iManagaer 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, and titles of hidden frames may be read by screen readers (iManager). |
|
(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 |
|
|
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 exceptions |
Proper tags for text boxes,buttons and other controls are provided, however some of the text fields are not labeled with descriptive language. |
|
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supported |
Divs are used to separate navigational items from content items. Content items are divided into separate divs with appropriate headers. First, Previous, Next and last actions are available for navigating through data tables. |
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Supported |
|
Return to the top of the page.
|
Section 1194.23 Telecommunications
Products - Detail |
|
Section 1194.24 Video and Multi-media
Products - Detail |
Return to the top of the page.
|
Section 1194.25 Self-Contained, Closed
Products - Detail |
Return to the top of the page.
|
Section 1194.26 Desktop and Portable
Computers - Detail |
Return to the top of the page.
|
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 visually impaired shall be provided. |
Supported with minor exceptions (via compatibility with operating system accessibility features and third-party screen reader utilities)* |
Identity Manager is compatible with commonly used assistive technologies. Users of assistive technology should contact their assistive technology vendor to assess the compatibility of specific assistive technology with Novell products and to learn how to adjust their settings 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 are visually impaired shall be provided. |
Supported with minor exceptions (via compatibility with operating system accessibility features and third-party screen reader utilities)* |
|
|
(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 |
Identity Manager does not require user hearing for access to any application functionality. |
|
(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. |
Supported |
Identity Manager does not require user hearing for access to any application functionality. |
|
(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. |
Supported |
Identity Manager does not require speech recognition. |
|
(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 with minor exceptions (via compatibility with operating system accessibility features and third-party screen reader utilities)* |
|
Return to the top of the page.
|
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 |
Novell makes its documentation available in variety of formats at http://www.novell.com/documentation Documentation is provided in HTML, and can be converted to other formats as needed. |
|
(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. |
Supported |
|
|
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
Supported |
Novell's support services accommodates voice communications and email communications, both of which are operable by persons with disabilities. Support personnel are familiar with such features as keyboard access and other options important to people with disabilities. |
Return to the top of the page.
*Novell testing indicates that the exceptions are not significantly disruptive to product functionality. In some cases, functionality described is accessible through alternative or equivalent means, via the keyboard utilizing standard menu options.
**There is a lag between Novell's software release date and the time it takes for some Assistive Technology manufacturers to upgrade their software and device drivers to support these new releases. The manufacturer's porting timeframe may be a factor in determining when you decide to upgrade.
IMPORTANT NOTICE:
Novell, Inc. makes no representations or warranties with respect to the contents or use of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Novell does not warrant that this document is error-free. Further, Novell reserves the right to revise this document and make changes to its content, at any time, without obligation to notify any person or entity of such revision or changes. No contractual obligations or commitments are formed either directly or indirectly by this document. Novell periodically provides new information about the accessibility of products as that information becomes available.
|
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 shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.. |
Supported |
|
|
(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 |
|
|
(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 |
|
|
(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. |
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 |
|
|
(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. |
Supported |
|
|
(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 |
|
|
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 |
|
|
(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. |
Supported |
|
|
(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. |
Supported |
|
|
(i) Frames shall be titled with text that facilitates frame identification and navigation |
Supported |
|
|
(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 |
|
|
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 |
|
|
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supported |
Divs are used to separate navigational items from content items. Content items are divided into separate divs with appropriate headers. First, Previous, Next and last actions are available for navigating through data tables. |
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Supported |
|
Return to the top of the page.
|
Section 1194.23 Telecommunications
Products - Detail |
|
Section 1194.24 Video and Multi-media
Products - Detail |
Return to the top of the page.
|
Section 1194.25 Self-Contained, Closed
Products - Detail |
Return to the top of the page.
|
Section 1194.26 Desktop and Portable
Computers - Detail |
Return to the top of the page.
|
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 visually impaired shall be provided.. |
Supported with minor exceptions (via compatibility with operating system accessibility features and third- party screen reader utilities)* |
Identity Manager is compatible with commonly used assistive technologies. Users of assistive technology should contact their assistive technology vendor to assess the compatibility of specific assistive technology with Novell products and to learn how to adjust their settings 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 are visually impaired shall be provided |
Supported with minor exceptions (via compatibility with operating system accessibility features and third- party screen reader utilities)* |
|
|
(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 |
Identity Manager does not require user hearing for access to any application functionality. |
|
(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. |
Supported |
Identity Manager does not require user hearing for access to any application functionality. |
|
(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. |
Supported |
Identity Manager does not require speech recognition. |
|
(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 with minor exceptions (via compatibility with operating system accessibility features and third-party screen reader utilities)* |
|
Return to the top of the page.
|
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 |
Novell makes its documentation available in variety of formats at http://www.novell.com/documentation Documentation is provided in HTML, and can be converted to other formats as needed. |
|
(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. |
Supported |
|
|
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
Supported |
Novell's support services accommodates voice communications and email communications, both of which are operable by persons with disabilities. Support personnel are familiar with such features as keyboard access and other options important to people with disabilities. |
Return to the top of the page.
*Novell testing indicates that the exceptions are not significantly disruptive to product functionality. In some cases, functionality described is accessible through alternative or equivalent means, via the keyboard utilizing standard menu options.
**There is a lag between Novell's software release date and the time it takes for some Assistive Technology manufacturers to upgrade their software and device drivers to support these new releases. The manufacturer's porting timeframe may be a factor in determining when you decide to upgrade.
IMPORTANT NOTICE:
Novell, Inc. makes no representations or warranties with respect to the contents or use of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Novell does not warrant that this document is error-free. Further, Novell reserves the right to revise this document and make changes to its content, at any time, without obligation to notify any person or entity of such revision or changes. No contractual obligations or commitments are formed either directly or indirectly by this document. Novell periodically provides new information about the accessibility of products as that information becomes available.
|
Section 1194.22 Web-based Internet information and applications - Detail(RMA) |
||
|
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 |
Load button does not have a alt element, Reset Database, Login to Role Mapping Administrator and Save buttons don't have alt element |
|
(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 with minor exceptions |
Invalid LDAP Admin name is depicted by turning the background red. |
|
(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. |
Supported |
|
|
(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 Supported |
|
|
(i) Frames shall be titled with text that facilitates frame identification and navigation |
Not Applicable |
|
|
(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 Supported |
|
|
(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 Supported |
|
|
(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 exceptions |
Tabbing is not supported in the Configuration page and the confirmation dialogs in the RMA page. |
|
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supported |
|
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Not Supported |
|