Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Cloud Infrastructure (OCI) Documentation January 2024

Product Description:

Oracle Cloud Infrastructure customer-facing documentation located at https://docs.oracle.com/en-us/iaas/Content/home.htm

Date:

26-Jan-2024

Contact Information:

accessible_ww@oracle.com

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports
The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Partially Supports
Some functionality of the product does not meet the criteria.
Does Not Support
Majority of functionality of the product does not meet the criteria.
Not Applicable
The criteria are not relevant to the product.

WCAG 2.1 Report

Table 1 also documents conformance with:

  • Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria
Conformance Level
Remarks and Explanations
1.1.1 Non-text Content (Level A)Partially Supports

The 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.
  • Controls have an associated name.
  • Text summary or alternative is provided for time-based media.
  • Non-text characters are not used.
  • No CAPTCHAs are used.

Exception:

  • OCI JIRA: CE-4264 - Remove alt text from decorative image on home page
  • OCI JIRA: TC-29177 - Remove alt text from decorative images and provide clear alternative text for graphics on the Getting Started and Learn About Oracle Cloud Basics pages
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Supports

This documentation was tested for:

  • There is no pre-recorded audio only or video only content.
1.2.2 Captions (Prerecorded) (Level A)Supports

This documentation was tested for:

  • Pre-recorded video includes closed captions
  • Pre-recorded video is an alternative for text and labelled as such.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Supports

This documentation was tested for:

  • Pre-recorded video includes an alternative to the video.
1.2.4 Captions (Live) (Level AA)Supports

This documentation was tested for:

  • No live audio content in video is being used.
1.2.5 Audio Description (Prerecorded) (Level AA)Supports

This documentation was tested for:

  • Pre-recorded video includes a second version (or the only version) of the video that has audio descriptions built into it on the main audio track
1.3.1 Info and Relationships (Level A)Partially Supports

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

Exception:

  • OCI JIRA: CE-4675: The links List in the footer of documentation pages not marked up as lists
1.3.2 Meaningful Sequence(Level A)Supports

The documentation was tested for:

  • The sequence of elements in the DOM matches a logical reading sequence.
1.3.3 Sensory Characteristics(Level A)Supports

The 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.
  • Instructions provided which refer to graphics included a reference to the text alternative of the graphic.
1.3.4 Orientation (Level AA)Supports

This documentation was tested for:

  • Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)Supports

This documentation was tested for:

  • There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)Supports

The 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.
1.4.2 Audio Control(Level A)Supports

This documentation was tested for:

  • No automatically playing audio is used.
1.4.3 Contrast (Minimum) (Level AA)Supports

This 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.
1.4.4 Resize text(Level AA)Supports

This documentation was tested for:

  • Text can be resized up to 200% without loss of content or functionality.
1.4.5 Images of Text(Level AA)Supports

This 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.
1.4.10 Reflow (Level AA)Supports

This documentation was tested for:

  • Text information reflows so that only one direction of scrolling is required while at 400% zoom.
  • An alternative mobile user interface is available and is accessed from the main application.
  • Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.
1.4.11 Non-text Contrast (Level AA)Supports

This documentation was tested for:

  • Non-text items have a contrast ratio of at least 3:1.
1.4.12 Text Spacing (Level AA)Partially Supports

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

Exception:

  • OCI JIRA: CE-4670 - Fix spacing issue on Search box label
1.4.13 Content on Hover or Focus (Level AA)Partially Supports

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

Exception:

  • OCI JIRA: CE-4324 - Not able to dismiss tooltips in Firefox
  • OCI Jira: CE-4325 - Make Tooltips hoverable
2.1.1 Keyboard(Level A)Partially Supports

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

Exception:

  • OCI JIRA: CE-4674 - Should be able to select the language from the language selector menu on the top of documentation pages using just the keyboard
2.1.2 No Keyboard Trap (Level A)Supports

This documentation 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.
2.1.4 Character Key Shortcuts (Level A)Supports

This documentation was tested for:

  • Single character keyboard shortcuts are only active when that component has focus.
2.2.1 Timing Adjustable(Level A)Supports

This documentation was tested for:

  • Time limits are not used.
2.2.2 Pause, Stop, Hide (Level A)Supports

This documentation was tested for:

  • There is no moving, blinking, or scrolling content.
2.3.1 Three Flashes or Below Threshold(Level A)Supports

This documentation was tested for:

  • No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
2.4.1 Bypass Blocks(Level A)Partially Supports

This documentation 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.

Exception:

  • OCI JIRA: CE-4671 - As tested on the About Oracle Database Service for Azure page, a "Skip to Main Content" link is provided but not visible when testing on a Mac using Firefox. The "Skip to Main Content” link is not available without explicitly searching for it using “Ctrl + F".
2.4.2 Page Titled(Level A)Partially Supports

This documentation was tested for:

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

Exception:

  • OCI JIRA: CE-4265 - The title of the home page needs to be updated to include 'Documentation'.
2.4.3 Focus Order(Level A)Supports

This documentation was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence.
2.4.4 Link Purpose (In Context)(Level A)Supports

This 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.
2.4.5 Multiple Ways(Level AA)Supports

This documentation was tested for:

  • Pages can be found using the provided "search" function.
  • Pages are in a site table of contents.
  • Pages are fully inter-linked to one another.
  • Page contains controls that enable reaching other pages.
2.4.6 Headings and Labels(Level AA)Supports

This documentation was tested for:

  • Headers describe the topic or purpose of the content below them.
  • Labels describe the purpose of the associated field.
2.4.7 Focus Visible(Level AA)Partially Supports

This documentation was tested for:

  • Visual indication of the location of the focus.

Exception:

  • OCI JIRA: CE-4672: On the Getting Started page Focus is not visible on
    • Oracle Cloud, Help Center, and OCI Documentation links and the Try Free Tier and thumbs up and down buttons
    • dropdowns
    • Copy and Tryit options in the codebox
  • OCI JIRA: CE-4675: On the top right of the documentation pages the Language selector menu should not have a hidden element that is focusable
2.5.1 Pointer Gestures (Level A)Supports

This documentation was tested for:

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Supports

This documentation was tested for:

  • There are no single pointer operations.
2.5.3 Label in Name (Level A)Supports

This 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.
2.5.4 Motion Actuation (Level A)Supports

This documentation was tested for:

  • There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)Supports

This documentation was tested for:

  • Properly set lang attribute for pages.
3.1.2 Language of Parts(Level AA)Supports

This documentation was tested for:

  • Proper use of lang attribute for text passages that are in a different language than that of the page
3.2.1 On Focus(Level A)Supports

This 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.
3.2.2 On Input(Level A)Supports

This 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.
3.2.3 Consistent Navigation(Level AA)Supports

This documentation was tested for:

  • Pages which are grouped together into sets with a common navigation mechanism utilize that mechanism in the same fashion. Navigation elements appear in the same relative order across pages.
3.2.4 Consistent Identification(Level AA)Supports

This documentation was tested for:

  • Images and controls are used and identified consistently throughout the product.
3.3.1 Error Identification(Level A)Supports

This documenation was tested for:

  • The documentation does not have input fields, except for the search and feedback fields.
3.3.2 Labels or Instructions (Level A)Supports

This documentation was tested for:

  • Labels or instructions are provided when the product requires user input.
3.3.3 Error Suggestion (Level AA)Supports

The documentation was tested for:

  • The documentation does not have input fields, except for the search and feedback fields that do not have errors.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

This documentation was tested for:

  • The documentation does not allow for changes to data.
4.1.1 Parsing(Level A)Supports

This documentation was tested for:

  • This criterion is always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)Partially Supports

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

Exceptions:

  • OCI JIRA: CE-4675: The search field on the top of the documentation pages is missing required attributes
4.1.3 Status Messages (Level AA)Supports

This documentation was tested for:

  • There are no status messages.

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria
Conformance Level
Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot ApplicableThe product is designed to be isolated from the underlying platform.
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsSupports

This documentation was tested for:

  • User controls for the selection of captions are provided at the same menu level as the user controls for volume or program selection.
503.4.2 Audio Description ControlsSupports

This documentation was tested for:

  • Audio descriptions are built into the video on the main audio track and the user controls for the selection of audio is at the same menu level as the user controls for volume or program selection.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

There are no accessibility or compatibility features to document. Documentation uses standard HTML specifications to support accessibility.

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Oracle Cloud Infrastructure documentation is in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.

back to top

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.