Oracle Accessibility Conformance Report

• 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
• Pages, pop ups, modals, and applets have meaningful and unique titles
• 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

The product does not present audio or video.

The product does not present audio or video.

The product does not present audio or video.

The product does not present audio or video.

The product does not present audio or video.

• 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)
• In the Reports area, the Customer Service report includes a layout table that could be confused for a data table. (28122498)

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

• 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

• 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

The product does not present audio or video.

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

• Text can be resized up to 200% without loss of content or functionality

The product was tested for:

• Images of text are not used

• 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 Price Groups area of Catalogs, the keyboard user cannot get to the Search box within the "Filter by" dropdown. (26404570)
• 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)
• 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)

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

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)

The product was tested for:

• The product does not contain moving or blinking information

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz 

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

• Pages have a meaningful title specified in the TITLE element

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

• The purpose of a link can be determined by its text 

• Pages are fully inter-linked to one another
• Page contains controls that enable reaching other pages

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

• Visual indication of the location of the focus 

• In Firefox, when arranging the products in a collection, there is no visual indication when focus in on an up-arrow. (21866631)

• Pages have properly set lang attributes

• Proper use of lang attribute for text passages that are in a different language than that of the page

• 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

• 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 

• Navigation mechanisms that are used in multiple pages are consistent

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

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

• 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)
• In the Publishing area, when the Schedule Publish page is blank and the user tries to schedule the publish, the screen reader does not read the error message, nor indicate which fields are required. (21377700)

• Form elements have a meaningful labels (input, select, textarea), either as a displayed label or using title 

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

• 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 

• Pages validate to the HTML specification

• Duplicate IDs are present in the following UI areas: 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, 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)

• 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 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, there are duplicate labels on page tab and pushbuttons. (26446187)
• In the Reports area, dropdown fields do not have accessible names, and some submenu items are not read by a screen reader. (27456307)

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.

The product does not convert file formats.

The product does not generate PDF exports.

The product does not yet support this guideline.

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. 

"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, except in the Reports area. The Reports area of the product uses Oracle Business Intelligence Enterprise Edition (OBIEE), which has an accessibility mode. The document "Using Oracle Commerce Cloud Reports" explains how to turn on OBIEE's accessibility mode, and includes a link to OBIEE documentation that describes OBIEE's accessibility features.

Product documentation is available in electronic format.