Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Service Cloud Agent Browser User Interface 20D

Product Description:

The Oracle Service Cloud Agent Browser User Interface provides agent access from any platform running a browser.  It includes common business functions such as incident, contact, organization, and task management, analytics, dashboards, searching for knowledge, notifications, standard text, attachment uploads, additional charts, home report/dashboard, co-browse, a preview chat, incident collaboration, knowledge advanced authoring, responding to social incidents, slicing for reports, rollups for reports, calculations for reports, auro-refresh for analytics, application integration for chat, knowledge foundation authoring, and a browser control on the workspaces.  This release introduces Propose Answer, Best Answer, Agent Guides, Agent Scripting, Assets, Opportunities, and auto filter for reports features.

Agent Desktop Features not Supported by Browser User Interface:

  • Management and Administrative User Interfaces
  • Outreach
  • Feedback

Customization: it is your responsibility to ensure that any customizations you make to this product conform to your accessibility requirements.

Date:

11-Sep-2020

Archive Note:

This VPAT applies to only version 20D. It does not apply to any versions of Oracle Service Cloud Agent Browser User Interface after this. This VPAT has been superseded by Oracle B2C Service Agent Browser User Interface 22B April 2022.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

  • Co-Browse
  • Incident Collaboration

Dependent Products


This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Evaluation Methods Used:

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

Accessibility Standards/Guidelines

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

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

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

 The product was tested for:

  • Control and input field has an associated label that describes its purpose.
  • Images that convey information have meaningful alternative text using ALT.
  • Images that are decorative are marked up using ALT="".
  • No time based media is used.
  • CAPTCHAs are not used.
  • Non-text characters are not used or have meaningful alternative text.
  • Title for Objects and Applets are provided.
  • Information shown in complex images such as charts is also available in an alternative textual form.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe product has no multimedia.
1.3.1 Info and Relationships (Level A)Partially Supports

The product was tested for:

  • User interface component labels are associated with the fields they are labeling.
  • Row and column headers are identified for all data tables
  • Headings are encoded with HTML heading tags.
  • Data tables specify SUMMARY or CAPTION
  • Layout tables use appropriate markup
  • Groups of components are marked up with their descriptions.
  • Style sheets are used only to change the layout and presentation on the screen.

Exceptions:

  • 25038265: No Summary or Row Header defined on Calendar for any Date fields
  • 26020358: Missing or Empty Label for multi-select component and for Select All check box 
  • 26401258: Screen Reader does not read menu label or menu type when entering dropdown.
  • 26517878: Text read out for Thread editor channel menu is unclear
  • 26890585: The label of the Importance flag button should be improved
  • 26890587: The label of the Importance flag text field is not unique
  • 30370155: Errors are found in Label/Form "Error: Ensures every from element has a label" found on opening rollup dialog box
1.3.2 Meaningful Sequence(Level A)Supports

The product was tested for:

  • The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)Supports

The product 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.
1.3.4 Orientation (Level AA)Supports

The product was tested for:

  • A fixed display orientation is required for essential functionality.
1.3.5 Identify Input Purpose (Level AA)Supports

The product 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 product was tested for:

  • Information conveyed by color or font styles is available in alternative formats, such as shape and text.
  • Information conveyed by color has a contrast ratio of at least 3:1

Reports can be configured by the customers to modify the text font color/size as a result of the data meeting a configured conditional.  In these cases, the customer has configured the reports themselves and will have to ensure the shape and/or font weight address accessibility concerns. 

1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Partially Supports

The product 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:

  • 25038260: Placeholder text does not meet contrast ratio on all pages
  • 25353534: In high contrast (Black) mode: Focused elements in dropdown select boxes do not meet accessibility contrast guidelines
  • 25353536: In high contrast (Black) mode: Focused elements in hierarchical menu boxes do not meet accessibility contrast guidelines
  • 30321704: In high contrast mode, the user cannot find out if the switch control in incident workspace is enabled or disabled
  • 30852990: Chat Login button icon is not visible in high contrast mode
  • 30852994: The Chat button icon is not visible in high contrast mode
  • 30852995: Concluded chat icon is not visible in high contrast mode
  • 31049650: Search icon in transfer/conference dialog is not displayed in high contrast mode
  • 31613857: Chat buttons (transfer, conference, terminate, wrap-up) are not visible in high contrast mode
  • 30852993: Enable Sounds button icon is not visible in high contrast mode
  • 28871448: An error reads "Error: Ensures the contrast between foreground and background colors meets WCAG 2AA contrast ratio thresholds" for Firefox in the Admin UI homepage
  • 28963893: In High Contrast mode, the delete hamburger icon in the Channels list page can not be seen
  • 28963895: In High Contrast mode, the WeChat and Facebook icons in the Select Channels type page can not be seen
1.4.4 Resize text(Level AA)Supports

The product was tested for:

  • Ensure that text can be resized up to 200% without loss of content or functionality.

Note:

  • The user interfaces for individual object types are configured by the customer; it is your responsibility to ensure that these configurations resize appropriately.
1.4.5 Images of Text(Level AA)Supports

The product was tested for:

  • Besides the Oracle logo, images of text are not used.
1.4.10 Reflow (Level AA)Supports

The product was tested for 

  • Content that requires two-dimensional layout only presents scroll bars in the component used 
    to present the two-dimensional content.
1.4.11 Non-text Contrast (Level AA)Supports

The product was tested for:

  • Non-text items have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)Supports

The product 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
1.4.13 Content on Hover or Focus (Level AA)Supports

The product 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.
2.1.1 Keyboard(Level A)Partially Supports

The product was tested for:

  • Ability to perform functions from the keyboard only
  • Logical movement of focus through the controls
  • 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:

  • 28814015: User has to press Enter key twice to open a sub-tab in a workspace
  • 27132277: Currency selector does not have currently selected value in focus when opened
  • 26837050: Can't expand hierarchy fields with keyboard using screen reader
  • 28671045: Recent Items search box down arrow is not accessible via keyboard
  • 27065567: Unable to type anything via keyboard for the recipient picker for forward incident when screen reader is running
  • 27222528: Add button can't be accessed for SLA field in organization workspace using keyboard alone in Safari browser
  • 27222529: Cancel button can't be accessed for SLA viewer using keyboard alone in Safari browser
  • 28316534: For Email custom field and Attribures - Email Icon (enabled/disabled) is not listed in Jaws Form Field dialog, also enabled icon cannot be accessed using only Keyboard
  • 28806141: Legal term page can not zoom with keyboard shortcuts
  • 28806143: Authorize page can not zoom with keyboard shortcuts
  • 29770789: Themes can't be accessed using keyboard only on edge browser
  • 29809490: IE11 Cannot use keyboard to select drop down menu selections
  • 30666499: Datetime Picker - Unable to change the date from the Datetime picker by using up/down Navigation keys - using screen reader.
  • 31479325: the user cannot delete any entry in Recent items via keyboard alone
  • 29222254: Skip navigation button broken when exactly one primary tab is open
  • 30364683: Selected items under the menu field not visible as scroll doesnt work upon hitting 'down/Up arrow' on the list
2.1.2 No Keyboard Trap (Level A)Supports

The product was tested for:

  • Movement of focus through the controls using only the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.
2.1.4 Character Key Shortcuts (Level A)Supports

The product was tested for:

  • Single character keyboard shortcuts are only active when that component has focus.
2.2.1 Timing Adjustable(Level A)Supports

The product was tested for:

  • The user is given a two minute notice before they are logged out when their session expires and they can click a button during those two minutes to remain logged in.  We do not have any other time limits in our application.
2.2.2 Pause, Stop, Hide (Level A)Not Applicable

The product was tested for:

  • There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)Supports

The product 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 product was tested for:

  • A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
  • Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
2.4.2 Page Titled(Level A)Supports

The product was tested for:

  • Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)Partially Supports

The product was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence

Exceptions:

  • 25042820: User must tab backwords to the "add" button after adding note
  • 25859644: Custom Objects:  Send Email icon not accessible using tabs
  • 30365369: Tab key does not navigate between two runtime options in the left panel
  • 28669943: In Firefox, Pressing tab on the recent items settings icon opens up the recent items setting pop up and Search box cannot ne accessed via keyboard alone
  • 29902390: In IE with a screen reader, the Navigation button is read when tabbing from it to the quick search
  • 29902446: After selecting an org or contact from the search control,  the tab position is lost.
  • 30970738: Arrow keys don't work properly for an agent's private message in Agent Browser User Interface
  • 30809113: Chat: Loss of focus indicator
  • 31521277: Improper focus after choosing operator in the slice bucket dialog
  • 26020360: Element with Role option must not have children which take focus on multi-select component
2.4.4 Link Purpose (In Context)(Level A)Supports

The product was tested for:

  • The text of links and their surrounding paragraph, list or table cell (with marked up table headers) is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)Supports

The product was tested for:

  • Pages are fully inter-linked to each other.
  • Page contains controls that enable reaching all pages.
2.4.6 Headings and Labels(Level AA)Partially Supports

The product was tested for:

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

Exceptions:

  • 25108837: Agent Browser UI (BUI) should contain at least one header even when no workspaces are open
  • 25098817: Labels for menu/search fields display twice in Form Field dialog
  • 25108756: Search button labels should be unique
  • 26099461: Forward dialog can lose focus when navigating with keyboard
  • 26863297: Standard text combobox needs a label 
  • 26850223: Agent Browser UI Navigation menu items should not be headers
  • 28000147: No alternative text is present for Primary tick mark image
  • 29972494: Engagement Engine login page needs visible labels for username and password fields
  • 30760076: Engagement Panel version 9 cobrowse:  tooltip / aria label for cobrowse button to be similar to that of video chat button
  • 31013294: Label attribute missing for many fields in Integrations screen
  • 31388756: Collapse, Expand buttons on any top level rollup report are not labeled
2.4.7 Focus Visible(Level AA)Partially Supports

The product was tested for:

  • Visual indication of the location of the focus.

Exceptions:

  • 25102004: Focus lost when an item in selected items panel expanded using keyboard in Hier Menu
  • 29222389: On Mac, focus indicator on primary tab is not a full box around the tab
  • 31022092: Focus on "Menu" not visible when zoomed to 200% in Chrome
  • 31521220: Unable to focus on "Add Bucket" link
2.5.1 Pointer Gestures (Level A)Not Applicable

The product was tested for:

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Not Applicable

The product was tested for:

  • There are no single pointer operations
2.5.3 Label in Name (Level A)Supports

The product was tested for:

  • User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.
2.5.4 Motion Actuation (Level A)Supports

The product was tested for:

  • There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)Supports

The product was tested for:

  • Properly setting the language based on the language setting for the user in the .Net client.
3.1.2 Language of Parts(Level AA)Supports

The product was tested for:

  • Passages or phrases in the content other than proper names and technical terms are rendered in the language specified in the interface.
3.2.1 On Focus(Level A)Partially Supports

The product was tested for:

  • When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window.

Exceptions:

  • 26917155: Screen reader begins reading from the top of the Address Edit dialog box when a value is selected after using the type ahead search
  • 26917204: Screen reader begins reading from the top of the page after typing the enter key to select a currency
  • 26864070: Screen readers should not read "unchecked" after every item in hierarchy fields (product and category)
  • 29766096: Menu filter popup expanded/collapsed state not announced by screen-reader
  • 30107740: Screen reader not reading drop down values properly
  • 30666306: After reading data in each cell of the report, "dot dot section" is read at the end - using screen reader
3.2.2 On Input(Level A)Partially Supports

The product was tested for:

  • In circumstances where changing the value of the components causes a substantial change to the page, warning is given prior to the user interacting with those user-interface components.
  • With Rules, our customers can configure scenarios where user input will shift the context of our application, potentially unexpectedly and unavoidably.

Exceptions:

  • 26850586: An aria-live region should be updated when search process is running and when search results are returned
  • 26887586: An aria-live region should be updated when a tab is closed
  • 31226872: Unable to enter text in the Emoji search field when screen reader is running in chat CKEditor
3.2.3 Consistent Navigation(Level AA)Partially Supports

The product was tested for:

  • Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order 

Exceptions:

  • 26020359: Link > multi-select component list items are present under Link section even though they are not links
3.2.4 Consistent Identification(Level AA)Partially Supports

The product was tested for:

  • Images and controls are used and identified consistently throughout the product.

Exceptions:

  • 28775430: Chat timer being read over and over with a screen reader.
  • 28844148: Chat: Screen reader reads timer (00:00:00) value while live window is open
  • 29533916: Engagement Cloud Chat: No announcement that consumer ended chat
3.3.1 Error Identification(Level A)Partially Supports

The product was tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred

Exceptions:

  • 25720788: Workspace validation errors should be written to the commonArialiveArea of the Agent Browser UI so that they are read by the screen reader
  • 27163363: Read only foreign key fields are not read by Screen readerproperly
  • 30604021: Chat: Space characterbetween timestamp and text not announced.
  • 27336817: Incident is read out as "Incident, one of one" when Add icon on ribbon bar is clicked
  • 27801624: Screen reader just reads column 1 primary, does not read its set or unset
  • 31513661: For disabled buttons, screen reader reads "button unavailable, to activate press spacebar"
3.3.2 Labels or Instructions (Level A)Partially Supports

The product was tested for:

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

Exceptions

  • 28710035: Screen reader does not instruct user how to select/unselect all in a menu 
  • 31426835: When Publish On dialog pops up, screen reader does not read it 
3.3.3 Error Suggestion (Level AA)Partially Supports

The product was tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user

Exceptions

  • 29538710: Engagement Cloud Chat: Unable to toggle transfer queue UI off
  • 26917157: Currency fields should not use a disabled button for displaying the selected currency
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

The product was tested for:

  • Submissions are reversible.
  • Data entered by the user is checked for input errors with and the user is provided an opportunity for the user to correct them
  • Data can be reviewed, corrected, and confirmed by the user before they are finalized
  • A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
4.1.1 Parsing(Level A)Supports

The product was 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
4.1.2 Name, Role, Value (Level A)Partially Supports

The product has been 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'.
  • FRAMES and iFRAMES are titled with meaningful text.

Exceptions:

  • 27520132: Calendar control does not read selectable dates as 'selectable'
  • 31226850: Emoji dialog is difficult to use with screen reader
  • 26166806: Hierarchical menu items not being read by screen reader
  • 26276443: Hierarchical Multi-select component is not being read by screen reader
  • 25189611: Add to message button is not being read by screen reader when the button is disabled
  • 26382809: Images read as clickable, when image is not a link
  • 27522707: Multi-select menu filters in reports are not accessible
  • 27329521: Single select hierarchial menu not recognized as a form field
  • 27070542:  Field labels are read as clickable
  • 27076904:  Combobox Load More should be read as a link
  • 27153797: Select a Guided requires space-bar to select value
  • 27154317: Once a Guided Assistant guide has been selected, there should be header at the top of the guide section
  • 26917156: Address field should not be read by screen reader as editable since a user can't type into it
  • 26917247: Screen reader does not read the current values in select-box-input fields
4.1.3 Status Messages (Level AA)Supports

The product was tested for:

  • Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

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 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot ApplicableThe product is designed to be isolated from the underlying platform.
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingSupports

The product was tested for:

  • The authoring tool provides a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for all supported features and, as applicable, to file formats supported by the authoring tool.
  • The authoring tool permits authors the option of overriding information required for accessibility
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot Applicable

The product does not contain functionality to convert from one format type to another.

504.2.2 PDF ExportNot Applicable

The product does not provide capabilities to export or save any content in pdf format.

504.3 PromptsNot Supported

The product editor allows for content authoring within the product, and Oracle does not yet support prompting of user with accessibility information.

504.4 TemplatesNot Applicable

The use of the product editor is for users to format content, and does not provide any capabilities for the user to select a template.

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

 The product documentation describes:

  • special keystrokes needed to operate control
  • workarounds

Accessibility-related documentation can be found at:

http://documentation.custhelp.com/euf/assets/devdocs/bui/topicrefs/c_bui_Using_keystrokes_to_navigate_the_Agent_Browser_UI_6de27275.html?hl=f8 

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Product documentation is in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupports

Oracle Service Cloud Support can provide information about accessibility features of the product.

603.3 Accommodation of Communication NeedsSupports

Oracle customers have access to electronic support through http://cx.rightnow.com or by calling Oracle Service Cloud Technical Support at 1.800.806.6592.  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.

back to top

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.