Datamaxx Group, Inc.

Voluntary Product Accessibility Template

Date: February 21, 2005

Product: Omnixx Force Browser

Description: The Omnixx Force Browser is one module of a comprehensive communications suite for law enforcement and homeland security applications.

The product covered by this Voluntary Product Accessibility Template includes Omnixx Desktop Logon, Omnixx Desktop, and Omnixx Force Browser.

Contact for more Information:

Please contact your Datamaxx Sales Representative at:

Datamaxx Group, Inc.
2001 Drayton Drive
Tallahassee, Florida 32311

Phone: 850.588.8000
Fax: 850.558.8104
E-Mail: Sales@datamaxx.com

Summary Table

Voluntary Product Accessibility Template
Criteria Supporting Features Remarks and Explanations
Section 1194.21 Software Applications and Operating Systems Supports with
Exceptions (*) 		The product provides full keyboard capabilities with enhanced keyboard commands and macro capability for persons with disabilities. Supports JAWS with certain non-critical exceptions.
Section 1194.22 Web-based Internet Information and Applications Not Applicable Is not a Web-based Internet Information Application
Section 1194.23 Telecommunications Products Not Applicable Is not a Telecommunications Product
Section 1194.24 Video and Multi-media Products Not Applicable Is not a Video or Multi-media Product
Section 1194.25 Self-Contained, Closed Products Not Applicable Is not a Self-Contained, Closed Product
Section 1194.26 Desktop and Portable Computers Not Applicable Is not a Desktop or Portable Computer Product
Section 1194.31 Functional Performance Criteria Supports Supports additional functionality for individuals who are blind, visually impaired, deaf or hard of hearing.
Section 1194.41 Information, Documentation and Support Supports Product documentation is provided in alternative formats as requested.

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. Supports with
Exceptions (*)		 The Logon, Desktop and Browser Application components provide full keyboard capabilities with enhanced keyboard commands and macro capability for persons with disabilities. Direct command line text entry is also available. Supports the JAWS screen reader with certain exceptions attributed to limitations in the Sun Java SDK and Accessibility Bridge middleware. However, these are not critical and the application is usable with JAWS.
(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. Supports There are no known issues associated with the product. All operating system accessibility features continue to work. The product does not affect the application programming interface.
(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. Supports with
Exceptions (*)		 Focus is well defined for keyboard access and control. Supports the JAWS screen reader with certain exceptions attributed to limitations in the Sun Java SDK and Accessibility Bridge middleware. However, the application provides full functional equivalency by providing the user multiple methods for implementing commands.
(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.

Supports with
Exception (*)

 The product provides the user with sufficient information about the state of an interface element with one exception relating to the use of the JAWS screen reader. This exception is attributed to the Sun Java SDK and Accessibility Bridge middleware. Tool tips are used where appropriate.
(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. Supports The product's use of images and their related meanings are consistent throughout.
(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. Supports The product fully supports textual information through operating system functions for displaying text. In addition, highly complex textual information is also supported through the use of the JAWS screen reader.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supports The application does not override user selected contrast and color selections or other individual display attributes.
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. Supports There are no issues associated with animated display elements for this product.
(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. Supports with
Exception (*)		 There is one exception in the product for the use of color in identifying required data field entry. This will be corrected in the next update.
(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. Supports The product fully supports user color and contrast settings along with the utilization of screen magnification assistive technology.
(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. Supports The product does not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz or lower than 55 Hz.
(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. Supports with
Exceptions (*)		 The product incorporates highly complex data entry forms. All field labels and their relationships are properly identified by assistive technology such as the JAWS screen reader. There are certain exceptions attributed to limitations in the Sun Java SDK and Accessibility Bridge middleware. However, all forms are fully accessible and usable by JAWS.

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. Supports The application supports the JAWS screen reader.
(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.

Supports The application supports standard screen magnifying software and the JAWS screen reader.
(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 Supports The application is fully accessible for persons who are deaf or hearing impaired.
(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. Supports The application is fully accessible for persons who are deaf or hearing impaired. There is only one instance of audio information in the application and functional equivalence is provided in that case.
(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. Supports The application is fully functional without 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. Supports The application supports information retrieval through the use of assistive technology devices interfaced to the computer hardware and operating system. Command line input and macro capability assist in overcoming keystroke commands requiring simultaneous actions. The application is designed to not require strength.

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 Supports Upon request, support documentation will be provided in braille, large print and electronically on CD-ROM. In the future, support documentation will be available on an accessible website.
(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. Supports Upon request, accessibility and compatibility features will be provided in braille, large print and electronically on CD-ROM. In the future, this documentation will be available on an accessible website.

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

Supports This criteria is currently supported through the Florida Telecommunications Relay Service. Future enhancements include direct TTY and improved interactive voice response menuing system access to Datamaxx services and support.

Return to the top of the page.

*Supports with Exceptions

The following exceptions were documented during the testing of this product for Section 508 compliance. The product is fully keyboard accessible including keyboard shortcuts, macros, and command line text control. These exceptions are currently attributable to limitations in the Sun Java SDK and Accessibility Bridge middleware architecture. However, these exceptions do not interfere with the use of the JAWS screen reader to fully operate and manage this application. These exceptions will be corrected in a future update to the product.

1. There are several instances where navigational text within the menu structure of a window is read several times by the screen reader; however, the functionality of the commands remain intact.
2. Focus is not maintained in one navigational tree when interfaced with the JAWS screen reader; however, the product provides full functional equivalency through multiple command methods.
3. There is one table of course listings where visual focus in not maintained; however, the text is fully accessible by the JAWS screen reader.
4. Selection windows cannot track row and column location; however, they are fully accessible by keyboard, visual focus is maintained and selection data is read correctly by the JAWS screen reader.
5. Blue text is used to signify required data entry fields. An alternate visual indicator will be provided.
6. The JAWS open windows list interacts with the forms open inside Omnixx Force by closing the active form when the list is closed.

Return to the top of the page.