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 these product and service providers will offer additional contact information to facilitate more detailed inquiries.
Summary Table
Voluntary Product Accessibility Template
| Criteria |
Supporting Features |
Remarks and explanations |
| Section 1194.21 Software Applications and Operating
Systems |
|
Please refer to the following VPAT for MyInfo features that
meet these criteria. |
| Section 1194.22 Web-based internet information and applications |
Not applicable |
|
| Section 1194.23 Telecommunications Products |
Not applicable |
|
| Section 1194.24 Video and Multi-media Products |
Not applicable |
|
| Section 1194.25 Self-Contained, Closed Product |
Not applicable |
|
| Section 1194.26 Desktop and Portable Computers |
Not applicable |
|
| Section 1194.31 Functional Performance Criteria |
|
Please refer to the following VPAT for MyInfo features that
meet these criteria. |
| Section 1194.41 Information, Documentation, and Support |
|
Please refer to the following VPAT for MyInfo features that
meet these criteria. |
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. |
Criteria fully met |
All features within MyInfo are keyboard accessible. |
| (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
|
MyInfo supports the accessibility settings of the operating system. Exception is Windows Accessibility Cursor options, which is not supported in the tree editor and in the text editor. |
| (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. |
Criteria fully met |
|
| (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. |
Criteria fully met |
|
| (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. |
Criteria fully met |
In MyInfo, all images used for controls or programmatic elements are consistent throughout the MyInfo applications. |
| (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. |
Criteria fully met |
|
| (g) Applications shall not override user selected contrast and color selections
and other individual display attributes. |
Supported with minor exceptions |
MyInfo supports system-wide color settings as identified in the operating system display properties. MyInfo does not extend operating system user defined font settings to the document frame due to the need to preserve the WYSIWYG (What You See is What You Get) User Interface (UI) model. However, MyInfo does enable the user to set document font sizes according to their specific needs.
MyInfo uses it's own background color options for the tree and for the text pane (which are fully configurable in the Options dialog). |
| (h) When animation is displayed, the information shall be displayable in at least
one non-animated presentation mode at the option of the user. |
Criteria fully met |
MyInfo does not use animations. |
| (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. |
Criteria fully met |
|
| (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. |
Criteria fully met |
A minimum of sixteen colors selections are provided in all instances where MyInfo allows a user to select from a range of colors. |
| (k) Software shall not use flashing or blinking text, objects, or other elements
having a flashing or blink frequency greater than 2 Hz and lower than 55 Hz. |
Criteria fully met |
MyInfo does not use flashing or blinking objects or text in any application User Interface. |
| (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. |
Criteria fully met |
|
Section 1194.31 Functional Performance Criteria
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. |
Criteria fully met |
MyInfo supports the use of screen readers to access user interface information. |
| (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. |
Criteria fully met |
|
| (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. |
Criteria fully met |
|
| (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. |
Criteria fully met |
|
| (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. |
Criteria fully met |
|
| (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. |
Criteria fully met |
|
