Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Commerce Cloud Service - Business User Tools 17.6

Product Description:

Merchants use the Oracle Commerce Cloud business user tools to set up an online commerce storefront. Using this product, merchants are able to:
  • Manage catalog data, including products, collections, media, inventory, and pricing
  • Create promotions and coupons that apply during customer checkout
  • Manage aspects of the storefront experience such as shipping methods, language, and connections to payment gateways
  • Manage aspects of the shopper's search and navigation experience
  • Assemble and style the storefront's web pages from a library of customizable ‘widgets’ and layouts
  • View reports on sales and site traffic
  • Support multiple languages 
  • Configure and send transactional emails
  • Manage media assets
  • Upload and manage extensions with additional functionality
  • Use Commerce Experiments, a webpage A/B testing tool, to configure and conduct experiments to obtain information that they can use to optimize their website

Date:

28-Nov-2017

Contact Information:

accessible_ww@oracle.com

Notes:

The documentation is provided in both HTML and pdf formats. The pdf version of the documentation is excluded from this VPAT.

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/us/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 with Exceptions The product was tested for:
  • Images that convey information have meaningful alternative text on the ALT attribute
  • Images that are decorative have an empty ALT attribute
  • Non-text characters are not used or have meaningful alternative text
  • Row and column headers for data tables are identified and their meaning is clear
  • Data tables have a meaningful summary attribute or caption element
  • Pages, pop ups, modals, and applets have meaningful and unique titles
  • Form elements have a meaningful labels
  • Information shown in complex images such as charts is also available in an alternative textual form
  • CAPTCHAS are not used
  • The product does not contain time-based media

Exceptions:

  • REST API document is missing alt text for expand arrows. (26410144)
  • In the product documentation, the row headers on tables should be more meaningful. (26934986)
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not Applicable

The product does not present audio or video.

1.2.2 Captions (Prerecorded) (Level A)Not Applicable

The product does not present audio or video.

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

The product does not present audio or video.

1.2.4 Captions (Live) (Level AA)Not Applicable

The product does not present audio or video.

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

The product does not present audio or video.

1.3.1 Info and Relationships (Level A)Supports with Exceptions The product was tested for:  
  • Form elements have a meaningful labels 
  • Data tables have a meaningful summary attribute or caption element 
  • Sections of content have meaningful headers (text only no links) and their structure and hierarchy is meaningful and groups of components are marked up with their description 
  • Style sheets are used only to change the layout and presentation on the screen 

Exceptions

  • The Assisted Selling Application Settings page has some missing and empty labels. (21840167) 
  • The Date and Time fields on the Schedule Publish page are missing table markup elements. (21056009)
  • The REST API documentation is missing HTML table summaries. (26908940) 
  • The REST API documentation has a structure violation. (26446205)
1.3.2 Meaningful Sequence(Level A)Supports with Exceptions The product was tested for:
  • The sequence of elements in the DOM matches a logical reading sequence

Exceptions:

  • In the Site Settings area, the header "Site Settings" should be read prior to the titles of the General, Location, and Price Groups tabs; these items are not read in logical sequence. (22346091) 
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 include 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 i.e. no information is conveyed by color alone
  • Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)Not Applicable

The product does not present audio or video.

1.4.3 Contrast (Minimum) (Level AA)Supports with Exceptions The product was tested for:
  • Text and images of text have a contrast ratio of at least 4.5:1
  • Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 

Exceptions:

  • The tabs in the Accounts area includes elements that do not conform to contrast ratio requirements. (25243685, 26896256)
  • In Design Studio, in the Collection Layout Grid View, when the Quick View Popup Stack is selected, the Quick View Popup Stack Name and the unselected Stack Step (either Main or Popup) do not conform to color contrast requirements. (26754859)
  • In the REST API documentation, the left-panel TOC/navigation fails color contrast. (26418525)
  • In the REST API documentation, there are color contrast problems for arrows, TOC, and link text. (26410156)
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)Not Applicable

Images of text are not used

2.1.1 Keyboard(Level A)Supports with Exceptions The product was tested for:
  • Fields and controls are accessible via the keyboard (by tabbing, enter, arrows or by documented shortcuts/access keys) 
  • Mouse-overs are not used unless they don't provide information essential for usage and comprehension of the application (image zoom hover over would be ok for example) or the information is provided some other way for assistive technologies to access. 
  • 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: FilterKeys (feature names may be different on different platforms) 

Exceptions:

  • In the Collections section of the Catalog, there is no keyboard alternative to the drag and drop approach for the re-sequencing of sibling collections or the reassignment of the a collection to another parent. (21217910)
  • In the Catalog, on the Media Tab within a Product, pressing the ESC key to close the 'Add Images' drop down list instead closes the product modal. (21056082)
  • In the Catalog, in the Collections tab, after selecting "Edit," the keyboard-only user has no way to remove a collection. (24535295)
  • In the Catalog, when the keyboard is used to copy products from one collection to another, the count increment is not shown on the target collection. (26277946)
  • In the Price Groups area of Catalogs, the keyboard user cannot get to the Search box within the "Filter by" dropdown. (26404570)
  • In Promotions, keyboard operation for scrolling through included products does not work correctly (24534966)
  • In Promotions, the "Unlimited" checkbox for Number of Items to be discounted becomes unchecked when a user tabs to it in Firefox. (25817119)
  • In Experiments, on the Variant Tab, the user cannot select all elements using keyboard only. (21765212)
  • In Experiments, the keyboard user cannot select a link or a collection dropdown element to select it as a variant change. (26528281)
  • The embedded assistance icon on the Stacking Rules has associated help text that can be accessed via mouse and that is read by a screen reader; however, a keyboard-only, non-screen reader user cannot access the text. (26594198)
  • In the Tax Processing area, the mouseover text associated with two icons is read by a screen reader, but a keyboard-only, non-screen reader user cannot access this text. (26762418)
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.2.1 Timing Adjustable(Level A)Supports with Exceptions

The product was tested for:

  • Time limits in the product can be extended with at least 20 seconds warning up to 10 times

Exceptions:

  • The business user tools UI includes growl messages that disappear after a short time, but does not provide a way to configure growl dismissal time as a user preference. (22353273)
2.2.2 Pause, Stop, Hide (Level A)Supports

The product was tested for:

  • The product does not contain moving or blinking information
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 with Exceptions 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 link

Exceptions:

  • Documentation needs "Skip to Main Content" link. (26934844)
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

  • In some situations, the focus order is incorrect - this was observed when modals are closed or the user tabs beyond the last element in a page (20396171, 20397740)
  • Focus is going out of 'Additional Store Languages' control after removing a language through keyboard (21162718)
  • In the Media library, when the user is tabbing through the list, focus goes back to top of list instead of continuing linearly. (21860982)
  • On the Media tab, when the user removes an image and then responds to the confirmation dialog, focus returns to the first image on the page instead of the next image. (21860990)
  • In the Locations tab of the Site Settings page, after the user selects a language, focus moves to start of the page instead of staying on the language selector. (21377693)
  • In some situations, focus is shifted behind a modal (21377694, 21860971)
  • Under some conditions, focus moves to the Dashboard page instead of staying in the Location tab of the Site Settings page. (21162718)
  • In the Catalog area, focus does not return to the "Manage Catalog" button after the Product Type modal closes. (20396238)
  • In Experiments several areas have loss of logical focus (21765209, 25725705, 25725927, 25725929)
2.4.4 Link Purpose (In Context)(Level A)Supports The product was tested for:
  • The purpose of a link can be determined by its text 
2.4.5 Multiple Ways(Level AA)Supports The product was tested for:
  • Pages are fully inter-linked to one another
  • Page contains controls that enable reaching other pages
2.4.6 Headings and Labels(Level AA)Supports with Exceptions The product was tested for:
  • Form elements have a meaningful label either as a displayed label or using title 
  • Row and column headers are identified for data tables and their meaning is clear 

Exceptions:

  • In the product documentation, the row headers on tables should be more meaningful. (26934986)
2.4.7 Focus Visible(Level AA)Supports with Exceptions The product was tested for:
  • Visual indication of the location of the focus 
Exceptions
  • In Gridview when focus is moved away from a selected widget, the state of that widget is not changed. (21056108)
  • In the 'Media' section, focus is not clearly visible on the Grid/ List view buttons and the Sort By dropdown. (21056108)
  • In Firefox, when arranging the products in a collection, there is no visual indication when focus in on an up-arrow. (21866631)
3.1.1 Language of Page(Level A)Supports The product was tested for:
  • Pages have properly set lang attributes
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, or 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 
  • In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components 
3.2.3 Consistent Navigation(Level AA)Supports The product was tested for:
  • Navigation mechanisms that are used in multiple pages are consistent
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 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: 
  • In the Payment Processing area of Settings, there is inconsistent error message behavior when required fields are skipped. In some cases, the system generates an error message with links to the fields with missing values; this should be true consistently. (22632893)
3.3.2 Labels or Instructions (Level A)Supports The product was tested for:
  • Form elements have a meaningful labels (input, select, textarea), either as a displayed label or using title 
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 can be reversed by the user
  • Data is checked for input errors with an opportunity for the user to correct them
  • Data can be reviewed, corrected, and confirmed by the user before they are finalized 
4.1.1 Parsing(Level A)Supports with Exceptions The product was tested for:
  • Pages validate to the HTML specification
Exceptions
  • Duplicate IDs are present in the following UI areas: Order Reporting, Catalog, Theme View, Product Type, Product, Payment Gateways, Promotions, Stacking Rules, Media Library, Assisted Selling Application Settings, Site Settings, Accounts, Publishing (21854170, 21866626, 21854437, 21840167, 22346104, 24611508, 25074148, 25817120, 26994085)
  • Empty labels are found in several UI areas, including the Settings for the Assisted Selling Application and the pages for creating new products and collections. (21916632)
  • Duplicate IDs are found on product documentation pages. (26324715)
4.1.2 Name, Role, Value (Level A)Supports with Exceptions 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 programatically exposed name
  • Frames have a meaningful title specified in the title attribute

Exceptions:

  • In the Web APIs area of Settings, when the user edits an existing application and tabs to the Application Key field, the screen reader does not read the field. (21377752)
  • In the Coupon creation area, some inline error messages are read of out context. (22346089)
  • In the Coupon and Promotion creation areas, some inline error messages are not read (22346094)
  • When the user skips a required field when creating a promotion, the error that appears visually is not read by the screen reader. (22346073)
  • In Experiments, on Experiments Dialog, the screen reader is not reading out validation errors (25725940)
  • In Experiments, on Experiments Dialog, the screen reader is not reading out title attributes associated with buttons and links (25725935)
  • In the Audiences area, when the list of rules for an audience is empty, the screen reader does not read the default text. (25914043)
  • In the Audiences area, when a rule is invalid and an error message is displayed, the screen reader does not read the elements within the rules. (26484340)
  • In the Tax Processing area, a screen reader does not read success or error growl messages. (26762530)
  • In the Tax Processing area, a screen reader announces the header elements as "type and text" instead of reading the header text. (26762528)
  • In Design Studio, the Stack tabs/steps on a Layout Grid View have children that take focus - a structural problem for accessibility. (26714629)
  • In the REST API documentation, element with role Tab must not have children that take focus. (26410099)
  • REST API resource tabs are marked up as radio buttons in code. (26410127)
  • Expand and arrows in the REST API list of endpoints are marked as page tabs. (26410137)
  • In the REST API documentation, there are duplicate labels on page tab and pushbuttons. (26446187)

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

This product includes features that allow merchandisers to author text to be displayed on the Oracle Commerce Cloud Service Storefront and in the Oracle Commerce Agent Console. The product uses CKEditor to provide this functionality, and thus incorporates CKEditor's accessibility features for content authoring.

See WCAG 2.0 section.

504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot Applicable

The product does not convert file formats.

504.2.2 PDF ExportNot Applicable

The product does not generate PDF exports.

504.3 PromptsNot Supported

The product does not yet support this guideline.

504.4 TemplatesSupports

The product provides customizable "widgets" that display text, images, and forms on the Oracle Commerce Cloud Service Storefront. Customers can use the widgets to create content that conforms to WCAG 2.0 AA. 

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

"Using Oracle Commerce Cloud" contains a chapter, "Accessibility Tasks," explaining how to navigate the user interface using keyboard shortcuts. The product's compatibility with assistive technology is available out of the box, with no action needed on the user's part. 

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 available in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle 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.

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 http://www.oracle.com/us/corporate/accessibility/oracle-accessibility-program-173235.html) 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/us/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.