Oracle Accessibility Conformance Report

The product and documentation were tested for:

• Images that convey information have meaningful alternative text using the ALT attribute
• 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)
• Pages, pop ups, modals, and applets have meaningful and unique titles
• Controls have an associated name
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used
• The video player in the product's media editor supports the use of caption files

There is no pre-recorded audio-only or video-only content.

The product and documentation were tested for:

• A business user who uploads a video intended for display on a website can also upload a caption file and associate it with the video. When the business user previews the video in the product's media editor and turns on captioning, the caption file supplies the captions.

The product and documentation were tested for:

• The product documentation advises customers to ensure that the soundtrack of any uploaded video is sufficiently descriptive of the visible content to communicate its meaning fully to a user who is visually impaired.
• The product documentation advises customers to supply a text file containing an alternate description of any uploaded video.

Exceptions:

• The video player provided in the media editor needs to support the use of an audio description as well as controls that allow the user to select an audio description. (30148086)

The product and documentation do not provide or support live media.

The product and documentation were tested for:

• The product documentation advises customers to ensure that the soundtrack of any uploaded video is sufficiently descriptive of the visible content to communicate its meaning fully to an end user who is visually impaired.

Exceptions:

• The video player provided in the media editor needs to support the use of an audio description as well as controls that allow the user to select an audio description. (30148086)

The product and documentation were 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
• Sections of content have meaningful headers, and their structure and hierarchy are meaningful
• Groups of components are marked up with their description
• Style sheets are used only to change the layout and presentation on the screen

Exceptions:

• In Experience Manager Rule List views, a screen reader does not read the column names, nor indicate that the columns are sortable. (25338972)
• In the product documentation, the row headers on tables need to be more meaningful. (26934986)
• In the List views of Experience Manager, the "Include Locations" checkbox in the header is missing a label. (33158105)

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:

• When the documentation pages are displayed using simulated devices, the scrollbar in the left-hand navigation pane does not work. (33340001)

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 weres 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 do not include automatically playing audio.

The product and documentation were 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 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 only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential

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:

• On Experience Manager pages, at 400% zoom, some action options at the top right of the screen are missing. (33086425)
• On the pages of all Workbench applications (including Experience Manager), both horizontal and vertical scrollbars appear at 400% zoom. (33319459)
• On the documentation pages, both horizontal and vertical scrollbars appear at 400% zoom. (33340165)

The product and documentation were tested for:

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

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

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

The product and documentation were 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 Experience Manager, to close the Project popover using the Esc key, the user must first use Tab or Shift-Tab to move focus to one of the fields at the top of the popover. (30048931)
• When focus is on a menu option reached from the Workbench toolbar, the Esc key does not close the menu; the keyboard user must tab through the options to exit the menu. (29445718)
• In Experience Manager, in the Project popover, a Chrome user who uses the keyboard to move focus to a project must sometimes press Enter twice to enter the project. (29290272)
• In Experience Manager, in the List views, a keyboard user does not have a convenient way to move from the table headers to the table contents, or to move quickly between rows, without traversing the headers and cells. (30210426)
• In Experience Manager, there is no keyboard alternative for drag and drop in the "mini-tree" of sections and cartridges within a rule or page. The workaround is to delete and re-add a cartridge. (24611047)

The product and documentation were tested for:

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

The product and documentation were tested for:

• There are no single character keyboard shortcuts

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

The product and documentation were tested for: 

• The product does not present moving, blinking, or scrolling content
• For any auto-updating that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause and stop the auto-updates.

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:

• The keyboard user can skip the navigation tree in the left-hand pane and go right to the editor in the right-hand pane
• The only other content that is repeated is the header bar, which contains only three options to be traversed

Exceptions:

• The product documentation needs a "Skip to Main Content" link. (26934844)

The product and documentation were tested for:

• Pages have a meaningful title specified in the TITLE element

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 the CAS Console and Keyword Redirects UIs, focus does not behave correctly in tables that occur within modals. (29132411, 29191539)
• In the CAS Console, focus order is not consistent when tabbing backward vs. forward through the List view. (29160182, 29126354)
• In Experience Manager, there are cases where focus remains on an overlay that lies behind the one that is currently active. (26634456)

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

• Pages are fully inter-linked to one another via a top-level menu that is always present
• Pages contain controls that enable reaching other pages

The product and documentation were tested for:

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

The product and documentation were tested for:

• Visual indication of the location of the focus

Exceptions:

• Focus is not visible on Workbench toolbar elements and megamenu options on home page. (29290243)
• In Experience Manager, focus is not visible on some elements of the Schedule modal within the editor of a page or rule. (28499732)

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, and a mechanism is available to abort the function before completion or undo the 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, 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

The product and documentation were tested for: 

• Navigation mechanisms that are used in a group of pages are used consistently, with navigation elements appearing in the same relative order on the various pages.

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

The product and documentation were tested for:

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

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:

• Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
• Pages validate to the HTML specification

Exceptions:

• Duplicate IDs are found on product documentation pages. (26324715)

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 programmatically exposed name
• Frames have a meaningful title specified in the title attribute

Exceptions:

• When a user tries to log into Workbench using the Chrome browser, but provides invalid input, a screen reader does not read the resulting error correctly. A workaround is to use Firefox. (29420569)
• In the User Management UI, a screen reader does not read the value selected from the "Permission from Groups" dropdown in the editor's General tab. (27106342)
• In the Experience Manager Manifest panel that is displayed with Preview, when a user segment or a device is selected, a screen reader does not read the selected value. (21414593)
• In Experience Manager, in a rule that includes the Rich Text Editor, a screen reader reads "Rich Text Editor" twice. (24903474)
• In Experience Manager, when the Project Contents list opens, a screen reader reads extraneous information. (21437353)

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:

• The status messages displayed in Experience Manager when the user saves changes are not read by a screen reader. (33179280)

The product and documentation were tested for:

• A business user who uploads a video intended for display on a website can also upload a caption file and associate it with the video. When the business user previews the video in the product's media editor and turns on captioning, the caption file supplies the captions. The controls for turning captions on and off are provided at the same user interface level as the volume controls. 

The product and documentation were tested for:

• User controls for the selection of audio description are provided at the same menu level as the user controls for volume or program selection

Exceptions:

• The video player provided in the media editor needs to support the use of an audio description as well as controls that allow the user to select an audio description. (30148086)

See the WCAG Section.

The product does not convert file formats.

The product does not generate PDF exports.

The product encourages customers to create accessible content as follows:

• The documentation states that the Rich Text Editor allows creation of accessible content.
• The documentation encourages customers who specify a video file for display on their website to do the following:
  • Provide a soundtrack that is sufficiently descriptive of the visible content to communicate its meaning fully to an end user who is visually impaired.
  • Upload a caption file for the video and associate it with the video, so that captioning functions in the editor's video player.
  • Customize the Media editor to include 1) a field for identifying an associated caption file, 2) a field for identifying an associated text file containing an alternative description of the video, and 3) a field for identifying an associated audio file that describes the video; and supply these associated files along with any video to be displayed on the site.
• The documentation encourages customers who use the Media Editor to display an image on the website to provide text in the Alt Text field, so that Assistive Technology can read the alt text to the user.
• The documentation encourages customers to test their website content for accessibility.

Exceptions:

• The out-of-the-box Media Editor needs to provide fields for a text alternative, an audio alternative, and a caption file, to encourage the business user to supply these files when specifying a video to be displayed on their website. (30147134)

The product was tested for:

• The product provides customizable "cartridges" that generate JSON or XML that can be used to display text, images, and videos on a website based on rules. A business user can use these cartridges to create content that conforms to the WCAG 2.0 AA standards. The rendering technology is independent of the cartridges.

The product and documentation were tested for:

• The Workbench User's Guide contains a chapter explaining how to navigate the user interface using the keyboard, as well as how to take advantage of other accessibility features (for example, pausing and stopping the auto-updating of information, and uploading a caption file for a video). The chapter mentions that our rich text editor allows creation of accessible content. It encourages business users to create accessible content and to test their websites for accessibility. The product's compatibility with assistive technology is available out of the box, with no action needed on the user's part. 

Product documentation is available in electronic format.