Oracle Accessibility Conformance Report

The product was tested for:

• Images that convey information have meaningful alternative text using ALT.
• Images that are decorative are marked up using ALT=”” or CSS background images.
• Titles for Objects and Applets are provided.
• Controls have an associated name.
• Non-text characters are not used or have meaningful alternative text.
• CAPTCHAs are not used.

Exception:

• The associated name is missing for the Select checkbox control in the Vitals Interop component for importing the result. (CHARTING-41462)
• Meaningful alternative text is missing for the clinical result indicators in the Vital Signs flowsheet grid (CHARTING-41461)
• Meaningful alternative text is missing for the clinical result indicators and the icon in the Vitals Interop flowsheet grid. (CHARTING-41462)

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.
• Headings are encoded with HTML heading tags.
• List markup is used for marking up lists.
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate.
• Data tables specify SUMMARY or CAPTION.
• Layout tables use appropriate markup.
• Groups of components are marked up with their description.
• Style sheets are used only to change the layout and presentation on the screen.

Exception:

• The Vitals Interop (Outside Records) flowsheet data grid does not have a label. (CHARTING-41409) 
• The elements are not linked correctly in Vital Signs flowsheet grid (CHARTING-41410)
• The relationship between the grid, header, and cells is missing in the Vitals Interop flowsheet grid.  (CHARTING-41412)
• The Vital Signs flowsheet data grid does not have a label. (CHARTING-41386)
• Label is not associated with the checkbox for importing the result within the Vitals Interop data grid.  (CHARTING-41444)

The product was tested for:

• The sequence of elements in the DOM 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.

Exception:

• The green color tick mark (success) for imported results in the Vitals Interop data grid does not provide a reference that this result has been imported. (CHARTING-41450)
• The Multiple Results (All Normal), Multiple Results (One or More High, Low, or Abnormal), Multiple Results (One or More Critical), Imported green tick in Vitals Interop data grid (Previously Added section), purple diamond icon in the Outside Records banner lacks a hover text and a text alternative, and it is not readable by screen readers. (CHARTING-41443)

The product was tested for:

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

The product was tested for:

• There are no text fields that collect information about the user.

The product was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight.
• Information conveyed by color has a contrast ratio of at least 3:1.

Exception:

• Clinical indicators and the Last Load icon should be displayed (visible) on the component in an alternative format like a legend or icon label, in addition to being provided through color and hover text. (CHARTING-41443)

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.

Exception:

• The grey text on a pink background does not meet the contrast minimum. (CHARTING-41403)

The product was tested for:

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

Exception:

• At 200% zoom, clicking the Add Vitals button hides a few integrated charting views used to chart vital signs and measurements. (CHARTING-41381)

The product was tested for:

• Images of text are not used.

The product was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.

Exception:

• Vitals Interop data grid content cuts off at 400% zoom, and the horizontal scroll bar is not operable. (CHARTING-41393)
• At 400% zoom, the Modern Vitals component displays a warning message, and the clinical flowsheet grid that displays the vitals and measurements is entirely lost. (CHARTING-41394)

The product was tested for:

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

Exception:

• The grey multiple results icon on a white background does not meet the contrast minimum. (CHARTING-41608)

The product was tested for:

• When the following attributes and no others are modified there is no loss in functionality or content:
  • Line height (line spacing) to at least 1.5 times the font size.
  • Spacing following paragraphs to at least 2 times the font size.
  • Letter spacing (tracking) to at least 0.12 times the font size.
  • Word spacing to at least 0.16 times the font size.

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.

Exception:

• No tooltip or content on hover is displayed for Multiple Results (All Normal), Multiple Results (One or More High, Low, or Abnormal), Multiple Results (One or More Critical),  Imported green tick in Vitals Interop data grid (Previously Added section), Comment icon in the Vitals Interop data grid, Purple diamond icon in the Outside Records banner. (CHARTING-41395)

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:

• The hover text across the component is not keyboard-navigable. (CHARTING-41445)
• Select checkbox in the Vitals Interop flowsheet result cell is not keyboard navigable. (CHARTING-41476)

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:

• Single character keyboard shortcuts are only active when that component has focus.

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.

The product was tested for:

• There is no content repeated on multiple pages.

The product was tested for:

• Pages have a meaningful title specified in the element.

Exception:

• No meaningful title is specified in the element of the Vital Signs Component. (CHARTING-41441)
• No meaningful title is specified in the element of the Vitals Interop Component. (CHARTING-41442)

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 the Modern Vitals detail pane, focus order is impacted when the first result within the section is expanded. (CHARTING-41392)
• In the Vitals Interop detail pane, focus order is impacted when the first result within the section is expanded. (CHARTING-41380)
• In the Vitals Interop data grid, focus order is disrupted on tabbing from one cell to the next. (CHARTING-41380)
• The checkbox in the Vitals Interop data grid cannot be focused via keyboard. (CHARTING-41380)

The product was tested for:

• The text of links and their surrounding paragraph, list, or table cell is sufficient to describe their purpose.

The product was tested for:

• Pages are fully inter-linked to each other.
• Page contains controls that enable reaching all pages.

The product was tested for:

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

Exception:

• There is no descriptive header for pending outside records in the Interop detail pane. (CHARTING-41475)

The product was tested for:

• Visual indication of the location of the focus.

Exception:

• The checkbox in the Vitals Interop data grid is not focusable. (CHARTING-41465)
• Limited results cause the focus to shift out of the detail pane when the detail pane size is minimal. (CHARTING-41468)

The product was tested for:

• The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

The product was tested for:

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

The product was tested for:

• There are no single pointer operations.

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:

• All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.
• Dragging movements are essential.
• The functionality of dragging movements are determined by the platform and not modified by the author.

The product was tested for:

• Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.

The product was tested for:

• Properly set lang attribute for each page.

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:

• Navigation elements have consistent order when repeated within software programs.

Exception:

• The order of repeated components is inconsistent between the Modern Vitals flowsheet and the Vitals Interop data grid. (CHARTING-41491)

The product was tested for:

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

Exception:

• The calendar image is inconsistently identified across the component. (CHARTING-41402)

The product was tested for:

• None of the following help mechanisms exist: Human contact details, human contact mechanisms, self-help options, automated contact mechanisms.

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.

Exception:

• No label or instruction is provided for the checkbox to import a result within the Vitals Interop data grid (CHARTING-41488)

The product was tested for:

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

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.

The product was tested for:

• Information previously entered by or provided to the user that is required to be entered again in the same process is auto-populated by the application.
• Information previously entered by or provided to the user that is required to be entered again in the same process is available for the user to select.
• Previously entered information is not valid at the time that the user is asked re-enter the information.

The product was tested for:

• A mechanism is available to assist the user with any authentication step that utilizes a cognitive functional test.

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.

Exception:

• Incorrect name and role defined to the Vital Signs flowsheet result cell. (CHARTING-41422)
• Interactive controls are nested in the Vitals Interop data grid. (CHARTING-41424)
• No accessible name for Imperial, Metric, and Modify buttons in the Vitals component. (CHARTING-41458)
• No accessible name for the Dismiss and Add buttons in the Vitals Interop component. (CHARTING-41459)

The product was tested for:

• Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

The product documentation describes:

• Accessibility modes, either at installation or runtime.
• Special keystrokes needed to operate controls.
• Workarounds.

Exception:

• The product documentation does not convey the users about the accessibility and compatibility features. (CHARTING-41348)

Product documentation is in electronic format.

Oracle Global Customer Support can provide information about accessibility features of the product.

Oracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle 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. An Oracle Support engineer will respond to technical issues according to the standard service request process.