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

The following tickets track the identified errors:

COMCON-900 - Icon on tool tips do not have text alternative in Compute plugin. This occurs for any tool tip on an info bubble (icon: i enclosed by a circle) on Compute list and detail pages as well Create Compute Instance dialog.

CSDK-678 - Image indicating left of screen has no label. This is encountered on any page where a compartment is needed to display data, if the user has not yet chosen a compartment.

The product 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
• Groups of components are marked up with their description
• Style sheets are used only to change the layout and presentation on the screen

The following tickets track the identified errors:

OUI-880 -  Form fields are not programmatically identified as required. This is due to the design in the component library, so all form fields across the site are assumed to be required unless they are labelled "optional" or "read only".

LBLP-468 -  List Table does not use column headers in Load Balancer access control rules.

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 included a reference to the text alternative of the graphic

This product has not yet been evaluated for this criteria.

The product was tested for:

• There are no text fields that collect information about the user.

The product was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight

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 following tickets track the identified errors:

OUI-955 - Link hover state fails contrast requirement. As this occurs in the component libraries, it will occur for hover appearance on all links across the site.

OUI-992 - Placeholder text in input fields fail contrast requirement. As this occurs in the component libraries, it will occur for placeholder text in all input fields across the site.

CSDK-677 - Tag filters side menu fails contrast requirement. As this occurs in the component libraries, any page that allows the user to filter by tags will display with too low a contrast ratio when no tag filter has been applied.

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

This product has not yet been evaluated for this criteria.

This product has not yet been evaluated for this criteria.

This product has not yet been evaluated for this criteria.

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

The product was tested for

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
• The ability to use the product with OS keyboard aids: StickyKeys and FIlterKeys.

The following tickets track the identified issues:

OUI-856 - Customer cannot see current selection on compartment selector when options overflow off screen. As this occurs in the component library, this will occur on any page that includes a compartment select combo-box.

OUI-844 - Customer cannot access time selection from keyboard when selecting a date in the date picker component. Time can still be directly added into the text input, in UTC format.

OUI-809 - Customer cannot access tool tip controls when component is within a group of form fields (that is, a field set). As this occurs in the component library, this will occur on any page that includes a field set grouping.

COMCON-891 - Compartment selector not accessible by keyboard on Firefox for Autoscaling Configurations under Compute plugin.

The product was tested for:

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

The product does not use single character keyboard shortcuts.

Time limits are not used.

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 following ticket tracks the identified errors:

CSDK-518 -  Customer must navigate separate "Skip to main content" links on page for primary navigation and feature navigation. As this occurs in the framework, it affects all pages across the site.

The product was tested for:

• Web pages or documents or software have titles that describe topic or purpose.

The following tickets track the identified errors:

UIPLAT-3151 Improve browser title and history to have more specific names. Currently page titles describe the topic (particular plugin selected) but not the specific purpose (functionality of each page). This occurs for page title on the home page and on all pages associated with Compute, VCN, Load Balancer, Block Storage, and Object Storage.

The product was tested for:

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

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 can be found using the provided "search" function
• Pages are in a site table of contents

The product was tested for:

• Headings and labels the describe topic or purpose.

The product was tested for:

• The logical movement through the focusable components using only the keyboard can be detected easily.

There are no multipoint or path-based gesture actions.

There are no single pointer operations.

The product has been tested for:

• User interface components that include 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 was tested for:

• Properly set lang attribute for pages

The following tickets track the identified errors:

CSDK-616 - Iframes within webpage may not report language programmatically

The product was tested for:

• No text passages 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 following tickets track the identified errors:

VCNLP-505 Context changes when user attempts to choose a compartment while creating a subnet. This occurs only on the Create Subnet dialog within the VCN plugin.

OUI-848 -  Whenever navigating controls as a group of form fields, context is lost when collapsing options. As this occurs in the component library, this will occur on any page that includes a field set grouping.

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

The following tickets track the identified errors:

OUI-824 - Customer loses focus context when tree select component like Compartment Select closes. As this is in the component library it will occur on any page that has a compartment select field.

OUI-778 - Customer loses focus context when closing modals and dialogs. As this is in the component library it will occur when closing any modal or dialog that has been opened from another popup.

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:

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

The product was tested for:

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

The following tickets track the identified errors:

OUI-814 - Screen reader unable to identify input. Screen reader does not speak correct label for Compartment Select field. As this is in the component library it will occur for every compartment select field across the site.

OUI-991 - FileSelector component has a decorative icon without a label. As this is in the component library it will occur on any page with a file selector component for file upload.

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:

• Data can be reviewed, corrected, and confirmed by the user before they are finalized

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

The following tickets track the identified errors:

UX-8257 - Multiple elements found with duplicate identifiers. Found in all pages housed within the central navigation, specifically left hand navigation and header.

CSDK-673 - Customer cannot use Image Source selector in the Compute Create Instance form with some specific screen readers.

OUI-986 - Customer cannot use form controls DatePicker, DatePickerRange, RichSelect with specific screen readers since they use the same key events as the screen readers. As this occurs in the component library it occurs on any page with these form controls.

The product was tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, etc.
• 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

The following tickets track the identified errors:

LBLP-467 - Screen reader does not identify dialog contents when opened in terminate dialogs in Networking plugin.

OUI-985 - Card component has incorrect role when used decoratively.

COMCON-899 -  Summary view toggle link in Create Instance form has no programmatically determined role in Compute Plugin.

This product has been tested for:

• Status messages can be programatically determined such that they can be identified by assistive technologies

The following tickets track the identified errors:

CSDK-681 - When a dialog is opened to create/update/delete any resource, there is no status message announced that indicates the success of that operation. Since this occurs in the component libraries it will occur for all create/update/delete dialogs across the site.

There are no accessibility or compatibility features to document. Product uses standard HTML specificiations to support accessibility.

Product documentation is in electronic format.