Oracle Accessibility Conformance Report

The product was tested for:

• Images that convey information are embedded within standard user interface components and have a meaningful AccessibleName and/or AccessibleDescription
• Images that are decorative are embedded within standard user interface components and have neither an AccessibleName nor an AccessibleDescription
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

The documentation was tested for:

• Images that convey information have meaningful alternative text using ALT
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
• Titles for Objects and Applets are provided
• Controls have an associated name
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

The product was tested for:

• User interface component labels are associated with the fields they are labeling via the LabelFor and LabeledBy relations
• Headings are marked as such with a Group relation from the header to the items beneath the header
• Groups of components are marked as such, with a Group relation from the header of the group to the members of the group
• Style sheets are used only to change the layout and presentation on the screen
• Lists are contained within a List component
• Tables are contained within a Table component, implement the AccessibleTable interface, provide an AccessibleSummary, and contain include row and column headers where appropriate

Exceptions for product.

Bug 37724315 - Table headers names are not read by screen reader

When navigating through data in tables or data grids (E.g. Query result panel) using TAB key, screen reader will not read column headers names, i.e., when a user focuses a column header, Screen reader will read something like "Column header 1 of n" instead of reading the column header name, where "n" mean the total number of columns in table or grid.

Bug 37723383 - Attribute  'title' of object iframes is 'undefined'

When user opens an object, all object content will be rendered inside an iframe. The attribute 'title' of this iframe will always contain the value 'undefined'. As a result of this, when using a Screen Reader tool and opening an object, Screen Reader will read 'frame undefined' at some point when focusing opened object tab.

Bug 37604280 - JDBC not showinng connection string

For JDBC connections, connection string is not being displayed correctly. E.g., Making mouse hover on a JDBC connection won't show the proper connection string, it will only show the username. This affects Screen Reader functionality since will only read the username connection and no more details.

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

• The accessibility hierarchy is logical

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

The documentation was tested for:

• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

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

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

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

Exception for product:

Bug 37724518 - Low contrast between colors (white and light grey) presented in table graphic information for duality views builder when using vscode ligth theme

If VSCode is set to use a light theme, user will encounter low color contrast (ratio around 2.4:1 between white and light grey colors) in some information presented inside a table graphic.

The product was tested for:

• Text (and application) resizes up to 200% using the platform's built-in magnifier or zoom feature

The documentation 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 only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential

The documentation was tested for:

• Images of text are not used 

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

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.

The product and documentation were tested for:

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

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

Exception for product:

Bug 37724444 -  Unable to use duality views builder feature using keyboard only. This feature allows users to view and map data from both JSON documents and relational tables. Both views can be accessed at the same time. Without this feature, users can still view the data separately from the navigation tree. 
User will not be able to use Duality View feature using keyboard only because of following reasons:

• User will be unable to add a root table for duality view creation.
• Graphic representation of tables in Duality View Builder will never be focused and, also will not be read by Screen Reader tool.

The documentation was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes

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

• Single character keyboard shortcuts are only active when that component has focus. Turn off, Remap are not available

The documentation was tested for:

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

The product and documentation were tested for:

• Time limits are not used

The product and documentation were tested for:

• There is no moving, blinking, or scrolling content.

The product and documentation were tested for:

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

The product was 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 does not apply.

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

• The name of the software application is meaningful

The documentation was tested for:

• Pages have a meaningful title specified in the TITLE element

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

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

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

• Oracle non-web software products including bundles, suites of software do not behave as a set of software programs as the term is defined. Therefore this guideline doesn't apply.

The documentation was tested for:

• Pages are contained in a "site map"
• 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 product and documentation were tested for:

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

The product and documentation were tested for:

• Visual indication of the location of the focus.

The product and documentation was tested for:

• The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

The product and documentation were tested for:

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

The product and documentation were tested for:

• There are no single pointer operations.

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

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

The product and documentation were tested for:

• There is no dragging movement

The product and documentation were tested for:

• Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.

The product was tested for:

• Properly set locale/language

The documentation was tested for:

• Properly set lang attribute for each page

The product was tested for:

• Properly set locale/language for text passages that are in a different language than that of the software

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 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 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 were 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 product was 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 does not apply.

The documentation was tested for:

• There are no navigational mechanisms that are repeated

The product and documentation were tested for:

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

The product and documentation were tested for:

• Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.

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:

• Content does not require user input

The product was tested for:

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

Exceptions for product:

Bug 37723245 - Screen Reader tool reading incorrect shortcut to navigate through object subtabs

When opening an object, (e.g. a table) user is unable to navigate through object subtabs, e.g. (COLUMNS, DATA, DETAILS, DEPENDENCIES, SQL, etc.) .
When using Screen Reader tool and opening an object, screen reader will tell user to issue CTRL + PAGE_DOWN shortcut to navigate through object subtabs, but this shortcut does not work.

Workaround: User can navigate through object subtabs using arrow keys when a subtab is focused.

Bug 37730373 - ACC: Screen reader will not read dropdown options when navigating through them

When user interacts with input dropdowns, screen reader tells the user to use arrow keys for moving through available options, but these options are not read by the tool.

Workaround: User first needs to type "SPACE BAR" when focusing an input dropdown, and only then, use arrow keys for navigating through available options. This way, screen reader tool will read content correctly as user moves through the available dropdown options.

The documentation was tested for:

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

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:

• Content does not require user input

The product was tested for:

• 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 allow for input or changes to data.

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

The product and documentation were tested for:

• A mechanism is available to assist the user with any authentication step that utilizes a cognitive functional test.

The product was tested for:

• Event notification of changes to names, states, properties and values is available to assistive technologies

Exceptions

37927872 – Screen reader will not read extension details tab

When extension is installed in VS Code, the Welcome page will be shown to the user with extension details. This info will not be read by Screen Reader tool.

Workaround: When user installs extension from VSCode Marketplace site (https://marketplace.visualstudio.com/items?itemName=Oracle.sql-developer), the same information described above is shown and Screen Reader is able to read it correctly.

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.

The product was tested for:

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

The documentation was tested for:

• There are no status messages.

The product and documentation were tested for:

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

The product and documentation were tested for:

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

The documentation was tested for:

• In the product documentation, the User Guide currently provides information regarding our accessibility modes, and also other information for keyboard-only and screen reader users of SQL Developer. View the following documentation for more information.
• https://docs.oracle.com/en/database/oracle/sql-developer/index.html

Not Applicable

Not Applicable

Not Applicable