Oracle Accessibility Conformance Report

The GUI and the documentation were tested for:

• CAPTCHAs are not used,
• There are no time-based media and content aimed towards creating specific sensory experience.
• If images (decorative or otherwise) and input controls have alternative texts which can be read by screen readers.
• If charts and graphs have descriptive and summary information relaying purpose of the content and a short state information.

The CLI was tested for:

• Images are not used.
• Non-text characters are not used.
• CAPTCHAs are not used.

The GUI was tested for:

• User interface component labels are associated with the fields they are labeling.
• Groups of components are marked up with their description.
• Lists follow standard text patterns for rendering lists and are available in text.
• Trees follow standard text patterns for rendering trees and are available in text.
• Tables follow standard text patterns for rendering tables and are available in text.

The CLI was tested for:

• Headings follow standard text patterns for rendering headings.
• Paragraphs follow standard text patterns for rendering paragraphs.
• Lists follow standard text patterns for rendering lists.
• Tables follow standard text patterns for rendering tables.

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

Exceptions:

• Screen readers fail to parse structure for some of groups, lists, trees and tables. Bug ID 38106961.
• Screen readers fail to read column header descriptions of tables. Bug ID 34333800.
• Screen readers fail to read editable widget descriptions until they selected. Bug ID 38111827.

The GUI was tested for:

• The sequence of elements in dialogs matches a logical reading and input sequence.

The CLI was tested for:

• The correct reading sequence is discernible when output is rendered to a file.

The documentation was tested for:

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

The GUI, CLI, 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.

The GUI and the documentation were tested for:

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

The CLI was tested for:

• Text display orientation in a command line user interface is based on the ability of the terminal application used.

The GUI, CLI, and documentation were tested for:

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

The GUI and CLI were tested for:

• Information conveyed by color is available in text.

The documentation was tested for:

• Information is not conveyed using color.

The GUI and the 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 CLI was tested for:

• Text has a contrast ratio of at least 4.5:1.

The GUI and the documentation were tested for:

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

The CLI was tested for:

• Text can be resized up to 200% without loss of content or functionality when rendered in a GUI-based terminal application that supports text rendering sizes up to 200% larger than normal.

The GUI, CLI, documentation were tested for:

• Images of text are not used.

The GUI and documentation were tested for:

• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.
• Text information reflows so that only one direction of scrolling is required while at 400% zoom.

The CLI was tested for:

• Text information can reflow with only one direction of scrolling when rendered in a GUI-based terminal application that supports text rendering sizes up to 400% larger than normal.

The GUI and documentation were tested for:

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

The CLI was tested for:

• Graphics are not used.
• Non-text characters are not used.

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

The GUI and CLI were tested for:

• Text is not rendered using markup languages.

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

The CLI was tested for:

• There is no content that appears on hover or focus.

The 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.
• Information appears on hover or focus using default browser behavior, such as the title attribute of components.

Exceptions:

• GUI has no easy way of activating/showing tooltips as a dialog is navigated via keyboard and tooltips are not persistent. Bug ID 34317912.

The GUI, CLI, and documentation were tested for:

• Ability to perform functions from the keyboard only,
• Proper operation of unique keystrokes, including those listed in the product documentation.

Exceptions:

• Bug ID 34356564: User is not able to navigate through Details pane using keyboard, he can use mouse only. Tab/Shift+Tab, ArrowUp/Down controls does not let user to navigate through separate details or scroll them up/down. Windows screen-readers can't read separate details as well, only macOS screen-reader can.
• Bug ID 38106789: User is not able to navigate through Global and Machine toolbars using keyboard, he can use mouse only. Tab/Shift+Tab controls doesn't move focus from one tool button to another. User is not able to switch between Global and Machine tools triggering corresponding button by keyboard, instead user can switch between tools via configurable keyboard shortcuts or through menu actions.

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

• Movement of focus through each control only using the keyboard. Keyboard can be captured for a reason (so it has logically justified "keyboard trap" which is a part of our functionality). The user is adviced of the method for releasing keyboard allowing to move focus away.

The CLI was tested for:

• Keyboard focus is not used.

The GUI and documentation were 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 CLI was tested for:

• There are no single character keyboard shortcuts.

The GUI, CLI, and documentation were tested for:

• Time limits are not used.

The GUI, CLI, and documentation were tested for:

• There is no moving, blinking or scrolling content.

The GUI, CLI, and documentation were tested for:

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

The GUI and CLI were tested for:

• Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is always automatically met.

The documentation was tested for:

• A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.

The GUI and CLI were tested for:

• The name of the software application and its dialogs are meaningful.

The documentation was tested for:

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

The GUI and documentation were tested for:

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

The CLI was tested for:

• Keyboard focus is not used.

Exceptions:

• Bug ID 38106997: Navigating Preferences/Settings dialogs and File Manager machine tool using macOS screen-reader (VoiceOver) follows invalid focus order.

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

• Links are not used in the product.

The GUI and CLI were tested for:

• Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is always automatically met.

The 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 each other.
• Page contains controls that enable reaching all pages.

The GUI and documentation were tested for:

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

The CLI was tested for:

• Headers describe the topic or purpose of the content below them.
• Labels are not used.

The GUI and documentation were tested for:

• Visual indication of the location of the focus.

The CLI was tested for:

• Keyboard focus is not used.

Exceptions:

• VM list in the manager UI has no keyboard focus indicator. Bug ID 34356068.

The GUI and documentation were tested for:

• Visual indication of the location of the focus is not obscured.

The CLI was tested for:

• Keyboard focus is not used.

The GUI, CLI, and documentation were tested for:

• There are no multipoint or path-based gesture actions.

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

The CLI was tested for:

• There are no single pointer operations.

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

• User interface components are not used.

The GUI, CLI, and documentation were tested for:

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

The GUI was tested for:

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

The CLI, and documentation were tested for:

• There are no functions that require dragging movement.

The GUI and documentation were tested for:

• The size of the targets for pointer inputs is at least 24 by 24 pixels.
• In some exceptional cases (buttons) undersized targets have spacing required to avoid intersecting other targets.
• In other exceptional cases (hyperlinks) undersized targets are in sentences or their size is otherwise constrained by the line-height of non-target text.

The CLI was tested for:

• There are no functions that require target selection.

The GUI was tested for:

• Properly set locale/language of the page.

The CLI was tested for:

• The CLI only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable.

The documentation was tested for:

• Properly set lang attribute for each page.

The GUI was tested for:

• Proper use of locale/language for text passages that are in a different language than that of the software.

The CLI was tested for:

• The CLI only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable.

The documentation was tested for:

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

The GUI and documentation were tested for:

• When an element receives focus, it does not result in a substantial change to the dialog, an additional change of keyboard focus, or the spawning of a pop-up window.

The CLI was tested for:

• Keyboard focus is not used.

The GUI, and documentation were tested for:

• Changes in the value of user interface components does not result in a substantial change to the dialog, an additional change of keyboard focus, or the spawning of a pop-up window.

The CLI was tested for:

• User interface components are not used.

The GUI and CLI were tested for:

• Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is always automatically met.

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

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

The CLI was tested for:

• Images and controls are not used.

The GUI was tested for:

• Self-help option is used and occurs in the same order relative to other page content throughout the product.

The CLI and documentation were tested for:

• No help mechanisms used.

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

• The documentation does not have input fields, except for the Search field.

The GUI, CLI and documentation were tested for:

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

The GUI and CLI were tested for:

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

The documentation was tested for:

• Content does not require user input

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

• The documentation does not require user input that modifies user controllable data.

The GUI and CLI were tested for:

• 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.
• In exceptional cases re-entering the information is essential because it's required to ensure the security or uniqueness of the content.

The documentation was tested for:

• The documentation does not require user input that can be cached.

The GUI, CLI, and documentation were tested for:

• No cognitive function tests used.

The GUI was tested for:

• Custom controls have a meaningful programmatically exposed name.

The CLI was tested for:

• User interface components are not used.

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

Exceptions:

• Bug ID 38172080: Some widgets have wrong or missing programmatically exposed names (visible only through screen-reader): Logs (machine tool) text-browser, Experience Mode and Search buttons (in Global Preferences and VM Settings dialogs), Shortcuts Filter text-editor (in Global Preferences dialog), Guest Screen canvas (of VirtualBoxVM), Home (global tool) text-browser, Font Scaling slider (in Global Preferences dialog), Boot Device Order list items (in VM Settings dialog), Storage Port combo-box (in VM Settings dialog), USB Filter Details dialog text-editors (in VM Settings dialog).
• Bug ID 38172113: Some widgets have programmatically exposed name repeated few times (visible only through screen-reader): Machines (global tool) tree, Extension (global tool) list, Media (global tool) tree and Location tool button, Network (global tool) lists and tables, Cloud (global tool) list, Snapshot (machine tool) tree, File Manager (machine tool) tool-buttons, Shortcut table (in Global Preferences), Language list (in Global Preferences), Storage tree and tool-buttons (in VM Settings), Port Forwarding table (in VM Settings), USB Filters list (in VM Settings), Shared Folders list (in VM Settings), User Interface Menu items (in VM Settings), User Interface Status items (in VM Settings), Cloud VM Settings table, Import/Export/NewVM/NewVD/CloneVD wizard tool buttons, Import/Export/NewCloudVM wizard trees, Status-bar indicators (of VirtualBoxVM), Virtual Media Selector list.

The GUI and CLI were tested for;

• Markup languages aren't used to generate the user interface.

The documentation was tested for:

• There are no status messages.

The GUI, CLI, and documentation were tested for:

• Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts.

The GUI, CLI, and documentation were tested for:

• Responds to platform settings for color, contrast, font type, font size, and focus cursor.

Exception

• On Windows VirtualBox GUI text size does not adapt to desktop font size change untill application is restarted. Bug ID 34343535.

There are no accessibility or compatibility features to document.

Product documentation is in electronic format.