Oracle Accessibility Conformance Report

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.
• Non-text characters are not used or have meaningful alternative text.
• CAPTCHAs are not used.

The product was tested for:

• User interface component labels are associated with the fields they are labeling.
• Relationships between data are identifiable by assistive technology, or a description of the information and the relationship is provided.
• 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.

The product was tested for:

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

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.

The product was tested for:

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

Exceptions:

• 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 was tested for:

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

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.

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.

The product was tested for:

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

The product was tested for:

• Images of text are not used.

The product was 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:

• In the Marketing area, elements in Audience listing are not accessible at 400% zoom. (31622308)
• In the Settings area, elements in modals are not accessible at 400% zoom. (31658570)
• In the Media area, elements in modals are not accessible at 400% zoom. (31658569)
• In the Publishing area, the publish button is not accessible at 400% zoom. (31639554)
• In the Catalogs area, elements in the import/export modal are not accessible at 400% zoom. (31639545)
• In the Catalogs area, elements in the Product Types modal are not accessible at 400% zoom. (31639546)
• In the Catalogs area, elements in the Product Types modal are not accessible at 400% zoom. (31608849)
• In the Catalogs area, elements in the Link Existing Collection modal are not accessible at 400% zoom. (31608849)
• In the Catalogs area, elements in the Collection context menu are not accessible at 400% zoom. (31608852)
• In the Catalogs area, elements in the New product modal are not accessible at 400% zoom. (31608850)
• In the Catalogs area, elements in the New collection modal are not accessible at 400% zoom. (31608851)
• In the Catalogs area, elements in the Link Existing Product modal are not accessible at 400% zoom. (31555972)
• In the Catalogs area, elements in the Link Existing Product modal are not accessible at 400% zoom. (31555972)
• 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)

The product was tested for:

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

Exceptions:

• 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 was 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 was tested for:

• Dismissable -The content 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 - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
• Information appears on hover or focus using default browser behavior, such as the title attribute of components.

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

Exceptions:

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

The product was tested for:

• Single character keyboard shortcuts can be turned off.
• Single character keyboard shortcuts can be remapped.
• Single character keyboard shortcuts are only active when that component has focus.

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:

• There is no moving, blinking, scrolling or auto-updating content.

The product was tested for:

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

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 links.

The product was tested for:

• Pages have a meaningful title specified in the TITLE element.

Exceptions:

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

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 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)
• In the Promotions area, as the user scrolls and new promotions are loaded dynamically, the keyboard focus should be consistently managed and shifted to the next visible, active element. (37089021)
• In the Catalog area, in the product list view, when the user opens the Edit dialog, the initial focus is not on the dialog, instead on the controls behind the dialog. (34217895)

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.

The product was tested for:

• Pages are fully inter-linked to each other.
• Page contains controls that enable reaching all pages.

The product was tested for:

• Headers describe the topic or purpose of the content below them.
• Labels describe the purpose of the associated field.

Exceptions:

• In the User Management area, in the Roles and Advanced Roles section within the user editor, the accessible name of the "Edit List" button should include the fact that this is to update the list of roles. (34217835)

The product was tested for:

• Visual indication of the location of the focus.

Exceptions:

• In the Catalog area, focus is not visible when user tabs to left side navigation panel elements on the Catalog details page. (37096372)

The product was tested for:

• The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

The product was tested for:

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

The product was tested for:

• When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function.
• When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion.
• When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event.

The product was 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 was tested for:

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

The product was tested for:

• All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.

The product was tested for:

• Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.

The product was tested for:

• Properly set lang attribute for each page.

The product was tested for:

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

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.

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.

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 unexpectedly closes. (34217859)

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.

The product was tested for:

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

The product was tested for:

• Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.

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 needs to be true consistently. (22632893)

The product was tested for:

• Labels or instructions are provided when the product requires user input.

The product was tested for:

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

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.

The product was tested for:

• Information previously entered by or provided to the user that is required to be entered again in the same process is auto-populated by the application.
• Information previously entered by or provided to the user that is required to be entered again in the same process is available for the user to select.

The product was tested for:

• The product supports password entry by password managers.
• The product supports copy and paste while authenticating.

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.

Exceptions:

• 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 Theme Code area, three labels are missing: Style Sheet, Style Variables, and Additional CSS. (31075382)
• In the User Management area, in the Roles and Advanced Roles dialogs within the editor for a new user, the roles returned in search results do not have accessible names. (34217866)
• In Maintenance area, Enable maintenance page checkbox does not have an accessible name. (36906316)
• In the Design area, the code view textboxes are missing labels. (31741923)
• In Design Studio, the popup stack tabs/steps on a Layout Grid View have children that take focus. (26714629)

The product was tested for:

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

Exceptions:

• 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)
• In the Settings -> Maintenance area, when maintenance page is activated, the message "Enable maintenance page request on ootb is in-progress" is not announced by screen reader. (36911118)
• In the Catalog area, in the Price Groups tab of the New Product dialog, when the user adds a new row to the Range table for Volume prices, the screen reader does not announce that a range has been added. (34217896)
• 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 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)
• 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)

See WCAG 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.