Summary Table

Voluntary Product Accessibility Template^TM

Criteria

Supporting Features

Remarks and explanations

Section 1194.21 Software Applications and Operating Systems

Supports with Exceptions

CrossOver is an application that allows users to run Windows applications on an Intel based Mac OS X system.

The general case for CrossOver is that CrossOver does not intentionally disable functionality for accessibility, so a program that is accessible on Windows should, in general, remain accessible within the CrossOver environment.

However, CrossOver is not a perfect replication of the Windows environment. That is true even in the context of a person with no disability. Hence, the only way to be certain of the accessibility of a CrossOver based solution is to examine the combination of CrossOver and the specific Windows application of interest.

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 Products

Not Applicable

Section 1194.26 Desktop and Portable Computers

Not Applicable

Section 1194.31 Functional Performance Criteria

Not Applicable

Section 1194.41 Information, Documentation and Support

Not Applicable

Section 1194.21 Software Applications and Operating Systems - Detail
Voluntary Product Accessibility Template^TM

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 through Equivalent Facilitation

The primary function of CrossOver is to enable users to run Windows programs on their Mac. Further, since CrossOver is a general purpose application, it cannot know in advance what keyboard mappings that application will use. As a result, CrossOver itself deliberately does not map its own internal functions to keyboard shortcuts, instead preserving those keys for use by the Windows applications it attempts to run.

However, the Keyboard Shortcuts tab of the Keyboard & Mouse pane of System Preferences provides the ability for a user to map a keyboard shortcut to any CrossOver menu choice. Hence, a user unable to use the visual interface could map keyboard shortcuts as needed to functions within CrossOver.

(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 with Exceptions

CrossOver does not deliberately disable or deactivate accessibility features in the Windows programs that it runs. In fact, our core mission at CodeWeavers is to enable the experience of running a Windows program on a Mac to be as near to identical with the same Windows experience as is possible. However, CrossOver as a product does not run every Windows application, nor does every feature of every Windows application necessarily work. Thus, it would be fair to caution that there may be some unintentional failure of accessibility functionality to work.

(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

Within the GUI of CrossOver itself, this is well supported. However, again, since CrossOver can be used to run any Windows application, it may be that Mac based Assistive Technology will be unable to interoperate with a Windows application.

(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

(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

(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

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

Supports

(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

The only animations used by CrossOver are simple 'wait' indicators that convey no other information but that CrossOver is working.

(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

(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

CrossOver doesn't provide any color or 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.

Supports

(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

CrossOver uses standard controls for accepting user input in places like the Register dialog, or the New Bottle sheet.