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.
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table).
• Titles for Objects and Applets are provided.
• Controls have an associated name.
• CAPTCHAs are not used.

Exception:

• In the Result Trends graph within Vital Signs, when users move between graph points using the arrow keys, the measurement details shown in the pop-up are not announced correctly to assistive technologies after the graph refreshes. (EHRM-75071)

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

• Across the Patient Portal, data tables and grid structures do not include accessible names or descriptions (such as captions or programmatic labels), making it difficult for users to understand the purpose of the content. This occurs in areas such as the Share Health Record preview and other pages including Health Conditions and Immunizations. (EHRM-81373)

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.
• Instructions provided which refer to graphics include 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.

The product was tested for:

• Text fields which collect information about the user contain the appropriate autocomplete content attribute.

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

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.

The product was tested for:

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

Exception:

• When previewing Consolidated Clinical Document Architecture (CCDA) documents after selecting visits in the Share Health Record workflow, the preview document viewer prevents zooming or text scaling on some devices. This may make it difficult for users who rely on zoom or text scaling to read the CCDA document content. (EHRM-83059)

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.
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

Exceptions:

• On the Home page, elements within the patient switcher overlap with surrounding content, making information difficult to read and interact with. (PP-4267)
• Across multiple pages, content does not fully reflow within the viewport, causing portions of the interface to extend beyond the visible area and requiring additional scrolling to access all content. (PP-3455)

The product was tested for:

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

Exceptions:

• The separator line between items in the side navigation menu does not provide sufficient contrast against the background color. This may make the separator difficult for some users to visually distinguish from the surrounding background. (EHRM-79242)
• Separator lines displayed across various sections of the application do not provide sufficient contrast against the white background. This may make the separators difficult for some users to visually distinguish when navigating through different areas of the interface. (EHRM-79245)

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.
• Information appears on hover or focus using default browser behavior, such as the title attribute of components.

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

Exceptions:

• In the Patient Information section during visit registration, when a user edits a field, keyboard navigation does not allow focus to move to the “Close” link using the Tab key. As a result, keyboard users cannot reach the Close option while editing these fields. (PP-3968)
• On the Forgot Password link, pressing Enter when the link has keyboard focus does not activate the link. This prevents keyboard users from opening the Forgot Password flow from the login page. (OHIPS-17611)
• On the Immunizations page, the tooltip associated with the Sort button is only displayed on mouse hover and is not available when the button receives keyboard focus, preventing users from accessing the tooltip information when navigating by keyboard. (PP-156)

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 in the product can be extended with at least 20 seconds warning up to 10 times.

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:

• A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links.
• WAI-ARIA Landmark elements are used outside of repetitive navigation links.

The product was tested for:

• Pages have a meaningful title specified in the TITLE element.

The product was tested for:

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

Exceptions:

• In the Questionnaires, Messages, Conditions, Visits, Histories, Documents, Results, Profile, Patient Switcher, Today page, payment flows, and portions of the Allergies and Immunizations tables, keyboard navigation using the Tab key moves focus to content that is not interactive. These elements do not perform an action but still receive keyboard focus, causing keyboard users to stop on non-actionable content before reaching the next interactive control. (EHRM-77473, EHRM-79177, EHRM-80315, EHRM-80320, PP-3404, PP-3571, PP-3857, PP-3900, PP-3963, PP-3967, PP-4027, PP-4028, PP-4268, PP-5316, EHRM-74346, EHRM-79179)
• In the Conditions workflow during registration and in profile option workflows, closing a dialog or confirming an action moves keyboard focus to the application menu instead of returning focus to the control that opened the dialog. This causes keyboard users to lose their place in the workflow after the dialog closes. (EHRM-80952, PP-3365, PP-4030, PP-4098)
• In cancel confirmation dialogs within visit and appointment workflows, keyboard focus is not placed on the first interactive element when the dialog opens. Instead of landing on the dialog’s Close (“X”) button, focus moves to another control, such as the “Do not cancel” link. (EHRM-86077, PP-3875)
• On the Help page and in the Reschedule Appointment workflow, some links require two Tab key presses before focus moves to the next interactive element. This creates inconsistent keyboard navigation through page content. (PP-3898, PP-4047)
• In the Access Logs page and the detailed Visit view, keyboard focus does not move to the expected starting point when the new view opens. For example, focus does not automatically move into the Access Logs page, and in the detailed Visit view, navigation does not begin at the Back button. (PP-3888, EHRM-86048)
• In the Allergies workflow, keyboard focus moves out of the frame and does not follow a logical navigation order while modifying the allergies list. (PP-78176)

The product was tested for:

• The text of links and their surrounding paragraph, list, or table cell (with marked up table headers), is sufficient to describe their purpose.

The product was tested for:

• Pages are contained in a "site map."
• Pages can be found using the provided "search" function.
• Pages are in a site table of contents.

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.

Exceptions

• In several areas of the application, the visual keyboard focus indicator may be difficult to see or may disappear while navigating using the keyboard. This behavior has been observed in areas including the Conditions page, the main application menu and submenu, the Home page, the Reschedule Appointment workflow, and the Results page, where the focus indicator may be faint, unclear, or not visible when navigating between elements or rows. (EHRM-74362, PP-3364, PP-3459, PP-3899, PP-3904, PP-3905)

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:

• There is no functionality that uses dragging movements.

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 from the language of the page.

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:

• Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time.

The product was tested for:

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

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:

• In the Immunization section of the questionnaires, the “…” button does not have an accessible label. This may make it difficult for users of assistive technology to understand the purpose of the button when navigating to immunization actions. (EHRM-81844)

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:

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

The product was tested for:

• The product supports password entry by password managers.
• The product supports copy and paste while authenticating.

The product was tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
• Additional state information is programmatically exposed for HTML 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 using the relevant WAI-ARIA or HTML5 attributes.
• Custom controls have a meaningful programmatically exposed name.
• Frames have a meaningful title specified in the title attribute.

Exceptions:

• On the Patient Portal Health Conditions and Immunizations pages, the Sort By dropdown does not indicate which option is currently selected when navigating through the list, making it difficult for users to determine the active sorting selection. (PP-142)

The product was tested for:

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

Exception:

• When a user selects Add to Favorite for a visit, a confirmation notification message appears on the page, but the message is not announced to assistive technology. This may prevent users from being aware that the visit has been successfully added to favorites. (PP-3520)

The product documentation describes:

• special keystrokes needed to operate controls
• workarounds

Accessibility-related documentation can be found at Develop Accessible Oracle JET Apps.

A reference guide for keystrokes and touch gestures can be found at: http://www.oracle.com/pls/topic/lookup?ctx=jetlatest&id=OJACC

User experience specifications, including keyboard shortcuts, keyboard navigation, and other accessibility documentation can be found at http://redwood.oracle.com

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.