Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Adapter for Salesforce Lightning 2018.1.0.0 (Updated)

Product Description:

The Oracle Adapter for Salesforce Lightning is a connector/adapter application that facilitates integration between Oracle CPQ Cloud and the Salesforce Lightning platform. This approach separates the UI from the CPQ application engine and database. The new UI is built using Salesforce Lightning technology including Lightning Components, Visualforce and Salesforce Lightning Design System (SLDS) and runs natively in SFDC as a managed package. The end result of Salesforce's rendering is an HTML, CSS and Javascript-based web application. When the UI is loaded, it integrates via REST API to retrieve CPQ Cloud data and layout/object metadata. The Lightning Adapter interprets this response and dynamically renders a Lightning UI seamlessly within SFDC.

This adapter is the combination of a User Interface (UI) framework to embed Oracle Configure, Price, Quote (CPQ) Cloud within Salesforce.com (SFDC) Lightning, and a baseline implementation of the CPQ Cloud Transaction UI. This configuration is customizable, allowing us to provide an accessible UI. It is the responsibility of the administrator to follow documented steps to maintain accessibility if modifications are made to the configuration.

Browsers supported by Salesforce Lightning with the exception of Microsoft Edge have full user interface support. Administrative considerations around accessibility are provided in the User Guide for the Oracle Adapter for Salesforce Lightning. The default system configuration, provided as base for implementations, is developed with full accessibility support in the end user interface. Modifications to this configuration should follow instructions in the User Guide to protect against accessibility issues. This product has a single Web UI comprised of multiple pages that are rendered by Salesforce's Lightning Components Framework.

Date:

27-Mar-2018

Archive Note:

This VPAT applies to only version 2018.1.0.0. It does not apply to any versions of Oracle Adapter for Salesforce Lightning after this.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:Admin Pages that use declarative Salesforce layout technology:

Callout URLs - Specify the URL/prefix for a REST API
Endpoints - Specify the endpoint pattern/suffix for a REST API
Transforms - Specify the transform script to accompany an Action Step which converts data from one format into another
Key Chains - Configure keys to facilitate integration

Admin Pages that use Visualforce layout technology:

Routes - Specify Adapter Actions to invoke on page entry/action
Actions - Specify a set of steps including API callout, local load, local save and transform to accompany a particular page entry route or user activity (ex. button click)
CPQ Site Settings - Specify the default configuration data including field mapping and blacklists.

Salesforce has provided a set of VPATs here: https://www.salesforce.com/company/legal/508_accessibility.jsp.

When navigating from Salesforce to Oracle CPQ using the Oracle Adapter for Salesforce Lightning, accessibility is enabled out of the box with the base implementation.

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.1	Level A - Yes Level AA - Yes Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018	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.
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 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) No CAPTCHA used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Supports	No Pre-recorded audio-only or video-only content is being used.
1.2.2 Captions (Prerecorded) (Level A)	Supports	No Pre-recorded video content is being used
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Supports	No pre-recorded video is being used
1.2.4 Captions (Live) (Level AA)	Supports	No live audio content in video is being used
1.2.5 Audio Description (Prerecorded) (Level AA)	Supports	No pre-recorded video is being used
1.3.1 Info and Relationships (Level A)	Supports	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
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 Instructions provided which refer to graphics included a reference to the text alternative of the graphic
1.3.4 Orientation (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.3.5 Identify Input Purpose (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
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	No automatically playing audio is used
1.4.3 Contrast (Minimum) (Level AA)	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
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	Images of text are not used
1.4.10 Reflow (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.11 Non-text Contrast (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.12 Text Spacing (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.13 Content on Hover or Focus (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
2.1.1 Keyboard(Level A)	Supports	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 The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)
2.1.2 No Keyboard Trap (Level A)	Supports	The product was tested for: Movement of focus through controls only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control
2.1.4 Character Key Shortcuts (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.2.1 Timing Adjustable(Level A)	Supports	The product was tested for: Time limits in the product can be turned off before they are encountered - to the greatest extent possible without a negative effect on security. Sessions in CPQ and Salesforce will terminate after a configurable period of time measured in hours. Time limits in the product can be adjusted to at least 10 times longer before encountered Time limits in the product can be extended with at least 20 seconds warning up to 10 times Time limits used are part of a real-time event, or an essential activity - time limit is related to session security and expiration of tokens
2.2.2 Pause, Stop, Hide (Level A)	Supports	There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	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. - skip section links are provided Structure and hierarchy is marked up with Header elements outside of repetitive navigation links WAI-ARIA Landmark elements are used 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, 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 can be found using the provided "search" function Pages are in a site table of contents (Salesforce tab navigation) Page contains controls that enable reaching pages
2.4.6 Headings and Labels(Level AA)	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
2.4.7 Focus Visible(Level AA)	Supports	The product was tested for: Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.5.2 Pointer Cancellation (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.5.3 Label in Name (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.5.4 Motion Actuation (Level A)	Not Supported	This product has not yet been evaluated for this criteria
3.1.1 Language of Page(Level A)	Supports	The product was tested for: Properly set lang attribute for pages
3.1.2 Language of Parts(Level AA)	Not Applicable	While the page has a lang attribute, this release does not support multi-language.
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)	Not Applicable	This product has no navigational mechanisms that are repeated.
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: 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)	Partially 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 The following failed testing Pages validate to the HTML specification Salesforce's Lightning Component framework and SLDS both result in invalid markup per https://validator.w3.org/. We have an issue open with Salesforce to report this bug: https://partners.salesforce.com/partnerCaseDetails?id=5000M00000euxN2QAI
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 iFrames have a meaningful title taken from the embedded page which is configurable
4.1.3 Status Messages (Level AA)	Not Supported	This product has not yet been evaluated for this criteria

2018 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	Not Applicable	The product has no multimedia.
503.4.2 Audio Description Controls	Not Applicable	The product has no multimedia.
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	Not Applicable	The product uses standard operating system keystrokes to operate controls and does not have any special accessibility and compatibility features. As such there is no accessibility related documentation.
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	Support documentation is provided in electronic formats.
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.