Oracle Accessibility Conformance Report

The documentation was tested for:

• Images that convey information have meaningful alternative text using ALT - See Bug#27816789 for issues with details on images not having meaningful text
• No images that are decorative are used
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table) - See Bug#27729514 for issues with EBNF diagrams in the X Dev API section 
• CAPTCHAs are not used

The documentation was tested for:

• 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
• Style sheets are used only to change the layout and presentation on the screen
• The documentation contains no fields that would require user interface component labels, and therefore also no group of components

The documentation was tested for:

• HTML markup and coding of text provides a correct and logical reading sequence

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

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

The documentation was tested for:

• Large-scale text has a contrast ratio of at least 3:1
• All other text has a contrast ratio of at least 4.5:1

No images of text are used.

The documentation was tested for:

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

The documentation was tested for:

• Images of text are not used

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

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

• Time limits are not used in the documentation

The documentation was tested for:

• The documentation has no moving, blinking, scrolling, or auto-updating content

The documentation was tested for:

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

The 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

The documentation was tested for:

• Pages have a meaningful title specified in the TITLE element

The documentation was tested for:

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

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

• 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 documentation was tested for:

• Headers describe the topic or purpose of the content below them
• The documentation doesn't have any user interface controls that would require labels

The documentation was tested for:

• Visual indication of the location of the focus

The documentation was tested for:

• Properly set lang attribute for each page

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

• The documentation has no user interface components whose settings or values can be changed

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

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

The documentation was tested for:

• No input fields are available in the documentation

The documentation was tested for:

• No input fields are available in the documentation

The documentation was tested for:

• No input fields are available in the documentation

The documentation was tested for:

• No input fields are available in the documentation

The 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
• Pages validate to the HTML specification

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.

No product-specific accessibility features for this product and no accessibility and compatibility features documentation.

However, the \G line terminator in the mysql command-line client and in MySQL Shell is recommended for accessibility mode.

Product documentation is in electronic format.