Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Service Cloud Agent Browser User Interface August 2017

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, and a browser control on the workspaces.  This release introduces slicing, rollups, calculations, auro-refresh for analytics, application integration for chat, and knowledge foundation authoring features.

Agent Desktop Features not Supported by Browser User Interface:

  • Management and Administrative User Interfaces
  • Agent Desktop Add-Ins
  • Propose Answer
  • Agent Guides
  • Agent Scripting
  • Assets
  • Opportunity Management
  • Outreach
  • Feedback
  • Field Service

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

Date:

16-Mar-2018

Archive Note:

This VPAT applies to only version August 2017. It does not apply to any versions of Oracle Service Cloud Agent Browser User Interface after this. This VPAT has been superseded by Oracle Service Cloud Agent Browser User Interface 20A.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

  • Co-Browse
  • Incident Collaboration
  • Chat

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.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.govYes

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 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 Applicable

No pre-recorded audio-only or video-only content is being used.

1.2.2 Captions (Prerecorded) (Level A)Not Applicable

No pre-recorded video content is being used.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not Applicable

No live audio content in video is being used.

1.2.4 Captions (Live) (Level AA)Not Applicable

No pre-recorded video is being used.

1.2.5 Audio Description (Prerecorded) (Level AA)Not Applicable

No pre-recorded video is being used.

1.3.1 Info and Relationships (Level A)Supports with Exceptions

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
  • 25882218: Answers : Product / Category labels are not read by screen reader
  • 25882213: Answer : Audit log table content is not read by screen reader
  • 26020358: Missing or Empty Label for multi-select component and for Select All check 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.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 Applicable

No automatically playing audio is used.

1.4.3 Contrast (Minimum) (Level AA)Supports with Exceptions

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
  • 25115052: Tab count in workspace tabs do not meet color contrast requirement
  • 25255986 Chat Browser User Interface (BUI) Accessibility - The icon for the Chats button is not visible in high contrast mode
  • 25353534 Browser User Interface (BUI): In high contrast (Black) mode: Focused elements in dropdown select boxes do not meet accessibility contrast guidelines
  • 25353536 Browser User Interface (BUI): In high contrast (Black) mode: Focused elements in hierarchical menu boxes do not meet accessibility contrast guidelines
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

Besides the decorative Oracle logo, images of text are not used.

2.1.1 Keyboard(Level A)Supports with Exceptions

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:

  • 23708510: User has to press Enter key twice to open a sub-tab in a workspace
  • 25034451: "Filter" pop-up not closing with esc key
2.1.2 No Keyboard Trap (Level A)Supports

The product was tested for:

  • Movement of focus through each control using only the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.

 

 

2.2.1 Timing Adjustable(Level A)Supports

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

We do not have any 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)Supports with Exceptions

The product was tested for:

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

Exceptions:

  • 25041424: Illogical Tabbing Order in "new" and "update" pages, occurs vertically and should be horizontally
  • 25042820: User must tab backwords to the "add" button after adding note
  • 25859644: Custom Objects:  Send Email icon not accessible using tabs
  • 25881350: Notes : Pressing tab doesn't go to Edit / Delete buttons
  • 26240426: Unable to access elements on filter area on a report using keyboard actions
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)Supports with Exceptions

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:

  • 25108679: Missing label and description issue with Requested Date field on Interaction Workspace
  • 23521614: Title Bar objects can appear as headers but are not marked up
  • 25108837: 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
  • 25130543: Add an HTML header above the Chat Details section of chat
  • 25115037: Message, Copy and Forward Dialog headers not marked up as HTML Headers
  • 26099461: Forward dialog can lose focus when navigating with keyboard
  • 26203577: Analytics Filter: Missing or Empty Label for Limit to text box
2.4.7 Focus Visible(Level AA)Supports with Exceptions

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 Menus
  • 25788713: Main page - the "Quick Search" icon disappears if the user tabs away from the Quick Search component
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)Not Applicable

All passage 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)Supports with Exceptions

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:

  • 25704529: Chat BUI Accessibility - Pressing enter on the unread messages control causes Firefox file menu to open
3.2.2 On Input(Level A)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.
3.2.3 Consistent Navigation(Level AA)Supports with Exceptions

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 each time

Exceptions:

  • 25881981: Answers : HTML, URL, File Attachments are read as radio buttons
  • 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)Supports with Exceptions

The product was tested for:

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

Exceptions:

  • 25882210: BUI : Accessibility : Answers : Richtext editor has unnecessary information read out
3.3.1 Error Identification(Level A)Supports with Exceptions

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: BUI Accessibility - Workspace validation errors should be written to the commonArialiveArea of the BUI so that they are read by the screen reader
  • 25780515: BUI Accessibility - Messages written to the commonArialiveArea should be removed after 30 seconds
3.3.2 Labels or Instructions (Level A)Supports

The product was tested for:

  • Labels and/or instructions are provided when the product requires user input.
3.3.3 Error Suggestion (Level AA)Supports

The product 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 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)Supports with Exceptions

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:

  • 24518560: Inconsistent Value for Foreign key Contact for screen readers
  • 24300501: Screen Readers do not inform users of empty "Recent Items" list
  • 25704525: Chat BUI - Screen reader does not read the expanded/collapsed state of chats in the chat panel
  • 25704540: Chat BUI - The chat duration timer should not be read as being clickable by screen readers
  • 25859841: Answers:  Screen reader reads Access level values twice
  • 25881188: BUI: Upload attachment required field should be enhanced
  • 26166806: Hierarchical menu items not being read by screen reader
  • 26276443: Hierarchical Multi-select component is not accessible

back to top

2017 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 FeaturesNot Supported

Product documentation is available in the form of online help, which presently contains defects making the product inaccessible to keyboard only users.  Product documentation does not presently contain a chapter specific to accessibility.

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.