Oracle Accessibility Conformance Report

The product was tested for:

• Non-text characters are not used or have a meaningful alternative text.
• CAPTCHAs are not used.

The product was tested for:

• User interface component labels are associated with the fields they are labeling.
• Relationships between data are identifiable by assistive technology, or a description of the information and the relationship is provided.
• Information about headings, lists and tables is exposed to assistive technologies using accessibility services provided by the platform software.
• Groups of components are described with a description of the grouping.

Exception: 

• In Processing Task Order Entry, table headings are not properly correlated to cells when using assistive technologies. (AP-11320)
• In Maintain Case:
  • Field instructions are not read by the screen reader. (AP-11330)
  • Field labels not always read by screen reader. (AP-11330)
  • The purpose of the form is not always relayed to a screen reader. (AP-11330)
  • Table headings are not properly correlated to cells when using assistive technologies. (AP-11326) 

The product was tested for:

• The sequence of elements presented by assistive technologies matches a logical reading sequence.

The product was tested for:

• Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound.
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic.

The product was tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.

Technologies that do not provide attributes that support identifying the expected meaning for the form input data are not in scope for this success criterion.

The product was tested for:

• Information conveyed by color has a contrast ratio of at least 3:1.

The product was tested for:

• Large-scale text and images of large-scale text have a contrast ratio of at least 3:1.
• Other text and images of text have a contrast ratio of at least 4.5:1.

Exceptions: 

• The case details banner displayed in Processing Task Order Entry does not have adequate contrast (AP-11343).
• The demographics banner displayed in Maintain Case does not have adequate contrast. (AP-11343)

The product was tested for:

• Text can be resized up to 200% without loss of content or functionality.

Exception: 

• At 200% zoom, a user can only navigate using a mouse. (AP-11295)

The product was tested for: 

• Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential.

The product was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

The product was tested for:

• Non-text items have a contrast ratio of at least 3:1.

Exception:

• The search icon in the application (next to the Case Details field) does not meet the contrast ratio of 3:1. (AP-11347)

There is no content implemented using markup languages that support editing the text style properties in this criteria.

The product was tested for:

• Dismissable -The content can be dismissed without moving the pointer or keyboard focus.
• Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing.
• Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

The product was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes.
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation.
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms).

Exception:

• At 200% zoom, a user can only navigate using a mouse. (AP-11295)

The product was tested for:

• Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.

The product was tested for:

• There are no single character keyboard shortcuts.

The product was tested for:

• Time limits are not used.

The product was tested for:

• There is no moving, blinking, scrolling or auto-updating content.

The product was tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.

Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is always automatically met.

The name of the software application describes the topic or purpose.

The product was tested for:

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence.

Exception:

• In Cytology Result Entry, the screening dialog box does not receive landing focus. Workaround: A user can use ALT+TAB to restore focus. (AP-11377)

The product was tested for:

• Links are not used in the product.

Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is always automatically met.

The product was tested for:

• Headers describe the topic or purpose of the content below them.
• Labels describe the purpose of the associated field.

The product was tested for:

• Visual indication of the location of the focus.

Exception: 

• In the Case Findings and Online Review workflows, the visible focus is lost after a user moves away from the case number and search fields. (AP-11287)

The product was tested for:

• There are no multipoint or path-based gesture actions.

The product was tested for:

• When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function.
• When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion.
• When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event.

The product was tested for:

• User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.

The product was tested for:

• There are no functions that require motion of the device.

The product was tested for:

• This application only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable.

The product was tested for:

• There are no passages of text that are different then the language of the application.

The product was tested for:

• When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window.

The product was tested for:

• In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components.

The product was tested for:

• There are no navigational elements that are repeated.

The product was tested for:

• Images and controls are used and identified consistently throughout the product.

The product was tested for:

• When input errors are detected, they are described to the user in text, including identifying the item where the error occurred.

The product was tested for:

• Labels or instructions are provided when the product requires user input.

The product was tested for:

• Where suggestions for fixing an input error are known, they are provided to the user.
• User input is not required.

Exception: 

• Error suggestions are not displayed or communicated via assistive technologies in date fields or in required fields. (AP-11331)

The product was tested for:

• Submissions can be reversed by the user.
• Data is checked for input errors with an opportunity for the user to correct them.
• Data can be reviewed, corrected, and confirmed by the user before they are finalized.

This criterion is considered as always satisfied.

The product was tested for:

• Controls have a programmatically associated name.
• Additional state information is programmatically exposed for controls, such as whether a field is ‘required’.
• Custom controls have appropriate roles specified using the role attribute.
• Custom controls have appropriate state and property information conveyed.
• Custom controls have a meaningful programmatically exposed name.

Exceptions: 

• The screen reader does not read:
  • Column headers in tables or the labels on text fields if a field has a defaulted value.
  • The labels on the toolbar button and alert help text. (AP-11332)

The product was tested for:

• There are no status messages.

The product was tested for:

• Does not disrupt platform accessibility features such as sticky keys, high contrast and large fonts.

The product was tested for:

• Responds to platform settings for color, contrast, font type, font size, and focus cursor.

Exception:

• Applications do not display or support using system controls such as Sticky Keys and preferences for color, contrast, font type, font size etc. (AP-11341)

The product documentation describes:

• Special keystrokes needed to operate controls.
• Workarounds.

Accessibility-related documentation can be found at

• Oracle Health Anatomic Pathology Reference Pages
• Oracle Health Anatomic Pathology Help Pages

Product documentation is in electronic format.

Oracle Health Products are supported by several operations teams who can provide accessibility support solutions to customers.

Oracle customers have access to electronic support through eService or by calling Oracle Health Support at 1.866.221.8877. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Health Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. Oracle Health Support will respond to technical issues according to the standard service request process.