Oracle Accessibility Conformance Report

The product and documentation were 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
• 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 and documentation were 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 Publishing page contains a structure error related to a dl (description list) element containing improperly formatted dt (terms) and dd (descriptions) groups. (31639553)
• In the Experiments area, on the Experiments dialog Results tab, the Refresh and Export Buttons are missing labels. (31706456)
• In the Experiments area, on the Experiments dialog Target tab, the Traffic Allocation Control and Variant text boxes are missing labels. (31689453)
• In the Design area, the code view textboxes are missing labels. (31741923)
• In the Catalog area, in the product list view, when the user opens the Edit dialog, the screen reader does not acknowledge that focus has shifted to the dialog, instead mentioning the controls behind the dialog. (34217895)
• In the Design area, some layout names are read twice by a screen reader. (34233440)

The product and documentation were tested for:

• The sequence of elements in the DOM matches a logical reading sequence

The product and documentation were 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

The product and documentation were tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text

Exceptions:

• In the Server Side Experiment dialog accessed from a Design Studio Layout, and in the Experiments application, there is loss of content and functionality when the display is in Portrait mode. (31669114)
• In the Audiences area, the New Rule dialog does not display correctly in portrait mode. (31622305)
• In the Design area, in portrait mode, display elements overlap and/or overflow in lists of components, layouts, and themes, and in settings forms for layouts, themes, and widgets. (31741927)

The product and documentation were tested for:

• Text fields which collect information about the user contain the appropriate autocomplete content attribute

The product and documentation were 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

The product and documentation were 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)

The product and documentation were tested for:

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

The product and documentation were tested for:

• Images of text are not used

The product and documentation were tested for:   

• Text information reflows so that only one direction of scrolling is required while at 400% zoom 
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content

Exceptions:

• At 400% zoom, there is a loss of content or functionality, and/or the user must scroll both vertically and horizontally to view all content, in the following areas: Experiments, Audience list views and dialogs, Search list views and dialogs, Search rule editors, Searchable Field Ranking editor, Settings dialogs, Create Site dialog, Media Library dialog, Publishing, Import/Export dialog, Product Types, Collection pickers, Collection context menus, New Product dialog, New Collection dialog, Link to Collections dialog, Link Existing Product dialog, and the Design area (menu bars, settings, dialogs, and lists). (31669113, 31622308, 31658570, 31658568, 31658569, 31639554, 31639545, 31639546, 31608849, 31608852, 31608850, 31608851, 31555972, 31741930)
• In the Accounts list and the account editor, content is missing in several places when displayed with 400% zoom. (34217874)
• In the User Management area, in the Roles dialog within the editor for a new user, some content is missing at 400% zoom. (34217841)
• In the Design area, with a zoom of 400%, some content is lost on the main Design page. (34233440)

The product and documentation were tested for:

• Non-text items have a contrast ratio of at least 3:1

Exceptions:

• The Experiments area includes UI components that do not satisfy the contrast requirements. Examples include the contrast between the Delete button and the Notification Panel when deleting an experiment; the contrast between the Yes button and the Notification Panel when closing the panel without saving changes; and the contrast between the star icon (which flags a goal as primary) and its background. (31706448)
• The Design area includes UI components that do not satisfy the contrast requirements with respect to their backgrounds. Examples include the default flag, the layout icon, the layout gridview icon, the stack gridview icon, and the slot icon. (31741933)

The product and documentation were tested for:

When the following attributes and no others are modified, there is no loss in functionality or content:

• Line height (line spacing) to at least 1.5 times the font size
• Spacing following paragraphs to at least 2 times the font size
• Letter spacing (tracking) to at least 0.12 times the font size
• Word spacing to at least 0.16 times the font size

Exceptions:

• In the Design area, for some labels on the list of layouts, when text is spaced according to the guideline’s requirements, the tooltips that should display truncated text do not do so. (34233440)

The product and documentation were tested for:

• Dismissable - Content on hover or focus can be dismissed without moving the pointer or keyboard focus
• Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing
• Persistent - Content on hover remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid

Exceptions:

• In the Experiments area, there are several places where the pointer cannot be moved over additional content that was triggered by pointer hover, without the additional content disappearing. Examples include the Experiment Name on the Experiments home page, the Results charts in the Progress panel, and the Results charts on the Results tab in the Server Side Experiments dialog. (31706462)

The product and documentation were 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 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)
• The Promotions area includes dropdown controls where the user must press Tab an extra time to select an item. (28710999)
• In the Search area's lists of Thesaurus entries, Keyword Redirects, and rules, and in a rule's collection picker, when a row's contents are too long and are truncated with an ellipsis, a tooltip with the full text is displayed on hover and read by a screen reader on focus; but the tooltip is not displayed on focus, and thus is not available to a keyboard user who does not use a screen reader. (31652837)
• In the Catalog area, in the File Selector window of the Import dialog, pressing Esc not only closes the File Selector window, but also closes the Import Dialog without notice to the user. This is in contrast to what happens when the File Selector dialog is closed using a mouse: in that case, focus correctly returns back to the Import dialog. (34217862)
• In the Catalog area, the user cannot select an item from the Collections Menu using the Enter key (which is the standard expected by screen readers), but only by using the Space key. (34217871)
• In the Catalog area, in the product list view, there is no way to reorder the products using the keyboard. (34217895)
• In the Design area, the information in the tooltip for the Preview icon is not available for a keyboard-only user. (34306220)

The product and documentation were 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

The product and documentation were tested for:

• Single character keyboard shortcuts can be turned off or remapped, or are only active when the component has focus

The product and documentation were 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 and documentation were tested for:

• The product does not contain moving or blinking information

The product and documentation were tested for:

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

The product and documentation were 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

The product and documentation were tested for:

• Pages have a meaningful title specified in the TITLE element

Exceptions:

• The Commerce login page is missing a title. (34217828)

The product and documentation were tested for:

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

Exceptions

• In Experiments several areas have loss of logical focus (21765209, 25725705, 25725927)
• In the Catalog area, in the Price Groups tab of the New Product dialog, tabbing from the Price Groups table should go directly to the Cancel button. Instead, there is an unexpected tab stop on the pagination control, which is hidden. A screen reader also announces the pagination control. Tabbing again does take the user to the Cancel button. (34217899)
• When the user is on the URL bar for the Accounts list page, pressing Tab takes the user to the next focusable field – the left-hand navigation panel – and lands on the Accounts menu item. The product should have a consistent approach to initial focus when the user tabs into the page. (34217878)
• In the Accounts area, when the Accounts list opens, focus remains on the Accounts tab in the left-hand navigation; tabbing from there takes the user to the next focusable element, which is the Changes item in the left-hand navigation; the next tab goes to the page header. The product should have a consistent approach to focus order when a page opens. (34217869)
• On the home page of the Administrative console, the first navigable and focusable element should be “Skip to content,” instead of the first item in the left-hand navigation menu. (34217860)
• In the Design area, focus order within the headers of widgets is not as expected. Focus goes to the Settings and Close icons on the right before going to the widget name on the left. (34233440)

The product and documentation were tested for:

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

The product and documentation were tested for:

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

The product and documentation were 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 User Management area, in the Roles and Advanced Roles dialogs within the user editor, the accessible name of the "Edit List" button should include the fact that this is a list of roles. (34217835)

The product and documentation were tested for:

• Visual indication of the location of the focus

The product and documentation were tested for:

• Multipoint or path-based gesture actions can be completed using a different input modality

The product and documentation were tested for:

• The down-event of the pointer is not used to execute any part of a function
• Completion of a function is on the up-event
• A mechanism is available to abort a function before completion or undo a function after completion

The product and documentation were tested for:

• User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually

The product and documentation were tested for:

• There are no functions that require motion of the device.

The product and documentation were tested for:

• Pages have properly set lang attributes

The product and documentation were tested for:

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

The product and documentation were 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

The product and documentation were 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 

Exceptions:

• In the Catalog area, in the Custom Search dialog, when focus reaches the “Reset” button and the user presses Enter, the entire Custom Search dialog closes. This is unexpected behavior. The dialog should stay open (with the rules reset). (34217859)

The product and documentation were tested for:

• Navigation mechanisms that are used in multiple pages are consistent

The product and documentation were tested for:

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

The product and documentation were 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 needs to be true consistently. (22632893)

The product and documentation were tested for:

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

The product and documentation were tested for:

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

The product and documentation were 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 

The product and documentation were tested for:

• Pages validate to the HTML specification

Exceptions

• Duplicate IDs are present in the following UI areas: Catalog, Collection, Theme View, Product Type, Product, Payment Gateways, Promotions, Stacking Rules, Media Library, Assisted Selling Application Settings, Site Settings, Accounts, Publishing, Operations (21854170, 21866626, 21854437, 21840167, 26994085, 31748141)
• 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 the Accounts list and Contacts list pages. (34217872)

The product and documentation were 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:

• 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 Design Studio, the Stack tabs/steps on a Layout Grid View have children that take focus - a structural problem for accessibility. (26714629)
• In the Reports area, dropdown fields do not have accessible names, and some submenu items are not read by a screen reader. (27456307)
• In Design Studio, in the Components section, when the user navigates to component instances, the screen reader reads the contents of a screen that is no longer displayed, before reading the contents of the current screen. In addition, it reads the buttons of the previous screen as unlabeled. (31075317)
• In Design Studio, in the Layouts sections, when the user navigates to layout settings, the screen reader reads the contents of a screen that is no longer displayed, before reading the contents of the current screen. (31075371)
• In Design Studio, in a layout with a content variation slot, a screen reader does not read the default and control slot names. (31075375)
• In Design Studio, in the Theme Code area, three labels are missing: Style Sheet, Style Variables, and Additional CSS. (31075382, 30736058, 30755971)
• In the Accounts and Price Groups areas, when the user specifies that an account or price group should be a child, but fails to choose a parent, the validation error is not read by a screen reader. (31177447)
• On the Experiments Target Panel, the buttons to add and remove Included URLs do not have discernible text. (31689455)
• On the Experiments Target Panel, the Audience selector does not have a unique role or accessible name. (31689458)
• In the Experiments area, on the Click Goal Selection Navigation Panel, the Refresh Goal URL button does not have discernible text. (31689457)
• In the Catalog area, in the Price Groups tab of the New Product dialog, when a keyboard user is trying to enter a Volume price and reaches the Price field in Range table, the screen reader announces that the user must enter a value, but there is no way for the user to know that there is a range start value or what that value is. Also, when the user adds a new range row to the Range table, the screen reader does not announce that a range has been added, nor that the user should now enter a price. (34217896)
• In the Catalog area, in a custom search, when the user adds a new rule and then tabs to move focus to the rule, a screen reader does not mention which fields are present. (34217871)
• In the User Management area, in the Roles and Advanced Roles dialogs within the editor for a new user, some items are missing accessible names. (34217866)
• In the User management area, in the User editor, the "Externally Managed" field is not read by a screen reader. It should be made read-only instead of disabled so that it is included in the tab order. (34217834)
• In the User Management area, in the list of users, the screen reader does not inform the user how to use the Roles filter. (34217831)
• In the User Management area, in the pop-up that lists a role’s privileges, a screen reader should read the role name. (34217844)
• On the home page of the Administrative console, a screen reader does not inform the user that down/up arrow should be used to navigate down and up the left-hand navigation panel. (34217860)
• When the user is in the Settings or Marketing area and there are multiple authors to a workset, the screen reader does not read out the author list in the changes tracker widget. (34234651)
• In the navigation menus within the Search and Accounts areas, when an item has child items (that is, there is a menu hierarchy), the arrow that expands/collapses the child list does not have an accessible name. (34277163)

The product and documentation were tested for:

• Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus

Exceptions:

• In the Accounts area, when the user has navigated to the Accounts, Contacts, or Registration Requests menu item, a screen reader should announce that the Accounts list, Contacts list, or Registration Request list has opened. (34217870)
• In the User Management area, in the Roles selector, when the user searches for roles, the screen reader should inform the user how many roles are brought back. (34217839)
• In the User Management area, in the Roles and Advanced Roles dialogs within the user editor, if the user’s search text yields no matching roles, a screen reader should announce that no roles are found. (34217844)
• In the left-hand navigation pane, when the user navigates to the User Management menu item and presses Enter, a screen reader should announce that the list of users has opened. (34217829)

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.

Exceptions:

• The authoring aspects of the product should prompt users to create accessible content. (32982442)

The product provides customizable "widgets" that display text, images, and forms on the Oracle Commerce Cloud Service Storefront and the Oracle Commerce Agent Console Cloud Service. 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 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.