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).
• Controls have an associated name.
• Client-side image maps specify the ALT attribute on each AREA element.
• Non-text characters are not used or have meaningful alternative text.
• CAPTCHAs are not used.

Exception:

• When scheduling a new appointment for a patient, the star icon next to certain appointment types or specialties is missing meaningful alternative text (AWREG-31764).
• When checking in a patient in Patient Tracker, the forms to print are displayed in an embedded PDF viewer. The forms displayed in the PDF viewer do not have alternative text (AWREG-32821).

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 are exposed to assistive technologies where supported by the user agent or other platform software.
• Groups of components are described with a description of the grouping.

Exception:

• When following the check-in process for a patient in Patient Tracker, the Grids used to display patient information are missing accessible text on the Financial Responsibility and Patient Form pages (AWREG-34074).
• When the user navigates from Patient Tracker to the landing page by selecting the O logo, the landing page opens in an overlay which covers the Patient Tracker page. The user is able to access the Patient Tracker content behind the overlay using keyboard navigation and the screen reader (AWREG-34041).
• When selecting a date from the Date Picker in Resource Schedule, the screen reader automatically announces the years and months in the Date Picker even though the year or month is not getting changed. Once the user stops the screen reader from announcing all the years/months, navigating the Date Picker works as expected. (AWREG-32151).

The product was tested for:

• The sequence of elements in the DOM matches a logical reading sequence.

The product was tested for:

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

Exception:

• When scheduling a new appointment for a patient via Calendar View, the Schedule Appointment button text is truncated when the screen is changed to a smaller size like mobile phone size (AWREG-32414).

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:

• In Resource Schedule when using 200% zoom, the Search Resources dropdown is either entirely or mostly hidden. If the user selects the dropdown by tabbing to it they are still able to search and select resources from it (AWREG-33033).

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:

• Content that requires two-dimensional layout only presents scroll bars in the component used
  to present the two-dimensional content.

Exception:

• At 400% zoom, the page's main content is not available when a user tries to schedule a new appointment via the Calendar View (AWREG-32422).

The product was tested for:

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

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.
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms).

Exception:

• When rescheduling an appointment from the patient's profile, the user cannot navigate to the Continue button in the Reschedule Appointment Dialog via keyboard. This issue is only occurs in the Chrome browser. (AWREG-32052).
• When canceling an appointment from the patient's profile, the user cannot navigate to the Cancel Appointment button in Cancel Appointment Dialog via keyboard. This issue is only occurs in the Chrome browser. (AWREG-32026).
• When checking in a patient from Patient Tracker, the user has an option to print the patient's forms. When the user selects the option to print the patient's forms, the documents to print open in an embedded PDF Viewer. If a screen reader is not used, tabbing to the PDF Viewer Toolbar does not work (AWREG-33954).

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 can be turned off.
• Single character keyboard shortcuts can be remapped.
• Single character keyboard shortcuts are only active when that component has focus.

The product was tested for:

• Time limits in the product can be extended with at least 20 seconds warning up to 10 times.
• Time limits used are part of a real-time event, or an essential activity.

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.

Exception:

• The Calendar View page doesn't have a meaningful title as it does not relate to any of the information displayed on the page (AWREG-31854).

The product was tested for:

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

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.

Exception:

• On the patient's Financial Responsibility page, the Add Guarantors link does not have meaningful text (AWREG-31556).

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.

The product was tested for:

• Visual indication of the location of the focus.

Exception:

• When registering a patient via the Create Patient -> Quick registration option or when the patient registers themselves via Self-Registration, the scrollbar is not moving down as the user tabs through the fields on the registration form (AWREG-34081).

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 has been 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:

• Properly set lang attribute for each page.

The product was tested for:

• Proper use of lang attribute for text passages that are in a different language than that 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:

• Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window.
• 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:

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

Exception

• When adding a new patient appointment via the View Calendar -> Schedule option, the user must fill out a form to schedule the appointment. If the user fills out the form incorrectly by missing the Start Time field, and then submits the form by pressing Schedule, the Provider field gets cleared without an error message (AWREG-31884).

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.

The product was tested for:

• 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 always satisfied for any content using HTML or XML.

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.

Exception:

• When adding a New Block from Resource Schedule, the screen reader cannot read the value of the Resource Search dropdown nor the helper text in the date time fields (AWREG-32185).
• When adding a new appointment for a patient, the screen reader does not announce how to interact with the appointment time suggestions even though the user can tab through the suggestions and use the spacebar or enter key to select one. This is due to the appointment time suggestions not containing the proper role (AWREG-31827).
•  When scheduling a new appointment for the patient, a list of appointment time suggestions are displayed. Each appointment time suggestion card is missing the expected ARIA child roles (AWREG-34054).
• When an appointment is canceled in Patient Tracker, the Cancelation Reason must be filled out prior to canceling. When the Cancel button becomes enabled after filling out this field, the screen reader does not announce the button is enabled (AWREG-32241).
• When rescheduling an appointment in Patient Tracker, the Continue button is disabled until the Reschedule Reason field is populated. When the Continue button becomes enabled after filling out this field, the screen reader does not announce the button is enabled (AWREG-32227).
• When a patient uploads their insurance card in the self-registration workflow, the Front of Insurance dialog has the wrong title. It's title is incorrectly set as Back of the Drivers License. When the dialog opens the screen reader announces this incorrect title (AWREG-34109).

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 removing a block in Resource Schedule, the screen reader does not announce the 'Block Deleted' status message (AWREG-32192).
• When adding a new block in Resource Schedule, the user must fill out a form to create the resource block. If the user does not fill out the required fields and submits the form, they will receive an error message at the top of the form. The screen reader does not announce this error message (AWREG-32178).
• When adding an appointment for a patient via Calendar View, the screen reader does not announce when the provider's schedule has been retrieved (AWREG-31875).
• When adding an appointment for a patient, the user must fill out a form to retrieve appointment time suggestions. If the user submits the form without selecting a time, an error message will appear. The screen reader does not announce this error message (AWREG-31834).
• When adding an appointment for a patient, the screen reader does not announce when appointment times haven't been found (AWREG-31542).
• When searching for patients in View Patients, the screen reader does not announce patient search results (AWREG-31486).

See WCAG section.

The product does not convert files from one format to another.

The product was tested for:

• PDF files conform to PDF/UA-1

The product was tested for:

• Prompts authors to create content that conforms to WCAG 2.0 AA.

The product does not provide templates.

There are no accessibility or compatibility features to document. Product uses standard HTML specifications to support accessibility.

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.