Section
508 Voluntary Product Accessibility Template
The purpose of the Voluntary Product Accessibility Template is to
assist Federal contracting officials in making preliminary assessments
regarding the availability of commercial Electronic and Information
Technology products and services with features that support accessibility.
It is assumed 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.
Click
here for more details about Section 508
|
Summary Table
Section 508 Voluntary Product Accessibility Template
|
| Criteria |
Supporting Features |
Remarks and explanations |
| Section 1194.21 Software Applications and Operating
Systems |
Supported.
Please refer to attached VPAT |
|
| Section 1194.22 Web-based internet information
and applications |
Supported.
Please refer to attached VPAT |
|
| Section 1194.23 Telecommunications Products |
|
ZYIMAGE RMA is not considered a telecommunications
product |
| Section 1194.24 Video and Multi-media Products |
|
ZyIMAGE RMA does not use multimedia except as
covered in section 1194.21 and 1194.22 |
| Section 1194.25 Self-Contained, Closed Products |
|
ZyIMAGE RMA is not a self-contained product |
| Section 1194.26 Desktop and Portable Computers |
|
ZyIMAGE RMA is software and Web-based as defined
under 1194.21, and 1194.22 |
| Section 1194.31 Functional Performance Criteria |
Supported.
Please refer to 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. |
Supported with exceptions:
The product has a web based interface and some functions can
not be executed from the keyboard. |
|
| (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 with minor exceptions:
Because the product is a browser based the browser that is used
will determine how well the application interacts with other
applications. |
Internet Explorer supports Windows Accessibility
features and also additional features that make Internet Explorer
more accessible for people with disabilities. |
| (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. |
This may depend on the browser that is used to
access the product. |
| (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.
See 1194.22 (a) |
|
| (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. |
ZyLAB has made a significant investment in collecting
user feedback and using this to increase the usability of its
products. |
| (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:
All information is presented in html pages in the browser. |
This may depend on the browser that is used to
access the product. |
| (g) Applications shall not override user selected
contrast and color selections and other individual display attributes. |
Supported:
See 1194.22 (d) |
|
| (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:
The product does not include animation |
|
| (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 minor exceptions:
The disposition schedule planning is color coded. An option
is provided to switch off color coding.
|
|
| (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:
This functionality is not permitted by the user. |
It is possible to provide customized stylesheets
to change the color and contrast of the application. This is
not a function that is permitted to the user. |
| (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:
The product does not include the use of flashing or blinking
text, objects or other elements. |
|
| (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:
Addressed throughout section 1194.22 |
|
|
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). |
Supported:
Alt tags are provided for all images. |
|
| (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:
The disposition schedule planning is color coded. An option
is provided to switch off color coding |
|
| (d) Documents shall be organized so they are readable
without requiring an associated style sheet. |
Supported. |
The product utilize style sheets, recognized by
the Access Board in the 508 standard as having potential accessibility
benefits. These style sheets can be overridden by the user's
browser preferences or a user-defined style sheet. |
| (e) Redundant text links shall be provided for
each active region of a server-side image map. |
Not applicable:
The applications does not include the use of server-side image
maps. |
|
| (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:
The applications does not include the use of client-side image
maps. |
|
| (g) Row and column headers shall be identified
for data tables. |
Supported:
The product uses the <th> tag to identify table header
rows. |
|
| (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: |
In the event that there are multiple logical levels
in a data table header information will be associated and row
information will be associated where appropriate using the <th>
tag. |
| (i) Frames shall be titled with text that facilitates
frame identification and navigation |
Not applicable:
The product does not use frames. |
|
| (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:
The product does not include the use of blinking or flashing
user interface elements. |
|
| (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:
All pages in the product are text only, with few exceptions
of buttons using graphic icons, but these have <alt> tags. |
|
| (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 with minor Exceptions:
The product uses .NET technology that generates interface elements
with scripts depending on the capability of the browser. If
a browser without scripting capability is used, html without
scripting will be generated. This feature has not been tested. |
Some product functions may not work properly with
scripts turned off. |
| (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:
The product does not require applets or other plug-ins. |
|
| (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:
Form fields will be in a logical tab order and all information
necessary to properly complete the form will be viewable on
the page or within the structural mark-up |
Form fields will be in a logical tab order and
all information necessary to properly complete the form will
be viewable on the page or within the structural mark-up |
| (o) A method shall be provided that permits users
to skip repetitive navigation links. |
Supported with minor exceptions:
The product does not use a repetitive navigation section. However,
the file plan location is repeated on every page and this is
a concatenation of clickable file plan locations (along the
path through the fileplan hierarcy). When using a tab key to
select a link, this section will be selected as the final selection.
|
|
| (p) When a timed response is required, the user
shall be alerted and given sufficient time to indicate more
time is required. |
Not applicable:
The product does not include the use of timed responses. |
|
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.
|
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. |
Supported:
The product supports the use of 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. |
Supported:
The product supports the system large font settings. |
Users of Microsoft Windows operating systems can
access Magnifier in the Accessibility Options. A 3rd party Assistive
Technology 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 |
Not Applicable:
The product does not require hearing. |
|
| (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:
The product does not provide information as audio. |
|
| (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:
The product does not require user speech. |
|
| (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 |
|
|