Oracle Accessibility Conformance Report

The product and documentation 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)
• Controls have an associated name
• CAPTCHAs are not used

The product and documentation was 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 summaries where appropriate
• Data tables specify SUMMARY
• 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 and documentation was tested for:

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

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

The product and documentation was tested for:

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

The Product  was tested for:

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

The Documentation was tested for:

• The documentation does not allow for input or changes to data.

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

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

Exception :

1. 33970709 - Tables on zoom to 200% are not structurally intact on UI

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

The product and documentation was tested for:

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

The product and documentation 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 1.5 times the font size
  • Spacing following paragraphs to 2 times the font size
  • Letter spacing (tracking) to at 0.12 times the font size
  • Word spacing to 0.16 times the font size

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

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

1. 35820670 - ACC- OCIUI:AJD: On the Pluggable Database (PDB) Detail Page, Info Icon Under "Database Connection"->"Connection Strings" Is Not Accessible Using Keyboard
2. 35820738 - ACC- OCIUI:AJD: Inaccessible Info Icons On the Pluggable Database (PDB) Detail Page
3. 35820415 - ACC- OCIUI:AJD: On Provisioning Page, Info Icon Under "Configure The Database"->"Hide Advanced Options" Is Not Accessible Using Keyboard

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

• Single character keyboard shortcuts are only active when that component has focus.

The product and documentation was tested for:

• Time limits are not used.

The product and documentation was tested for:

• There is no moving, blinking or scrolling content

The product and documentation was tested for:

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

The product and documentation was tested for:

• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links

The product and documentation was tested for:

• Pages have a meaningful title specified in the TITLE element

The product and documentation was tested for:

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

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

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

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

• Visual indication of the location of the focus

There are no multipoint or path-based gesture actions.

The product and documentation was tested for:

• There are no single pointer operations.

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

There are no functions that require motion of the device.

The product and documentation was tested for:

• Properly set lang attribute for each page

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

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

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

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

The documentation was tested for:

• The documentation does not allow for input or changes to data.

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

• The documentation does not detect input errors and does not allow for input or changes to data.

The product was tested for:

• Data is checked for input errors with an opportunity for the user to correct them

The documentation was tested for:

• The documentation does not allow for input or changes to data and does not check for or correct errors.

The product and documentation was tested for:

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

Exception :

1. 35543780 - In the Pluggable Database (PDB) list page , multiple static elements have same ID attribute : icon_external_link which might be read by voice assist

The product and documentation 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’ or 'invalid'
• 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:

1. 35292112 - Info button next to 'Provide Contacts for Operational Notifications and Annoucements' of Create DB UI in OCI is a button with no discernable text
2. 35292084 - Info button next to 'Create Admin Credentials' of Create DB UI in OCI is a button with no discernable text

The product and documentation was tested for:

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

In our documentation, we currently provide information  for keyboard-only and screen reader users.

Accessibility Guide for Oracle Cloud Services

Accessibility Features and Tips for Oracle Autonomous Data Warehouse

Documentation is provided in electronic formats.