Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Health Clinical Digital Assistant 2024

Product Description:

Oracle Health Clinical Digital Assistant provides Oracle Health EHR customers with a mobile app that includes a clinical virtual assistant, voice dictation, and ambient capabilities to providers. The Oracle Health Clinical Digital Assistant will have quick access to on-the-go information such as Schedules, Upcoming Patient Summaries, Reminders, and more. It can be used to ask for information regarding the patient, their lab results, medications, and other important patient information. Most interactions result in a multimodal display of the information and a summarized read-out of the information. The provider can interact with this information using hand gestures (such as pinch, zoom, tap/select, double tap) or voice (ex, "show me the serum creatinine levels"). If Oracle Health Clinical Digital Assistant requires disambiguation or additional slot-filling, the dialog will be optimized to 1-2 prompts on the multimodal display.

Date:

13-May-2024

Contact Information:

accessible_ww@oracle.com

Dependent Products

This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Oracle Health & AI Product Documentation Cerner Wiki 8.5.4

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/Guideline	Included In Report
Web Content Accessibility Guidelines 2.1	Level A - Yes Level AA - Yes Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018	Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports: The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Partially Supports: Some functionality of the product does not meet the criteria.
Does Not Support: Majority of functionality of the product does not meet the criteria.
Not Applicable: The criteria are not relevant to the product.

WCAG 2.1 Report

Table 1 also documents conformance with:

Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports	The HTML 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. 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 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 Images that are decorative are marked with "setIsAccessibilityElement:NO" 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 native Android product was tested for: Images that convey information such as ImageView and ImageButton objects have meaningful alternative text using the android:contentDescription XML attribute for static elements and the setContentDescription() method for dynamic elements. Images that are decorative have the android:contentDescription XML attribute set to "@null". 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.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.4 Captions (Live) (Level AA)	Not Applicable	The product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	The product has no multimedia.
1.3.1 Info and Relationships (Level A)	Supports	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. 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. The native Android product was tested for: User interface component labels are associated with the fields they are labeling. Headings are marked as such using the accessibilityHeading attribute. Tables are contained in a Table component.
1.3.2 Meaningful Sequence(Level A)	Supports	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. The native Android product was tested for: The TalkBack reading/presentation sequence matches the logical reading sequence.
1.3.3 Sensory Characteristics(Level A)	Supports	The HTML and native iOS/Android 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.
1.3.4 Orientation (Level AA)	Supports	The HTML and native iOS/Android product were tested for: A fixed display orientation is required for essential functionality.
1.3.5 Identify Input Purpose (Level AA)	Supports	The HTML and native iOS/Android product were tested for: Text fields which collect information about the user contain the appropriate autocomplete content attribute.
1.4.1 Use of Color(Level A)	Supports	The HTML and native iOS/Android 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.
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Supports	The HTML and native iOS/Android 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.
1.4.4 Resize text(Level AA)	Supports	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 native Android product was tested for: Text can be resized up to 200% without loss of content or functionality using the Android Zoom feature.
1.4.5 Images of Text(Level AA)	Supports	The HTML and native iOS/Android product were tested for: Images of text are not used.
1.4.10 Reflow (Level AA)	Supports	The HTML product is available through the mobile user interface. Due to mobile devices not supporting reflow, this criteria is always met.
1.4.11 Non-text Contrast (Level AA)	Supports	The HTML and native iOS/Android product were tested for: Non-text items have a contrast ratio of at least 3:1.
1.4.12 Text Spacing (Level AA)	Supports	The HTML and native iOS/Android 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.
1.4.13 Content on Hover or Focus (Level AA)	Supports	The HTML and native iOS/Android product were tested for: There is no content that appears on hover or focus.
2.1.1 Keyboard(Level A)	Supports	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 and Android products were 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.
2.1.2 No Keyboard Trap (Level A)	Supports	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 native Android 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 TalkBack and Switch Control assistive technologies.
2.1.4 Character Key Shortcuts (Level A)	Supports	The HTML and native iOS/Android product were tested for: There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)	Supports	The HTML and native iOS/Android product were tested for: Time limits in the product can be extended with at least 20 seconds warning up to 10 times.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The HTML and native iOS/Android product were tested for: There is no moving, blinking, scrolling or auto-updating content.
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The HTML and native iOS/Android product were tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
2.4.1 Bypass Blocks(Level A)	Supports	The HTML product was tested for: 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 native iOS/Android product was tested for: 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.
2.4.2 Page Titled(Level A)	Supports	The HTML and native iOS/Android product were tested for: Pages have a meaningful title specified in the <title> element.
2.4.3 Focus Order(Level A)	Supports	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 built-in screen reader. The native Android product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence using a connected Bluetooth keyboard, along with the built-in screen reader.
2.4.4 Link Purpose (In Context)(Level A)	Supports	The HTML and native iOS/Android product were 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.
2.4.5 Multiple Ways(Level AA)	Supports	The HTML product was tested for: The product does not contain multiple pages. The native iOS/Android app product was tested for: 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.
2.4.6 Headings and Labels(Level AA)	Supports	The HTML and native iOS/Android product were tested for: Headers describe the topic or purpose of the content below them. Labels describe the purpose of the associated field.
2.4.7 Focus Visible(Level AA)	Supports	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 native Android product was tested for: Visual indication of the location of the focus using TalkBack to display a focus indicator.
2.5.1 Pointer Gestures (Level A)	Supports	The HTML and native iOS/Android product were tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Supports	The HTML and native iOS/Android product were 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.
2.5.3 Label in Name (Level A)	Supports	The HTML and native iOS/Android 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.
2.5.4 Motion Actuation (Level A)	Supports	The HTML and native iOS/Android product were tested for: There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)	Supports	The HTML product was tested for: Properly set lang attribute for each page. The native iOS/native Android product was tested for: Properly set language property, where it differs from that of the underlying platform using the *accessibilityLanguage* property.
3.1.2 Language of Parts(Level AA)	Supports	The HTML product was tested for: There are no passages of text that are different from the language of the page. The native iOS/native Android product was tested for: There are no passages or phrases where the language differs from that of the application/platform.
3.2.1 On Focus(Level A)	Supports	The HTML and native iOS/Android 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.
3.2.2 On Input(Level A)	Supports	The HTML and native iOS/Android 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.
3.2.3 Consistent Navigation(Level AA)	Supports	The HTML product was tested for: There are no navigational mechanisms that are repeated. The native iOS/native Android product was tested for: 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.
3.2.4 Consistent Identification(Level AA)	Supports	The HTML and native iOS/Android product were tested for: Images and controls are used and identified consistently throughout the product.
3.3.1 Error Identification(Level A)	Supports	The HTML and native iOS/Android 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.
3.3.2 Labels or Instructions (Level A)	Supports	The HTML and native iOS/Android product were tested for: Labels or instructions are provided when the product requires user input.
3.3.3 Error Suggestion (Level AA)	Supports	The HTML and native iOS/Android product were tested for: Where suggestions for fixing an input error are known, they are provided to the user.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The HTML and native iOS/Android 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.
4.1.1 Parsing(Level A)	Supports	The HTML product was tested for: This criterion is always satisfied for any content using HTML or XML. The native iOS and Android product were tested for: Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique Ids Markup content validate to the appropriate markup specification(s)
4.1.2 Name, Role, Value (Level A)	Supports	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. The native Android product was tested for: User interface components have a programmatically associated name and role using the label property and appropriate Attributes State information, properties, and values are programmatically exposed for user interface components using the appropriate part of the Android API.
4.1.3 Status Messages (Level AA)	Supports	The HTML and native iOS/Android products were tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of Color	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without Speech	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited Manipulation	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and Strength	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria	Conformance Level	Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive Technology	Heading cell - no response required	Heading cell - no response required
502.2.1 User Control of Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility Features	Partially Supports	The HTML and native iOS/native Android product were tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts. Exception: On Android, TalkBack disrupts the Automatic Speech Recognition feature of the app. (MIECS-55131)
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and Headers	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.4 Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.6 Label Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.8 Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.10 List of Actions	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on Objects	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.14 Event Notification	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Supports	The HTML and native iOS/native Android product were tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor.
503.3 Alternative User Interfaces	Not Applicable	The product does not have assistive technology features.
503.4 User Controls for Captions and Audio Description	Heading cell - no response required	Heading cell - no response required
503.4.1 Caption Controls	Not Applicable	The product has no multimedia.
503.4.2 Audio Description Controls	Not Applicable	The product has no multimedia.
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
602 Support Documentation	Heading cell - no response required	Heading cell - no response required
602.2 Accessibility and Compatibility Features	Supports	The product documentation describes: Accessibility modes, either at installation or runtime. Help documentation is located at: https://wiki.cerner.com/display/public/MG2B/Accessibility+in+Oracle+Health+Clinical+Digital+Assistant
602.3 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support Documentation	Not Applicable	Product documentation is in electronic format.
603 Support Services	Heading cell - no response required	Heading cell - no response required
603.2 Information on Accessibility and Compatibility Features	Supports	Oracle Health Products are supported by several operations teams who can provide accessibility support solutions to customers.
603.3 Accommodation of Communication Needs	Supports	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.

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.