Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Fusion Service Request Management Cloud Service (Updated) 11.13.18.02.0

Product Description:

This VPAT covers the service request management functionality available in Oracle Engagement Cloud. The product supports the ability to create, edit, assign, respond to and resolve service requests. Service Requests can be associated to accounts, contacts, partner accounts, activities, and assets that are shared between the sales and service applications. The user interface for the product is based on the Fusion Simplified User Experience. Service Requests can also be created and updated through REST APIs and file-based import.

Date:

13-Dec-2018

Archive Note:

This VPAT applies to only versions 11.13.18.02.0 through 11.13.18.08. It does not apply to any versions of Oracle Fusion Service Request Management Cloud Service after this. This VPAT has been superseded by Oracle Fusion Service Request Management Cloud Service 11.13.18.10.0.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:
Access to the data through REST or SOAP web services
PDF and ePub files

Accessibility mode can be activated by the user using the Accessibility preferences page available from the global UI header across the top of every page. The user can access this page through one of two paths - either by selecting the accessibility mode icon in the global UI header or by selecting the user menu in the top right corner of the global UI header and then choosing Personalization > Set Preferences > Accessibility.

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/Guideline	Included In Report
Web Content Accessibility Guidelines 2.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/	Level A - Yes Level AA - Yes Level AAA - No
Section 508 as published in 2017, at https://www.Section508.gov	Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports: The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Supports with Exceptions: Some functionality of the product does not meet the criteria.
Does Not Support: Majority of functionality of the product does not meet the criteria.
Not Applicable: The criteria are not relevant to the product.

WCAG 2.0 Report

Table 1 also documents conformance with:

Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports	The product was tested for: Images that convey information have meaningful alternative text using ALT Images that are decorative are marked up using ALT=”” or CSS background images Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table) Titles for Objects and Applets are provided Controls have an associated name Text summary or alternative is provided for time-based media Client-side image maps specify the ALT attribute on each AREA element. CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product was tested for No Pre-recorded audio-only or video-only content is being used
1.2.2 Captions (Prerecorded) (Level A)	Supports	The product was tested for Pre-recorded video includes captions embedded in the media (potentially as a second version of the media)
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Supports	The product was tested for: Pre-recorded video includes an alternative to the video
1.2.4 Captions (Live) (Level AA)	Not Applicable	No live audio content in video is being used.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Supported	Bug 26554336 - Prerecorded videos do not include audio description
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 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 Known accessibility defects include: (Bug #26185241) When a user is composing a Service Request message, the screen displays two Cancel buttons (a button for the parent service request record and a button for the message) but the alternate text labels are the same for both buttons. (Bug #25879589) When a user creates a Service Request using the Save and Close action, a confirmation message is displayed and the user must close the message. However, a screen reader will incorrectly focus on the Close link rather than the text of the confirmation message. (Bug #23272062) In the Edit Service Request page, users may have difficultly determining how to access knowledge because the text label to expand the right hand panel is named ambiguously ("Restore Pane"). (Bug #26598140) When using a screen reader, if a user opens the right hand panel on the Service Request detail page and uses the Manage SmartText icon to view a SmartText, the contents of the SmartText are read twice. (Bug #26483034) When using a screen reader, if an administrative user accesses the Functional Setup task 'Manage Business Unit' to create a new business unit, the page includes extra elements which can take the focus of the cursor.
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 which refer to graphics included a reference to the text alternative of the graphic
1.4.1 Use of Color(Level A)	Supports	The product was tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)	Supports	The product was tested for: 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 All other text and images of text have a contrast ratio of at least 4.5:1 Known accessibility defects include: (Bug 27641034) The splitter to display the right hand panel on the Service Request detail page is not visible in High Contrast mode.
1.4.4 Resize text(Level AA)	Supports	The product was tested for: Text can be resized up to 200% without loss of content or functionality
1.4.5 Images of Text(Level AA)	Supports	The product was tested for: 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, and without requiring specific timings for individual keystrokes Proper operation of unique keystrokes and access keys, including those listed in the product documentation Known accessibility defects include: (Bug #25668485) When a user tries to edit the category field and product field on a Service Request, the user must use the Alt+down keystroke to expand the field and the Shift+Tab keystroke to search the rows in the hierarchy. However, the user is not able to use the keyboard to select one of the items in the hierarchy. As a workaround, the user must tab into the search box and search on the text of the desired item specifically. (Bug #23032577) In the Queues list page, the sort controls in the column headers cannot be selected using a keyboard in order to choose ascending or descending order. (Bug #26595324) When composing a Service Request message, after a value is selected in the From field, the cursor can lose focus intermittently if the JAWS Command+E is used to navigate to the message content area. As a workaround, the user can instead use the Tab key to navigate to the message content area. (Bug #26595266) When composing a Service Request message, the Insert Knowledge button does not perform any action when invoked using a screen reader tool. (Bug #26537763) When using a screen reader, if an administrative user is attempting to associate a Business Unit to a Communication Channel, the reset action does not clear the existing search value and the Search and OK actions do not work. (Bug #26482845) When using a screen reader, if an administrative user is attempting to create a Business Unit, the user unable to select a value for the Default Set field, which is a mandatory field, thus the user is unable to create a Business Unit.
2.1.2 No Keyboard Trap (Level A)	Supports	The product was tested for: Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control
2.2.1 Timing Adjustable(Level A)	Supports	The product was tested for: When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
2.2.2 Pause, Stop, Hide (Level A)	Supports	There is no moving, blinking or scrolling content that starts automatically.
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: 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	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product was tested for: The text of links and their surrounding paragraph, list, 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 can be found using the provided "search" function Pages are in a site table of contents 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 Known accessibility defects include: (Bug #22365035) The attachment popup dialog for selecting attachments when creating or editing a Service Request does not provide text for the H2 header element. (Bug #27517760) When using a screen reader, the contacts subtab on a Service Request is only identified by Row number, which may not be sufficient for a user to identify the selected row. (Bug #27431050) When using a screen reader, the team subtab on a Service Request is only identified by Row number, which may not be sufficient for a user to identify the selected row. (Bug #27260098) When using a screen reader, if there is a service request message with a single recipient, only the recipient name is read and displayed but not the email address of the recipient.
2.4.7 Focus Visible(Level AA)	Supports	The product was tested for: Visual indication of the location of the focus
3.1.1 Language of Page(Level A)	Supports	The product was tested for: Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)	Supports	The product was tested for: Proper use of lang attribute for text passages that are in a different language than that of the page
3.2.1 On Focus(Level A)	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
3.2.2 On Input(Level A)	Supports	The product was tested for: Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
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 Known accessibility defects include: (Bug #26235418) When a user navigates into the embedded help from the Service Requests work area, if the user has navigated links into a second level help page, the Escape key will completely exit the help and return the user to the Service Requests work area, rather than navigating back one level within the help content.
3.2.4 Consistent Identification(Level AA)	Supports	The product was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	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
3.3.2 Labels or Instructions (Level A)	Supports	The product was tested for: Labels 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 is checked for input errors with an opportunity for the user to correct them Data can be reviewed, corrected, and confirmed by the user before they are finalized
4.1.1 Parsing(Level A)	Supports	The 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	The product was tested for: HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc. Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’. Custom controls have appropriate roles specified using the role attribute Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes Custom controls have a meaningful programmatically exposed name Frames have a meaningful title specified in the title attribute

2017 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of Color	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without Speech	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited Manipulation	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and Strength	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria	Conformance Level	Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive Technology	Heading cell - no response required	Heading cell - no response required
502.2.1 User Control of Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility Features	Not Applicable	The product is designed to be isolated from the underlying platform.
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and Headers	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.4 Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.6 Label Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.8 Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.10 List of Actions	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on Objects	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.14 Event Notification	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Not Applicable	The product is designed to be isolated from the underlying platform.
503.3 Alternative User Interfaces	Not Applicable	The product does not have assistive technology features.
503.4 User Controls for Captions and Audio Description	Heading cell - no response required	Heading cell - no response required
503.4.1 Caption Controls	Supports	The product was tested for: user controls for the selection of captions are provided at the same menu level as the user controls for volume or program selection.
503.4.2 Audio Description Controls	Supports	The product was tested for: user controls for the selection of audio description are provided at the same menu level as the user controls for volume or program selection.
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
602 Support Documentation	Heading cell - no response required	Heading cell - no response required
602.2 Accessibility and Compatibility Features	Supports	The product documentation describes: accessibility modes, either at installation or runtime special keystrokes needed to operate controls workarounds Accessibility-related documentation can be found at: Oracle Applications Cloud Using Common Features, Chapter 13 Accessibility
602.3 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support Documentation	Not Applicable	Product documentation is in electronic format.
603 Support Services	Heading cell - no response required	Heading cell - no response required
603.2 Information on Accessibility and Compatibility Features	Supports	Oracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication Needs	Supports	Oracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.