Oracle Accessibility Conformance Report

The HTML product was tested for:

• Images that convey information have meaningful alternative text using ALT.
• 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.
• Text summary or alternative is provided for time-based media.
• 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.

The native iOS product was tested for: 

• Images that convey information have meaningful alternative text using the UIAccessibility Label attribute and are marked with the Image trait
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table) or complex image is a container composed of individual accessible elements
• Controls have an associated name
• Text summary or alternative is provided for time-based media
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

The HTML 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.

The native iOS product was tested for:

• User interface component labels are associated with the fields they are labeling through use of the label's text as the Label trait of the labeled field
• Headings are marked as such using the Heading trait
• Tables are contained in a Table component

Exceptions:

• Logout button is not relayed when it receives focus. (PATESIG-9889)
• When the add forms button is activated, a dialog for adding consent forms appears, but this change is not announced. (PATESIG-9889)
• When the delete form button is activated in procedural consent form list by clinical staff, it triggers the opening of a warning dialog, but the dialog is not announced. (PATESIG-9889)
• When viewing a consent form, the hidden label for the input field where the user enters their name in the text entry box is not announced correctly. (PATESIG-9889)

The HTML product was tested for:

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

The native iOS product was tested for:

• The VoiceOver reading/presentation sequence matches the logical reading sequence

Exceptions:

• The contents of the Demographic Banner are not announced in the expected top-to-bottom and left-to-right sequence. (PATESIG-9724)

The HTML and native iOS product were 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 HTML and native iOS product were tested for:

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

The HTML and native iOS product were tested for:

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

The HTML and native iOS product were 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
• Information is not conveyed using color

Exceptions:

• When viewing a form, there are form fields highlighted in blue, the fields that are not highlighted indicate they are disabled but there is no other visual means for conveying this information. (PATESIG-9725)

The HTML and native iOS product were 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:

• On the Registration List Home Page, when viewing the list of patients, the "Filter by" placeholder text and the MRN and FIN sub-texts have a ratio of 3.5:1. (PATESIG-9726)
• On the Form Selection page, when viewing the list of forms that have been previously completed, the sub-text "Completed" has a ratio of 4.2:1. (PATESIG-9726)

The HTML product was tested for:

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

The native iOS product was tested for:

• Text can be resized up to 200% without loss of content or functionality using the iOS Zoom feature.

The HTML and native iOS product were tested for:

• Images of text are not used.

The HTML product was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.
• An alternative mobile user interface is available and is accessed from the main application.
• Content that requires two-dimensional layout only presents scroll bars in the component used
  to present the two-dimensional content.

Due to mobile devices not supporting reflow, this criteria is always met.

Exceptions for HTML:

• When the Follow-up Patient List is viewed at 400% zoom the 'user utility menu' is truncated. (PATESIG-9727)

The HTML and native iOS product were tested for:

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

The HTML and iOS product were 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.

Exceptions:

• In the Patient Follow-Up List there is a utility menu, and the close button within the menu is not fully visible. (PATESIG-9728)

The HTML and native iOS product were 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 HTML 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).

The native iOS product was tested for:

• Ability to perform functions from the keyboard only.
• Logical movement of focus through the controls.
• Proper operation of unique keystrokes, including those listed in the product documentation.

Exceptions:

• The Patient Follow-Up List contains a utility menu that does not get focus when accessed via arrow keys on desktop workflows. (PATESIG-10048)
• When accessing the Patient Follow-Up List in desktop workflows, and use of the security options within the utility menu, the options are selected using the Enter or Space key, however the menu collapses but fails to redirect the user to the designated settings page. (PATESIG-10048)
• When accessing in desktop and reviewing procedural consent forms, the edit and delete buttons within the list box are not accessible. (PATESIG-10048)
• At the end of the “Present to Patient” workflow, certain elements such as save all forms and review all forms in the forms submitted dialog are not keyboard accessible. (PATESIG-10048)
• Patient List features a 'Skip to Content' button that does not respond to the enter or space key. (PATESIG-10048)

The HTML 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 native iOS 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 using the built-in VoiceOver and Switch Control assistive technologies.

The HTML and native iOS product were tested for:.

• There are no single character keyboard shortcuts.

The HTML and native iOS product were tested for:

• Time limits in the product can be adjusted to at least 10 times longer before encountered.

The HTML and native iOS product were tested for:

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

The HTML and native iOS product were tested for:

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

The HTML 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.

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 for the native iOS native product.

The HTML and native iOS product were tested for:

• Pages have a meaningful title specified in the element.

Exceptions:

• Patient Follow-up List contains an empty title attribute. (PATESIG-9731)

The HTML product was tested for:

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

The native iOS product was tested for:

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence using the appropriate platform-specific technique for this, e.g. via a connected Bluetooth keyboard for touch devices, along with the built-in screen reader.

Exception:

• Depending on form design and field elements, when accessing via desktop workflow, tabbing through the interactive elements may results in certain input fields being overlooked and skipped. (PATESIG-9732)

The HTML and native iOS product were tested for:

• Links are not used in the product.

The HTML product was tested for: 

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

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 for the native iOS/native Android product.

The HTML and native iOS product were tested for:

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

Exceptions:

• The search field in the 'add procedural forms' section lacks a visual label. (PATESIG-9734)

The HTML product was tested for:

• Visual indication of the location of the focus.

The native iOS product was tested for:

• Visual indication of the location of the focus using VoiceOver to display a focus indicator.

The HTML and native iOS product were tested for:

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

Exception:

• When using voice over in the present to patient flow, when the signature capture component is open, user interface components that are behind the signature capture component can be accessed. (PATESIG-8733)

The HTML and native iOS product were tested for:

• The multipoint or path-based gesture actions are essential e.g. signatures.

The HTML and native iOS product were tested for:

• 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

The HTML and native iOS product were 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.

Exceptions:

• The "Home" button, “Info” icon button and the "Add" button is identified merely as "button" and “unlabeled zero button.” (PATESIG-9736)

The HTML and native iOS product were tested for:

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

The HTML and native iOS product were tested for:

• There is no functionality that requires dragging movements.

The HTML and native iOS product were 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 HTML product was tested for:

• Properly set lang attribute for each page.

The native iOS product was tested for:

• Application is in the locale/language of the underlying platform.
• Properly set language property, where it differs from that of the underlying platform using the accessibilityLanguage property.

The HTML product was tested for:

• There are no passages of text that are different from the language of the page.

The native iOS product was tested for:

• There are no passages or phrases where the language differs from that of the application/platform.

The HTML and native iOS product were 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 HTML and native iOS product were 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.

The HTML product was tested for:

• There are no navigational mechanisms that are repeated.

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 for the native iOS/native Android product.

The HTML and native iOS product were tested for:

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

The HTML and native iOS product were tested for:

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

The HTML and native iOS product were tested for:

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

The HTML and native iOS  product were tested for:

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

The HTML and native iOS product were tested for:

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

The HTML and native iOS product were 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

The HTML and native iOS product were tested for:

• Re-entering information previously entered by or provided to the user is essential.

The HTML and native iOSproduct were tested for:

• The product supports password entry by password managers.

The HTML 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.

The native iOS product was tested for:

• User interface components have a programmatically associated name and role using the UIAccessibility Label property and appropriate Attributes.
• State information, properties, and values are programmatically exposed for user interface components using the appropriate part of the UIAccessibility API.

Exceptions:

• Patient Follow-up List contains a utility menu when interacted with behaves as follows:
  • It does not have it's expanded or collapsed state announced.
  • The first item within the utility menu is not receiving keyboard focus when it gets expanded.
  • There is no announcement of the menu's title or items within the menu that are selected or unselected.
  • As menu contains list items but are not announced. (PATESIG-9737)
• Patient Follow-up List features an utility menu which contains options with sub menu options. The 'settings' list option contains sub menu item that is not announced.
  • Visually also there is no indication that the 'settings' option has sub menu. (PATESIG-9737)

The HTML and native iOS product were tested for:

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

Exceptions:

• When the form is saved and closed, a success message appears which is not announced. (PATESIG-9738)
• When consent forms are submitted through a "Present to Patient" button, the confirmation dialog is not announced. (PATESIG-9891)

The native iOS product was tested for:

• Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts.

The iOS product was tested for:

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

Exceptions:

• Application text does not respond to font size changes at the iOS platform level. (PATESIG-10320)

The product documentation describes:

• Special keystrokes needed to operate controls.

Accessibility-related documentation can be found on the Accessibility in Mobile Applications page.

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.