eHiTS ^® : Electronic High Throughput Screening

Section 1194.21 Software Applications and Operating Systems

eHiTS belongs to this category. See section 1194.21 below.

Section 1194.22 Web-based Internet Information and Applications

 eHiTS Web-GUI belongs to this category. See section 1194.22 below.

Section 1194.23 Telecommunications Products

 n/a

eHiTS is not such a product.

Section 1194.24 Video and Multi-media Products

 n/a

 eHiTS is not such a product.

Section 1194.25 Self-Contained, Closed Products

 n/a

eHiTS is not such a product.

Section 1194.26 Desktop and Portable Computers

 n/a

 eHiTS is not such a product.

Section 1194.31 Functional Performance Criteria

 See section 1194.31 below.

Section 1194.41 Information, Documentation and Support

(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. This is entirely  true for eHiTS.

to get the simple command line usage type:
ehits.sh -help

(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. This is entirely  true for eHiTS.

(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.

n/a

 There is no user interface for eHiTS, it's a command line application, using text terminal window.

(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.

n/a

There is no user interface, no images for eHiTS. It's all text based.

(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.

n/a

There are no bitmap images in eHiTS. It's all text based.

(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. Textual information is  provided through operating system functions.

(g) Applications shall not override user selected contrast and color selections and other individual display attributes.

 n/a

eHiTS does not do this.

(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

eHITS does not do this.

(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.

 n/a

eHiTS does not do this.

(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

The product does not allow the user to adjust color and contrast settings.

(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. eHiTS does comply since it does not use flashing or blinking text, objects, or other elements at all.

(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. eHiTS does comply since it does not use electronic forms at all.

(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.

  n/a

 eHiTS Web-GUI  does not contain  any multimedia presentations.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

  n/a

 eHiTS Web-GUI  does not contain any information conveyed by color.

(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.

n/a  

 eHiTS Web-GUI  does not contain any such information.

(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.

  n/a

eHiTS Web-GUI  does not contain  any image maps.

(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

 n/a

 eHiTS Web-GUI  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.

(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.

  Supported.

 All pages are text only.

(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

(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 supported.

The list of applets are: JMOL.
This is the only applet used in the GUI, but it's noteven essential.

(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. But Web browser dependent

 eHiTS Web -GUI is written using basic HTML 4 and JavaScript 1.2. Web browsers that interface with Assistive Technology and is HTML / Javascript compliant will have this functionality.

(o) A method shall be provided that permits users to skip repetitive navigation links.

 n/a

 eHiTS Web-GUI  does not have repetitive navigation links.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

 n/a

 eHiTS Web-GUI  does not require any timed response.