Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Live Experience Cloud Service 20.8

Product Description:

Oracle Live Experience enables businesses to maximize customer lifetime value with personalized in-app digital engagement that is proactive and contextual.

The following web based user interfaces are covered by this VPAT:

Administration UI
Distribution Partner Tenant Administration UI
Desktop Associate Experience (DAE)
Meeting App
Diagnostics
Product documentation

In addition, a user interface widget (for Android, iOS and Web) intended for embedding in the customer's own application is covered by this VPAT.

Date:

27-Aug-2020

Archive Note:

This VPAT applies to only version 20.8. It does not apply to any versions of Oracle Live Experience Cloud Service after this. This VPAT has been superseded by Oracle Live Experience Cloud Service 21.3.

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 JavaScript Extension Toolkit (JET) 8.0.0 (Updated)

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)	Partially Supports	The Web UIs were tested for: Images that convey information have meaningful alternative text using ALT Images that are decorative are marked up using ALT=”” or CSS background images Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table) Controls have an associated name Text summary or alternative is provided for time-based media Client-side image maps specify the ALT attribute on AREA elements CAPTCHAs include text alternatives that describe the purpose of the non-text content, and provide an alternative CAPTCHA serving the same purpose using a different modality Exceptions: 29633843 - 1.1.1: DAEUI issues- ensure img elements have alternate text The Android UI 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 The iOS UI 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” 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 Web UIs were tested for: No Pre-recorded audio-only or video-only content is being used The Android UI was tested for: No Pre-recorded audio-only or video-only content is being used The iOS UI was tested for: No Pre-recorded audio-only or video-only content is being used
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	The Web UIs were tested for: No Pre-recorded Audio/Video content is being used The Android UI was tested for: No Pre-recorded Audio/Video content is being used The iOS UI was tested for: No Pre-recorded Audio/Video content is being used
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	The Web UIs were tested for: No Pre-recorded Audio/Video content is being used The Android UI was tested for: No Pre-recorded Audio/Video content is being used The iOS UI was tested for: No Pre-recorded Audio/Video content is being used
1.2.4 Captions (Live) (Level AA)	Not Supported	The Web UIs were tested for: No captions are provided on realtime video The Android UI was tested for: No captions are provided on realtime video The iOS UI was tested for: No captions are provided on realtime video Exceptions: 29512680 - Captions not provided for live audio content
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	The Web UIs were tested for: No Pre-recorded Audio/Video content is being used The Android UI was tested for: No Pre-recorded Audio/Video content is being used The iOS UI was tested for: No Pre-recorded Audio/Video content is being used
1.3.1 Info and Relationships (Level A)	Supports	The Web UIs were tested for: User interface component labels are associated with the fields they are labeling 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 Android UI was tested for: User interface component labels are associated with the fields they are labeling Headings are marked as such using the accessibilityHeading attribute Android UI does not use tables The iOS UI 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 iOS UI does not use tables
1.3.2 Meaningful Sequence(Level A)	Supports	The Web UIs were tested for: The sequence of elements in the DOM matches a logical reading sequence The Android UI was tested for: The Talkback reading/presentation sequence matches the logical reading sequence The iOS UI was tested for: The VoiceOver reading/presentation sequence matches the logical reading sequence
1.3.3 Sensory Characteristics(Level A)	Supports	The Web UIs 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 included a reference to the text alternative of the graphic The Android UI 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 The iOS UI 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 Web UI was tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text. The Android UI was tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text. The iOS UI was 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)	Supports	The Web UI was tested for: Text fields which collect information about the user contain the appropriate autocomplete content attribute. The Android UI was tested for: Text fields which collect information about the user contain the appropriate autocomplete content attribute. The iOS UI was 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 Web UIs 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 The Android UI was tested for: Information is not conveyed using color The iOS UI was tested for: Information is not conveyed using color
1.4.2 Audio Control(Level A)	Supports	The Web UIs were tested for: Audio that plays automatically for more than 3 seconds can be paused or stopped The Android UI was tested for: Audio that plays automatically for more than 3 seconds can be paused or stopped The iOS UI was tested for: Audio that plays automatically for more than 3 seconds can be paused or stopped
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	The Web UIs 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: 29315377 - 1.4.3 DAEUI - Set avatar dialog and diagnostics contrast issue 29314668 - 1.4.3 DAEUI Context attributes URL contrast issue in chrome and associate name, Available status contrast issue in Firefox 29321017 - 1.4.3 DAEUI: Context attributes URL contrast issue in chrome 29322194 - 1.4.3 OHC Docs Contrast issues in OHC template and footers 29633719 - 1.4.3 DAE UI: Contrast issues 29648272 - 1.4.3 Web Widget: Contrast related issues 29905401 - 1.4.3: Meeting: Contrast issue for 'Device doesn't appear to be compatible' text 30065420 - 1.4.3 Meeting - contrast issue in meeting diagnostic page 31167877 - 1.4.3 AdminUI: Contrast issues in Engagement and team performance reports The Android UI was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 Other text and images of text have a contrast ratio of at least 4.5:1 Exceptions: 29501006 - 1.4.3: Mobile Component Extension (MCE) UI Contrast issues - short code call 29500863 - 1.4.3: MCE UI Contrast issues - during call The iOS UI was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 Other text and images of text have a contrast ratio of at least 4.5:1 Exceptions: 29506934 - 1.4.3 : ios MCE: contrast issue in call widget page
1.4.4 Resize text(Level AA)	Partially Supports	The Web UIs were tested for: Text can be re-sized up to 200% without loss of content or functionality Exceptions: 27716487 - 1.4.4:UI - paging control not visible while viewing Engagement page in 200% zoom The Android UI was tested for: Text can be resized up to 200% without loss of content or functionality using the Android zoom feature The iOS UI was tested for: Text can be resized up to 200% without loss of content or functionality using the iOS Zoom feature
1.4.5 Images of Text(Level AA)	Supports	The Web UIs were tested for: Images of text are not used The Android UI was tested for: Images of text are not used The iOS UI was tested for: Images of text are not used
1.4.10 Reflow (Level AA)	Supports	The Web UI was tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom. The Android UI was tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom. The iOS UI was tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom.
1.4.11 Non-text Contrast (Level AA)	Partially Supports	The Web UI was tested for: Non-text items have a contrast ratio of at least 3:1 Exceptions: 31496771 - 1.4.11 Admin UI: Graph Bars and pie chart images have non-text contrast issues 31496654 - 1.4.11 Admin UI: "EXPORT TO CSV" button in engagement report has non-text contrast issue The Android UI was tested for: Non-text items have a contrast ratio of at least 3:1 The iOS UI was tested for: Non-text items have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)	Partially Supports	The Web UI 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 1.5 times the font size Spacing following paragraphs to 2 times the font size Letter spacing (tracking) to at 0.12 times the font size Word spacing to 0.16 times the font size Exceptions: 31485890 - 1.4.12 Admin UI: Reporting periods list text spacing issues, truncates menu options 31443694 - 1.4.12 Admin UI: Engagement history page, text spacing issues in a couple of menus where text is not displayed completely 31349304 - 1.4.12 Admin UI: User screen, page numbers are not aligned properly resulting in text spacing errors The Android UI was tested for: Native Mobile Applications does not use a hybrid approach that uses markup languages The iOS UI was tested for: Native Mobile Applications does not use a hybrid approach that uses markup languages
1.4.13 Content on Hover or Focus (Level AA)	Supports	The Web UI was tested for: Dismissable -The content can be dismissed without moving the pointer or keyboard focus Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. The Android UI was tested for: There is no content that appears on hover or focus. The iOS UI was tested for: There is no content that appears on hover or focus.
2.1.1 Keyboard(Level A)	Partially Supports	The Web UIs 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) Exceptions: 29315299 - 2.1.1 DAE in Chrome - Pressing enter on Swap video button does not work when Screen reader is ON 29634430 - 2.1.1 DAE - After deleting avatar, focus does not come back to avatar dialog 29659112 - 2.1.1 Admin UI in FF - blank spaces observed, text field nav issues, unnatural nav sequences, hidden elements read out 29648185 - 2.1.1 Web Widget can't navigate to Good or Excellent buttons to rate call 29658939 - 2.1.1 DAE-SCI in Chrome - invisible elements read out, can't navigate to some elements, like Call options, Context attribute options, and Annotation options 29658334 - 2.1.1 DAE-Siebel Integration - can't navigate to answer call from call pop up 29664102 - 2.1.1 DAE ServiceCloud Integration: Safari - keyboard navigation issues to Menu button and incoming call drop down 29705406 - 2.1.1 DAE ServiceCloud Integration on Mac Safari: invisible elements read out, cannot navigate to some elements 29706111 - 2.1.1 DAE Siebel integration: Safari on Mac - keyboard navigation+screen reader issues 29687450 - 2.1.1 DAE iOS Safari only: Can not navigate to associate status dropdown list( voice over+ keyboard navigation) 29705108 - 2.1.1 DAE iOS Safari only: The focus is on email and password fields but the text can not be entered in text fields 29707553 - 2.1.1 DAE iOS Safari only: Answer button reading out as answer followed by unwanted senetence.. 29707564 - 2.1.1 DAE iOS Safari only: Can not navigate to color palette, eraser and pencil icon 29707558 - 2.1.1 DAE iOS Safari only: Can not navigate to context attributes drag button(...) 29699738 - 2.1.1 DAE iOS Safari only: Can not navigate to share meeting link after clicking start meeting button( voice over+ keyboard navigation) 29771379 - 2.1.1 DAE iOS Safari only: Meeting link should be highlighted as soon as click share meeting button( voice over+ keyboard navigation) 29705115 - 2.1.1 DAE iOS Safari only: The end user name in incoming call pop up is not reading out properly 29702902 - 2.1.1 DAE iOS Safari only: The recording indicator is not reading out properly by voice over[keyboard navigation + voice over] 29699817 - 2.1.1 DAE iOS Safari only: Can not navigate to change password, set avatar,etc.. in the menu options 29905282 - 2.1.1 Mac Safari only - Meeting : can not navigate to texts in the meeting diagnostic page(keyboard navigation+voice over) 30292542 - 2.1.1 Web Widget: keyboard navigation not happening to "position of queue" 30198570 - 2.1.1 DAE Android Chrome: Cannot navigate through items in the call pop menu 30287402 - 2.1.1 DAE FF only: Pressing space bar when focus is on any of the main buttons displayed in home page does not show related dialog 30948949 - 2.1.1 Web Widget: Maximize button reading as minimize, does not highlight when traversed into icon 31037939 - 2.1.1 Web Widget: unable to navigate to cross sign on callback dialog, it closes after 5seconds 31478970 - 2.1.1 Web Widget: callback popup - not able to navigate to country code drop down 31497419 - 2.1.1 DAE - ONEPLUS 6T (Android9) only: can't navigate to ID verification panel, screen reader does not readout 31757051 - 2.1.1 DAE: on Edge and Chrome, can't move ID Verification panel using keyboard The Android UI 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 The iOS UI 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: 29491915 - 2.1.1 ios MCE: after call establish voice over does not work(voice over+ keyboard navigation) 29507340 - 2.1.1 ios MCE: personnel shopper: the focus is not moving to local video window( voiceover+navigation)
2.1.2 No Keyboard Trap (Level A)	Supports	The Web UIs were tested for: Movement of focus can be moved to a component of a page using keyboard, with no "keyboard trap" that prevents focus from moving away from any control The Android UI was tested for: Movement of focus can be moved to a component of a page using keyboard, with no "keyboard trap" that prevents focus from moving away from any control The iOS UI was tested for: Movement of focus can be moved to a component of a page using keyboard, with no "keyboard trap" that prevents focus from moving away from any control
2.1.4 Character Key Shortcuts (Level A)	Not Applicable	The Web UI was tested for: There are no single character keyboard shortcuts. The Android UI was tested for: There are no single character keyboard shortcuts. The iOS UI was tested for: There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)	Supports	The Web UIs were tested for: Time limits used are part of a real-time event, or an essential activity. The Android UI : Time limits are not used. The iOS UI : Time limits are not used.
2.2.2 Pause, Stop, Hide (Level A)	Not Applicable	The Web UIs were tested for: There is no moving, blinking or scrolling content The Android UI was tested for: There is no moving, blinking or scrolling content The iOS UI was tested for: There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The Web UIs were tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz The Android UI was tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz The iOS UI 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	The Web UIs were tested for: A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page. The Android UI: 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 iOS UI: 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 Web UIs were tested for: Pages have a meaningful title specified in the TITLE element. The Android UI was tested for: The name of the software application is meaningful The iOS UI was tested for: The name of the software application is meaningful
2.4.3 Focus Order(Level A)	Partially Supports	The Web UIs were tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence Exceptions : 29702920 - 2.4.3 DAE iOS Safari only: If there is any dialog the focus should not go to control elements present in the outer window 29687567 - 2.4.3 DAE iOS Safari only: Keyboard navigation should not focus on element that is behind the screen (generate meeting link screen) 29699773 - 2.4.3 DAE iOS Safari only: Keyboard navigation should not focus on element that is behind the screen(enter a short code screen)[voiceover+ keyboard navigation] 29705221 - 2.4.3 DAE iOS Safari only: The focus should not move on hidden context attributes 29905460 - 2.4.3: Meeting: Focus goes to Join Meeting button that is disabled and screen reader reads as - Join meeting button, to activate press spacebar 30607216 - 2.4.3 Web Widget: Tabbing on maximize window icon reads background elements 31135071 - 2.4.3 AdminUI: Chrome only - Can not be navigated sequentially across editable text fields The Android UI was tested for: Logical movement through the focusable components using Talkback, in an order that follows a meaningful sequence Exceptions : 29478844 - 2.4.3 Android MCE: Collab call - Keyboard navigation should not focus on element that is behind the screen The iOS UI was tested for: Logical movement through the focusable components using VoiceOver, in an order that follows a meaningful sequence
2.4.4 Link Purpose (In Context)(Level A)	Supports	The Web UIs were tested for: The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose The Android UI was tested for: Links are not used in the product The iOS UI was tested for: Links are not used in the product
2.4.5 Multiple Ways(Level AA)	Supports	The Web UIs were tested for: Pages are fully inter-linked to other pages Page contains controls that enable reaching other pages The Android UI: 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 iOS UI: 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)	Partially Supports	The Web UIs were tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field Exceptions: 29328474 - 2.4.6 DAE UI - Screen reader description for resize panel is not correct 28980994 - 2.4.6 Web Widget Shortcode - Tap to share your screen with representative msg is not read out 29632854 - 2.4.6 Firefox Admin UI - collection of minor screen reader issues in the admin UI in Firefox browser 29652641 - 2.4.6 DAE UI: Screen reader issues in Meeting App, reading out blanks and invisible elements, hightlight 29479029 - 2.4.6 MAE: Change password page fields are read out as Edit box 29652587 - 2.4.6 DAE SCI: screen reader issues in Service Cloud misreading labels, or read as blank 29656297 - 2.4.6 DAE Siebel Integration: screen reader issues on Diagnostics page, DAE landing page, Avatar page, Enter Short Code page 29634475 - 2.4.6 DAEUI - Messages not read out 29647941 - 2.4.6 Web Widget - Maximize button misidentified, Share button mishighlighted, Short Code not read out 29709966 - 2.4.6 SAFARI Only : Web Widget: background elements are read out through screen reader 30034961 - 2.4.6 SCI: Service Cloud LX icon is read as Unlabelled button 30049794 - 2.4.6 DAE: Screen reader not able to read End conversation window provided options 30049769 - 2.4.6 DAE: Screen reader not able read incoming SMS content 30035698 - 2.4.6 DAE: Screen reader not able to read user menu list items 30145778 - 2.4.6 DAE SMS: Screen reader reads SMS number in conversation tab as values and not in sequence of digits 30182630 - 2.4.6 AdminUI: Screen reader reads out 'error' for the color square boxes and none of the items associated with square boxes are read out. 31135019 - 2.4.6 Admin UI: Chrome only - Screen reader does not read hint and icons in chart 31129911 - 2.4.6 Admin UI: Engagement history summary - screen reader reads out blank when traversing between columns in context attribute 31183664 - 2.4.6 Admin UI: Firefox Only - Can't navigate to Video Quality tab using voiceover+screen reader 31349478 - 2.4.6 Admin UI: FF only - Error message is not read out by screen reader The Android UI was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field The iOS UI 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 Web UIs were tested for: Visual indication of the location of the focus The Android UI was tested for: Visual indication of the location of the focus using Talkback to display a focus indicator The iOS UI was tested for: Visual indication of the location of the focus using VoiceOver to display a focus indicator
2.5.1 Pointer Gestures (Level A)	Not Applicable	The Web UI was tested for: There are no multipoint or path-based gesture actions. The Android UI was tested for: There are no multipoint or path-based gesture actions. The iOS UI was tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Not Applicable	The Web UI was tested for: There are no single pointer operations The Android UI was tested for: There are no single pointer operations The iOS UI was tested for: There are no single pointer operations
2.5.3 Label in Name (Level A)	Supports	The Web UI 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. The Android UI 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. The iOS UI 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)	Not Applicable	The Web UI was tested for: There are no functions that require motion of the device. The Android UI was tested for: There are no functions that require motion of the device. The iOS UI was tested for: There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)	Supports	The Web UIs were tested for: Properly set lang attribute for pages The Android UI was tested for: Application is in the locale/language of the underlying platform The iOS UI was tested for: Application is in the locale/language of the underlying platform
3.1.2 Language of Parts(Level AA)	Supports	The Web UIs were tested for: Passage or phrases are in same language as that of the parent page, which in turn is in the locale/language of the underlying browser/platform The Android UI was tested for: Passage or phrases are in same language as that of the parent page, which in turn is in the locale/language of the underlying platform The iOS UI was tested for: Passage or phrases are in same language as that of the parent page, which in turn is in the locale/language of the underlying platform
3.2.1 On Focus(Level A)	Supports	The Web UIs were tested for: When an element receives focus, it does not result in a substantial change to the page The Android UI 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 The iOS UI 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 Web UIs were tested for: Changes in the value of user interface components does not result in a substantial change to the page The Android UI was tested for: Changes in the value of user interface components does not result in a substantial change to the page The iOS UI was tested for: Changes in the value of user interface components does not result in a substantial change to the page
3.2.3 Consistent Navigation(Level AA)	Supports	The Web UIs were 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. The Android UI: 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 iOS UI: 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 Web UIs were tested for: Images and controls are used and identified consistently throughout the product The Android UI was tested for: Images and controls are used and identified consistently throughout the product The iOS UI was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	Partially Supports	The Web UIs were tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred Exceptions: 29478914 - 3.3.1 DAE : Information contents of "Share a Meeting link" and "Generate meeting link" are not read by Voice Assistant 29473749 - 3.3.1 DAEUI: 'Short code not found message' not read by screen reader The Android UI was tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred The iOS UI 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)	Partially Supports	The Web UIs were tested for: Labels or instructions are provided when the product requires user input Exceptions: 30542637 - 3.3.2 DAEUI: Blind call transfer pop-up form elements has a label error 31037971 - 3.3.2 Web Widget: Callback popup window has label error The Android UI was tested for: Labels or instructions are provided when the product requires user input The iOS UI was tested for: Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)	Supports	The Web UIs were tested for: Where suggestions for fixing an input error are known, they are provided to the user The Android UI was tested for: Where suggestions for fixing an input error are known, they are provided to the user The iOS UI 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 Web UIs 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 The Android UI was tested for: Submissions can be reversed by the user The iOS UI was tested for: Submissions can be reversed by the user
4.1.1 Parsing(Level A)	Partially Supports	The Web UIs were tested for: Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs. Pages validate to the HTML specification Exceptions: 29653817 - 4.1.1 DAEUI: KYC : structure has unordered list in dropdown 30042838 - 4.1.1 DAE SMS: Multiple elements in the page having the same id attribute 30281056 - 4.1.1 Admin UI: DAE Outbound InApp calling - Multiple elements with the same id attribute errors 30542676 - 4.1.1 DAEUI: Transfer call pop-up has Multiple elements with the same id attribute errors 31337286 - 4.1.1 Admin UI: Reports page - Landmarks must have unique role error 31485920 - 4.1.1 Distributed Parter Tenant Reports - Landmarks must have unique role error The Android UI was tested for: Markup languages aren't used to generate the user interface The iOS UI was tested for: Markup languages aren't used to generate the user interface
4.1.2 Name, Role, Value (Level A)	Partially Supports	The Web UIs were 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 a meaningful programmatically exposed name Frames have a meaningful title specified in the title attribute Exceptions: 29628614 - 4.1.2 Web Widget KYC :Ensure close button has discernible text 29687482 - 4.1.2 DAE iOS Safari Only: The associate status available and away are reading out as links 29702911 - 4.1.2 DAE iOS Safari Only: The context info button is reading as image[keyboard navigation + voice over] 29705208 - 4.1.2 DAE iOS Safari Only: The notifications are not read out by voice over 30042874 - 4.1.2 DAE SMS: 'Accessible text not defined for table/grid' error in Firefox browser 31477302 - 4.1.2 Web Widget: Mute button missing label (discernible text error) 31604350 - 4.1.2 Parter Admin UI License usgage Reports: Label/form section has error related to accessible name The Android UI 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 iOS UI 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
4.1.3 Status Messages (Level AA)	Supports	The Web UI was tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. The Android UI was tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. The iOS UI 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	Supports	The Web UIs : This criteria does not apply as Live Experience is set of web application that uses standard technologies which run in a browser. The Android UI was tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts. The iOS UI was 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	Partially Supports	The Web UIs : This criteria does not apply as Live Experience is set of web application that uses standard technologies which run in a browser. The Android UI was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor. The iOS UI was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor. Exception: 29505760 - 503.2: Widgets are not proper for font size and text characteristics like Bold while changed in the iOS Setting.
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 Supported	The Web UIs were tested for: No caption controls are provided The Android UI was tested for: No caption controls are provided The iOS UI was tested for: No caption controls are provided Exceptions: 29177645 - 503.4.1 Admin UI: Recording playback - no user control for selection of captions 29512315 - 503.4.1 DAE MCE MAE: No user control for selection of captions
503.4.2 Audio Description Controls	Not Applicable	The Web UIs were tested for: No pre-recorded video is used The Android UI was tested for: No pre-recorded video is used The iOS UI was tested for: No pre-recorded video is used
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 the accessibility features of the operating system and browser tool shortcuts. Refer to the article "Live Experience Accessibility" from the More Info section: https://docs.oracle.com/cloud/live-experience-cloud/live-experience-more-info.htm.
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	Live Experience documentation is available 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 Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication Needs	Supports	Oracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle 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. An Oracle Support engineer 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.