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.
* Changes: added Section 1194.41
Date: November 20, 2008
Name of Product: Access Manager 3.1
Return
to the top of the page.
|
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.
|
Partial Support
|
Some screens within the
administration GUI may require the use of a 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
|
Some screens do not
clearly display the input focus on the current screen
|
|
(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.
|
Partial Support
|
Some images within the
administration GUI do not provide an alt text message
|
|
(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 with minor
exceptions
|
Some images are not
consistent throughout the administration GUI
|
|
(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 with minor
exceptions
|
Some screens will
override the user's selected contrast and color selections
|
|
(h) When animation is
displayed, the information shall be displayable in at least one
non-animated presentation mode at the option of the user.
|
N/A
|
|
|
(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.
|
N/A
|
|
|
(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.
|
Partial Support
|
Some form controls
within the Administration GUI may require the use of a mouse
|
Return
to the top of the page.
|
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).
|
Partial Support
|
Some screens do not
provide a text equivalent to non-text elements.
|
|
(b) Equivalent alternatives
for any multimedia presentation shall be synchronized with the
presentation.
|
N/A
|
|
|
(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.
|
Partial Support
|
Some screens require
the associated style sheet
|
|
(e) Redundant text links
shall be provided for each active region of a server-side image
map.
|
N/A
|
|
|
(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.
|
Support with
exceptions
|
Some image maps do not
provide redundant text links
|
|
(g) Row and column headers
shall be identified for data tables.
|
Not Supported
|
Row and column headers
in iManager are not identified in tables, and there is no
workaround for this limitation.
|
|
(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 iManager are not marked, and there is no workaround.
|
|
(i) Frames shall be titled
with text that facilitates frame identification and navigation
|
Partial Support
|
Some screens do not
provide sufficient frame identification
|
|
(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.
|
N/A
|
|
|
(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.
|
Partial Support
|
Some screens require
scripting languages that have difficulties being used with
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).
|
Supported
|
|
|
(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
|
Some screens do not
have all the information needed for use with Assistive Technology
|
|
(o) A method shall be
provided that permits users to skip repetitive navigation links.
|
Supported with
exceptions
|
Some screens require
the user to use repetitive links for navigation
|
|
(p) When a timed response is
required, the user shall be alerted and given sufficient time to
indicate more time is required.
|
Supported
|
|
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.
Return
to the top of the page.
|
Section 1194.23 Telecommunications Products -
Detail Voluntary Product Accessibility Template
Access Manager is not considered a telecommunication product.
|
Return
to the top of the page.
|
Section 1194.24 Video and Multi-media Products -
Detail
Voluntary Product Accessibility Template
Access Manager is not considered a video or
multi-media product.
|
Return
to the top of the page.
|
Section 1194.25 Self-Contained, Closed Products -
Detail Voluntary Product Accessibility Template
Access Manager is not considered a self-contained
product.
|
Return
to the top of the page.
|
Section 1194.26 Desktop and Portable Computers -
Detail
Voluntary Product Accessibility Template
Access Manager is software as defined under section
1194.21.
|
Return
to the top of the page.
|
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.
|
Partial Support
|
Some screens cannot be
read entirely with screen readers
|
|
(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.
|
Partial Support
|
Some screens cannot be
read using Assitive technology and screen readers.
|
|
(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
|
Access 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
|
Access 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
|
Access 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.
|
Support with
exceptions
|
Some screens require
the use of a mouse.
|
Return
to the top of the page.
|
Section 1194.41 Information, Documentation and
Support - Detail
Voluntary Product Accessibility Template
|
|
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.
|
*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.
|