Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Dynamic Documentation Component Desktop 2018.19

Product Description:

Dynamic Documentation automates the creation of a clinical note relating to care delivery. With Dynamic Documentation, the note aggregates chart information from clinical documentation entered using a variety of methods to meet the needs of physicians in varied care settings.

Dynamic Documentation provides the following features:

Narrative-driven documentation focused on keeping you in flow and promoting patient care as the center of focus with documentation aggregated as a by-product of care performed in the chart and along with Workflow MPages views.
Narrative or text-based information can be inserted into the note by typing or through voice recognition support.
Auto Text allows for on-the-fly, personalized, narrative-based documentation to support the clinical document.
Data entry efficiency mechanisms such as automatic data insertion and flexible tools make the note more patient-centered.
Spelling is automatically checked as you type, using a robust medical dictionary.
Flexible formatting tools bring attention to important items and provide a professional and polished completed note.
You can refresh the chart data in the note to ensure that the most up-to-date information is included and to support a multitude of Physician Documentation workflows.
Dynamic Documentation templates are based on industry-standard, web-based technologies, including the ability to tailor to meet the specialized needs of a client site.
Addendum capabilities ensure that the document workflow is completed.

The responses to many of the technical standards are based on functionality provided by underlying technologies; please see the ACR listed in the Product Dependencies section for more information.

Date:

30-Apr-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.

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)	Not Applicable	The Desktop product and the HTML product were tested for: Non-text characters are not used or have a 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 Desktop 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. 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. Groups of components are marked up with their description.
1.3.2 Meaningful Sequence(Level A)	Supports	The desktop product was tested for: The sequence of elements presented by assistive technologies matches a logical reading sequence. The HTML product was tested for: The sequence of elements in the DOM matches a logical reading sequence.
1.3.3 Sensory Characteristics(Level A)	Supports	The Desktop product and the HTML 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.
1.3.4 Orientation (Level AA)	Supports	The Desktop product and the HTML product were tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)	Not Applicable	The desktop product was tested for: Technologies that do not provide attributes that support identifying the expected meaning for the form input data are not in scope for this success criterion. The HTML product was tested for: There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)	Supports	The Desktop product and the HTML product were tested for: Information is not conveyed using color.
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Supports	The Desktop product and the HTML 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 Desktop product and the HTML product were tested for: Text can be resized up to 200 percent without losing content or functionality.
1.4.5 Images of Text(Level AA)	Not Applicable	The Desktop product and the HTML product were tested for: Images of text are not used.
1.4.10 Reflow (Level AA)	Partially Supports	The Desktop product and HTML product were tested for: Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content. Exception: On the Note Editor page, content does not adjust or wrap and an additional scroll bar is required to view the text. (DYNAMICDOC-7443).
1.4.11 Non-text Contrast (Level AA)	Supports	The Desktop product and the HTML 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 Desktop product and HTML 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 Desktop product and the HTML 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.
2.1.1 Keyboard(Level A)	Partially Supports	The Desktop product and the HTML product were 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). Exception: The following elements and controls are not accessible with keyboard. Collapse an Expanded List: In the Note Details and Save Note dialog boxes, the TAB key does not collapse an expanded list in a box. Workaround: Press ALT+UP ARROW to collapse a list in a box. Highlight Option From a List: In the Save Note dialog box, when you press ALT+DOWN ARROW to expand a list in the Type box, an option from the list is not automatically highlighted. Workaround: Use the arrow keys to highlight an option from a list. Select Calendar Icon: The calendar icon, wherever applicable, cannot be selected using the keyboard. Workaround: Press the DOWN ARROW key to open the calendar when the Date box is selected. Select First Item on the Tagged Items List: In the Document Viewing tab, pressing TAB once does not select the first item on the Tagged Items list. Workaround: Press TAB twice to select the first item on the list.(DYNAMICDOC-7448)
2.1.2 No Keyboard Trap (Level A)	Supports	The Desktop product and the HTML product were tested for: Movement of focus through controls only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.
2.1.4 Character Key Shortcuts (Level A)	Supports	The Desktop product and the HTML product were tested for: Single character keyboard shortcuts can be turned off. Single character keyboard shortcuts are only active when that component has focus.
2.2.1 Timing Adjustable(Level A)	Not Applicable	The Desktop product and the HTML product were tested for: Time limits are not used.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The Desktop product and the HTML product were tested for: There is no moving, blinking or scrolling content.
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The Desktop product and the HTML 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 desktop 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. 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.
2.4.2 Page Titled(Level A)	Supports	The desktop product was tested for: The name of the product describes the topic or purpose. The HTML product was tested for: Pages have a meaningful title specified in the <title> element.
2.4.3 Focus Order(Level A)	Supports	The Desktop product and the HTML product were tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence.
2.4.4 Link Purpose (In Context)(Level A)	Supports	The Desktop product and the HTML product were tested for: The text of links and their surrounding paragraph, list, or table cell is sufficient to describe their purpose.
2.4.5 Multiple Ways(Level AA)	Supports	The desktop 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. The HTML product was tested for: The product does not contain multiple pages.
2.4.6 Headings and Labels(Level AA)	Supports	The Desktop product and the HTML 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 Desktop product and the HTML product were tested for: Visual indication of the location of the focus.
2.5.1 Pointer Gestures (Level A)	Not Applicable	The Desktop product and the HTML product were tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Supports	The Desktop product and the HTML 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. When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event.
2.5.3 Label in Name (Level A)	Supports	The Desktop product and the HTML 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)	Not Applicable	The Desktop product and the HTML product were tested for: There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)	Supports	The desktop product was tested for: This application only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable. The HTML product was tested for: Properly set lang attribute for each page.
3.1.2 Language of Parts(Level AA)	Supports	The desktop product was tested for: This application only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable. The HTML product was tested for: There are no passages of text that are different from the language of the page.
3.2.1 On Focus(Level A)	Supports	The Desktop product and the HTML 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 Desktop product and the HTML 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 desktop product was tested for: Navigation elements have consistent order when repeated within software programs. The HTML 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.
3.2.4 Consistent Identification(Level AA)	Supports	The Desktop product and the HTML product were tested for: Images and controls are used and identified consistently throughout the product.
3.3.1 Error Identification(Level A)	Partially Supports	The Desktop product and the HTML product were tested for: Where suggestions for fixing an input error are known, they are provided to the user. Exception: When input errors are detected, they are not described to the user in the Sign/Submit Note dialog (for the Date and Time fields). (DYNAMICDOC-7444).
3.3.2 Labels or Instructions (Level A)	Supports	The Desktop product and the HTML product were tested for: Labels or instructions are provided when the product requires user input.
3.3.3 Error Suggestion (Level AA)	Partially Supports	The Desktop product and the HTML product were tested for: Where suggestions for fixing an input error are known, they are provided to the user. Exception: When input errors are detected, they are not described to the user in the Sign/Submit Note dialog (for the Date and Time fields). (DYNAMICDOC-7445).
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The Desktop product and the HTML product were tested for: Submissions can be reversed by the user. 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	This criterion is considered as always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)	Supports	The desktop product was tested for: Controls have a programmatically associated name. Additional state information is programmatically exposed for controls, such as whether a field is ‘required’. 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.
4.1.3 Status Messages (Level AA)	Not Applicable	The Desktop product and the HTML product were tested for: There are no status messages.

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	Supports	The Desktop product and the HTML product were tested for: Does not disrupt platform accessibility features such as sticky keys, high contrast and large fonts.
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	Not Supported	The Desktop product and the HTML product were tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor. Exception: The product does not respond to platform settings for color, contrast, font type, font size, and focus cursor (DYNAMICDOC-7446).
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	Supports	See WCAG Section.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The Desktop product and HTML product were tested for: Does not generate file conversions.
504.2.2 PDF Export	Not Applicable	The Desktop product and the HTML product were tested for: The product does not support PDF Export.
504.3 Prompts	Partially Supports	This product was tested for: Prompts authors to create content that conforms to WCAG 2.0 AA. Exception: Prompts to enable users to add Alt text to images are not provided (DYNAMICDOC-7447).
504.4 Templates	Supports	This product was tested for: Templates are provided that allow content creation that conforms to WCAG 2.0 AA.

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. Special keystrokes needed to operate controls. Workarounds. Accessibility-related documentation can be found at: (https://wiki.cerner.com/x/D4Y7fQ)
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.