VPAT - Oracle Health Clinical AI Agent Nursing (Android) 2025.4

Notes:

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/

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.0	Level A - Yes Level AA - Yes Level AAA - No
Web Content Accessibility Guidelines 2.1	Level A - Yes Level AA - Yes Level AAA - No
Web Content Accessibility Guidelines 2.2	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.2 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.2 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 native Android app 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". 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
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 native Android app 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 native Android app was tested for: The TalkBack reading/presentation sequence matches the logical reading sequence.
1.3.3 Sensory Characteristics (Level A)	Supports	The native Android app 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 included a reference to the text alternative of the graphic
1.3.4 Orientation (Level AA)	Supports	The native Android app was tested for: A fixed display orientation (portrait only) is required for essential functionality.
1.3.5 Identify Input Purpose (Level AA)	Supports	The native Android app was tested for: There are no text fields that collect information about the user.
1.4.1 Use of Color (Level A)	Supports	The native Android app 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
1.4.2 Audio Control (Level A)	Not Applicable	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Supports	The native Android app was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 All 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 native Android app 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 native Android app was tested for: Images of text are not used.
1.4.10 Reflow (Level AA)	Supports	Due to mobile devices not supporting reflow, this criteria is always met.
1.4.11 Non-text Contrast (Level AA)	Supports	The native Android app was tested for: Non-text items have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)	Supports	The native Android app 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
1.4.13 Content on Hover or Focus (Level AA)	Supports	The native Android app was tested for: There is no content that appears on hover or focus.
2.1.1 Keyboard (Level A)	Supports	The native Android app 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
2.1.2 No Keyboard Trap (Level A)	Supports	The native Android app 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 native Android app was tested for: There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable (Level A)	Supports	The native Android app was 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 native Android app was tested for: There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold (Level A)	Supports	The native Android app was 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	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 native Android app was tested for: The name of the software application is meaningful.
2.4.3 Focus Order (Level A)	Supports	The native Android app 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
2.4.4 Link Purpose (In Context) (Level A)	Supports	The native Android app was tested for: The text of links and their surrounding paragraph, list, table cell (with marked up table headers), is sufficient to describe their purpose
2.4.5 Multiple Ways (Level AA)	Supports	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 native Android app was 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 native Android app was tested for: Visual indication of the location of the focus using TalkBack to display a focus indicator
2.4.11 Focus Not Obscured (Level AA)	Supports	The native Android app was tested for: The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.
2.5.1 Pointer Gestures (Level A)	Supports	The native Android app was tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Supports	The native Android app 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
2.5.3 Label in Name (Level A)	Supports	The native Android app 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.
2.5.4 Motion Actuation (Level A)	Supports	The native Android app was tested for: There are no functions that require motion of the device.
2.5.7 Dragging Movements (Level AA)	Supports	The native Android app was tested for: There is no functionality that uses dragging movements.
2.5.8 Target Size (Minimum) (Level AA)	Supports	The native Android app 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.
3.1.1 Language of Page (Level A)	Supports	The native Android app was tested for: Application is in the locale/language of the underlying platform.
3.1.2 Language of Parts (Level AA)	Supports	The native Android app 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 native Android app was tested for: When an element receives focus, it does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window
3.2.2 On Input (Level A)	Supports	The native Android app was tested for: Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of focus, or the spawning of a new screen
3.2.3 Consistent Navigation (Level AA)	Supports	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 native Android app was tested for: Images and controls are used and identified consistently throughout the product
3.2.6 Consistent Help (Level A)	Supports	The native Android app was tested for: Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.
3.3.1 Error Identification (Level A)	Supports	The native Android app was 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 native Android app was tested for: Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)	Supports	The native Android app was 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 native Android app 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
3.3.7 Redundant Entry (Level A)	Supports	The native Android app was tested for: There are no occurrences of information that the user needs to enter which has been previously entered.
3.3.8 Accessible Authentication (Minimum) (Level AA)	Supports	The native Android app was tested for: The product supports copy and paste while authenticating.
4.1.1 Parsing (Level A)	Not Applicable	This criterion is considered as always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)	Supports	The native Android app 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 native Android app was 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 native Android app was tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts Exception: Labels and text in form and lists needs to support font size changes applied in the Android settings. Clinical Digital Assistant Framework (CDAF) plugin pages don't respond to text size changes applied in the Android settings. (CDAF-33327, CDAF-33338)
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 native Android app was 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	There are no accessibility or compatibility features to document. Product uses standard HTML specifications to support accessibility.
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 applicable Standards/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.

Oracle Accessibility Conformance Report

Name of Product:

Product Description:

Report Date:

Contact Information: