Oracle Accessibility Conformance Report

• 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:

• 29308089 - 1.1.1 Associate Desktop UI (DAEUI): Firefox (FF) only Short code image - image elements should have alternate text
• 29653861 - 1.1.1: DAEUI Know Your Customer (KYC) : Image element doesn't have alternate text
• 29633843 - 1.1.1: DAEUI issues- ensure img elements have alternate text
• 29784062 - 1.1.1: Distribution Partner Tenant - Ensure image elements have alternate text error
• 29900071 - 1.1.1: Meeting: Diagnostics - Image elements do not have alternate text
• 30065391 - 1.1.1 Meeting - Ensures <img> elements have alternate text in diagnostic page

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

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

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

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

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

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

• 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 

Exceptions: 

• 29389468 - 2.4.6 Admin UI - Rows in the table is read by screenreader as column 1 row 1
• 29892853 - 2.4.6 Admin UI - Settings toolbar items missing label

• 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

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

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

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

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

• 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
• 29304099 - 1.4.3 DAEUI: Chrome only Available text contrast error
• 29321017 - 1.4.3 DAEUI: Context attributes URL contrast issue in chrome
• 29308118 - 1.4.3 Meeting: FF only Open meeting link Start and Cancel buttons - contrast issues
• 29308108 - 1.4.3 Meeting: FF only Open meeting link log in text - contrast issues
• 29308144 - 1.4.3 Meeting: Meeting exit session - contrast issues
• 29603866 - 1.4.3 Admin UI Contrast Issues
• 29322194 - 1.4.3 OHC Docs Contrast issues in OHC template and footers
• 29633719 - 1.4.3 DAE UI: Contrast issues
• 29628136 - 1.4.3 AdminUI (KYC) : Error in colour contrast for Jumio button text On/Off
• 29648272 - 1.4.3 WebComponent: Contrast related issues
• 29784022 - 1.4.3: Distribution Partner Tenant - Multiple issues related to Contrast
• 29905906 - 1.4.3: Meeting Engagement - Contrast issues in Rule type,Application location, equals boxes
• 29905401 - 1.4.3: Meeting: Contrast issue for 'Device doesn't appear to be compatible' text
• 29892663 - 1.4.3: Distribution Partner Tenant: Usage Report Page contrast issues for multiple elements
• 30065420 - 1.4.3 Meeting - contrast issue in meeting diagnostic page

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

• 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

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

• 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) 

• 29315299 - 2.1.1 DAE in Chrome - Pressing enter on Swap video button does not work when ScreenReader is ON
• 29310052 - 2.1.1 Admin UI - Cannot navigate to Users Breadcrumb
• 29308820 - 2.1.1 Admin UI in FF - Pressing enter does not work when focus is on Cancel and continue editing
• 29492873 - 2.1.1 DAE - Keyboard navigation unable to access cancel button post deleting avatar
• 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 Component 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)
• 29905312 - 2.1.1 Admin UI: Can't navigate to some options and rows in Engagement scenarios page
• 30041049 - 2.1.1 DAE: press 'Enter' on Done button in share a meeting dialogue not closing the pop up.

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

• 29478844 - 2.1.1 Android MCE: 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
• Logical movement of focus through the controls
• Proper operation of unique keystrokes, including those listed in the product documentation

• 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) 

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

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.

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

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

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.

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

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

• 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

• 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

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.

• Headers describe the topic or purpose of the content below them    
• Labels describe the purpose of the associated field 

• 29328474 - 2.4.6 DAE UI - Screenreader description for resize panel is not correct
• 29309366 - 2.4.6 Admin UI - Chrome only Transcript acknowledgement note contents not read out
• 28980994 - 2.4.6 WebComponent Shortcode - Tap to share your screen with representative msg is not read out
• 29632854 - 2.4.6 Firefox Admin UI - collection of minor screenreader issues in the admin UI in Firefox browser
• 29389468 - 2.4.6 Admin UI: Rows in the table is read by screenreader as column 1 row 1
• 29632701 - 2.4.6 Chrome Admin UI - Issue regarding screen reader and keyboard navigations
• 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: screenreader 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 WebComponent - Maximize button misidentified, Share button mishighlighted, Short Code not read out
• 29709966 - 2.4.6 SAFARI Only : WebComponent: background elements are read out through screen reader
• 29784129 - 2.4.6 Distribution Partner Tenant - Screenreader refers to tenant name with tenant name followed by Edit edit settings
• 30049873 - 2.4.6 DAE SMS: screen reader reads the end user number in values and not in sequence of digits
• 30043220 - 2.4.6 AdminUI SMS: screen reader is not reading out the engagement recording name operation as it is a clickable item
• 30041956 - 2.4.6 AdminUI SMS configuration tool tip is not identified and read by the screen reader
• 30036497 - 2.4.6 MAC safari only:DAE - keyboard is not navigating on start meeting and generating meeting link button
• 30034961 - 2.4.6 SCI: Service Cloud LX icon is read as Unlabelled button
• 30034634 - 2.4.6 DAE:screen reader read out incorrectly in share a meeting link pop up.
• 30034320 - 2.4.6 DAE:screen reader read out elements which are not appear on the screen in meeting waiting page
• 30034300 - 2.4.6 DAE:Done button in diagnostics pop up read out as cancel button done
• 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

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

• 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  

The Web UIs were tested for: 

• Properly set lang attribute for pages

        Exception:

• 29308157 - 3.1.1 Meeting: FF only HTML doc has no lang attribute error in end user left the meeting page
• 30065449 - 3.1.1 Meeting - <html> element must have a lang attribute in meeting diagnostic page.

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

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

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

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

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

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

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:

• 29601856 - 3.3.1 Admin UI: Layout table could be confused for a data table by ScreenReaders
• 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 screenreader

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

The Web UIs were tested for:   

• Labels or instructions are provided when the product requires user input

        Exceptions:

• 29308075 - 3.3.2 DAEUI: FF only Collaboration call swap video buttons - form elements has a label error
• 29296101 - 3.3.2 Admin UI: FF only Engagement Report, Team Performance Report mulitple errors - form elements has a label
• 29439877 - 3.3.2 Admin UI: Application tab -Recording - Label/Form issues
• 29452170 - 3.3.2 Admin UI: In Engagement history page,Label/Form issues observed
• 29452225 - 3.3.2 Admin UI: Reports page displays error for missing Labels/Form
• 29452081 - 3.3.2 Admin UI: Security tab - Localization tab - Label/Form issues
• 29601712 - 3.3.2 Admin UI : Setup your password page - ensure form element has a label, multiple errors
• 29601781 - 3.3.2 Admin UI Chrome only: General branding enter custom log url label issue
• 29601658 - 3.3.2 Admin UI: Application Toolbar - Ensure form element has a label error
• 29601677 - 3.3.2 Admin UI: Register application screen - Application name text box, ensure form element has a label error
• 29653646 - 3.3.2 DAEUI: KYC: Ensure verification details button have labels defined
• 29628061 - 3.3.2 DAEUI: KYC: Enable/Disable button doesn't have label + screen reader
• 29653701 - 3.3.2 DAEUI: KYC: Ensure incoming call form element has label
• 29653795 - 3.3.2 DAEUI: KYC: Separator doesn't have label defined
• 29783956 - 3.3.2 Distribution Partner Tenant - Listbox missing label in Landing page
• 29905971 - 3.3.2: TOB: Meeting Engagement - Label issues in Rule type,Application location, equals dropboxes
• 29892727 - 3.3.2: Distribution Partner Tenant: Usage Report page - Screenreader does not read out navigation list items correctly
• 29892702 - 3.3.2: Distribution Partner Tenant: Usage Report page - form element missing label
• 30056207 - 3.3.2: Admin UI Setting page : Forms element should have a label.
• 30056176 - 3.3.2: Admin UI KYC Engagement scenarios : Ensuer the toggle button enable/disable button has label

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

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

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

• 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:

• 29308133 - 4.1.1 Meeting: FF only Meeting structure error
• 29653817 - 4.1.1 DAEUI: KYC : structure has unordered list in dropdown
• 29783982 - 4.1.1: Distribution Partner Tenant - Multiple elements with the same id attribute error, multiple issues
• 30042838 - 4.1.1 DAE SMS: Multiple elements in the page having the same id attribute
• 30065465 - 4.1.1 Meeting - Multiple elements in the page having the same id attribute in meeting diagnostic page
• 30065319 - 4.1.1 DAE - Multiple elements in the page having the same id attribute in meeting waiting page

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

• 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:

• 29304251 - 4.1.2 DAE UI: Chrome only Remote support Stop camera share button has no label or tooltip, triggering a discernible text error
• 29296067 - 4.1.2 Admin UI - General branding - color picker button has no label or tooltip, triggers discernible text error
• 29628614 - 4.1.2 WebComponent KYC :Ensure close button has discernible text
• 29698608 - 4.1.2 DAEUI MAC Safari only: screen reader reads 'Generate a meeting link' as a button
• 29784096 - 4.1.2 Distribution Partner Tenant - User's icon is referred to as Listbox by ScreenReader
• 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
• 30042771 - 4.1.2 DAE SMS: Form element has no label and buttons have no discernible text

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

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.

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.

• No caption controls are provided

• No caption controls are provided

• No caption controls are provided

• 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

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

The product documentation describes the accessibility features of the operating system and browser tool shortcuts.

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

Live Experience documentation is available in electronic format