Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Live Experience Cloud Mobile Demo App 19.4

Product Description:

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

This VPAT covers the Oracle Live Experience Mobile Demo Application (App) for Android and iOS. intended for demonstrating the Live Experience user interface components.

Date:

19-Apr-2019

Archive Note:

This VPAT applies to only version 19.4. It does not apply to any versions of Oracle Live Experience Cloud Mobile Demo App after this. This VPAT has been superseded by Oracle Live Experience Cloud Mobile Demo App 19.5.

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 Live Experience Cloud 19.4

Evaluation Methods Used:

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

Accessibility Standards/Guidelines

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

Standard/Guideline	Included In Report
Web Content Accessibility Guidelines 2.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/	Level A - Yes Level AA - Yes Level AAA - No
Section 508 as published in 2017, at https://www.Section508.gov	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.
Supports with Exceptions: 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.0 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.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports	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 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 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 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 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 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 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 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 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.4.1 Use of Color(Level A)	Supports with Exceptions	The Android UI 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 Exceptions: 29509231 : 1.4.1 Mobile Demo App: only color is used to show the selected Menu item under main menu The iOS UI 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)	Supports	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)	Supports with Exceptions	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: Android Mobile Demo App: Contrast issues - short code call 29500863 - 1.4.3: Android Mobile Demo App: Contrast issues - during call 29500746 - 1.4.3: Android Mobile Demo App: Contrast issues - hamburger, home page and settings page 29647458 - 1.4.3: Android Mobile Demo App: KYC:contrast issues in type of document select page 29647769 - 1.4.3: Android Mobile Demo App::KYC:contarst issues in check readability page and capture face page 29647683 - 1.4.3: Android Mobile Demo App::close button has contrast issues in verification failed screen 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 Mobile Demo App: contrast issue in call widget page 29507448 - 1.4.3 : ios Mobile Demo App: COLOR contrast issue in demo app 29507933 - 1.4.3 : ios Mobile Demo App: contrast issue in many places (notifications, screenshare stop banner) 29508011 - 1.4.3 : ios Mobile Demo App: contrast issue in the popups 29648133 - 1.4.3 : ios Mobile Demo App: contrast issues in many pages.
1.4.4 Resize text(Level AA)	Supports	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 Android UI was tested for: Images of text are not used The iOS UI was tested for: Images of text are not used
2.1.1 Keyboard(Level A)	Supports with Exceptions	The Android UI was tested for: Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes Proper operation of unique keystrokes and access keys, including those listed in the product documentation The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms) Exception: 29478844 - 2.1.1 Android Mobile Demo App: Collab call - Keyboard navigation should not focus on element that is behind the screen The iOS UI was tested for: Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes Proper operation of unique keystrokes and access keys, including those listed in the product documentation The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms) Exceptions: 29491915 - 2.1.1 ios Mobile Demo App: after call estbalish voice over does not work(voice over+ keyboard navigation) 29507340 - 2.1.1 ios Mobile Demo App: personnel shopper: the focus is not moving to local video window( voiceover+navigation) 29507782 - 2.1.1 ios Mobile Demo App: Keyboard navigation should not focus on element that is behind the screen (voiceover+keyboard navigation) 29648902 - 2.1.1 ios Mobile Demo App: the voice over reading KYC as kaic( voice over) 29641368 - 2.1.1 ios Mobile Demo App: In almost done page the close(x) button read out as just button 29538550 - 2.1.1 ios Mobile Demo App: appropriate button name should be given for call button after call initiated(voice over+ keyboard navigation)
2.1.2 No Keyboard Trap (Level A)	Supports	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.2.1 Timing Adjustable(Level A)	Not Applicable	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 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 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)	Not Applicable	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 Android UI was tested for: The name of the software application is meaningful Names of the scenarios realized by the application are meaningful and accurate The iOS UI was tested for: The name of the software application is meaningful Names of the scenarios realized by the application are meaningful and accurate
2.4.3 Focus Order(Level A)	Supports	The Android UI was tested for: Logical movement through the focusable components using Talkback, in an order that follows a meaningful sequence 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)	Not Applicable	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 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)	Supports with Exceptions	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 Exceptions: 29649866 - 2.4.6 : Android Mobile Demo App::identity card, driving license and passport buttons are not reading as buttons 29478873 - 2.4.6 : Android Mobile Demo App:: Collab call, Remote support screen - six buttons are read as 'unlabelled' 29478884 - 2.4.6 : Android Mobile Demo App:: DAE avatar should be called out appropriately 29478827 - 2.4.6 : Android Mobile Demo App:: Reads as 'unlabelled' for the 'agent name, Duration' box 29628604 - 2.4.6 : Android Mobile Demo App::KYC scenario -the close button is not reading out properly( voice assistant). 29639831 - 2.4.6 : Android Mobile Demo App::KYC scenario:The focus is not moving to elements in verification failed screen(voice assistant+ keyboard navigation) 29649927 - 2.4.6 : Android Mobile Demo App::KYC:the voice over reading KYC as kaic( voice Assistant) 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 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
3.1.1 Language of Page(Level A)	Supports	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)	Not Applicable	The Android UI: Passage or phrases are in same language as that of the parent page, which inturn is in the locale/language of the underlying platform The iOS UI: Passage or phrases are in same language as that of the parent page, which inturn is in the locale/language of the underlying platform
3.2.1 On Focus(Level A)	Supports	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 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 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 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)	Supports	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)	Supports	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 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 Android UI was 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 iOS UI was 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	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)	Supports	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

2017 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 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	Supports with Exceptions	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 iOS Mobile Demo App: 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 Android UI was tested for: No caption controls are provided The iOS UI was tested for: No caption controls are provided Exceptions: 29512315 - 503.4.1 No user control for selection of captions
503.4.2 Audio Description Controls	Not Applicable	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
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 referenced on the Oracle Live Experience Cloud VPAT describes the accessibility features of the operating system and browser tool shortcuts. See section 2-7 Dependencies. Refer to the article "Live Experience Accessibility" from the Get Started section: https://docs.oracle.com/cloud/live-experience-cloud/live-experience-get-started.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.