Oracle Accessibility Conformance Report

The product and documentation were tested for:

• Images that convey information have descriptive alternative text
• Images that are decorative are marked up using ALT=”” or CSS background images
• Controls have an associated name 
• Time-based media is not used
• Client-side image maps are not used
• Non-text characters are not used
• CAPTCHAs are not used

The product and documentation were 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 at the discretion of the application author
• 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

During testing the following defects were discovered:

• 34285625 - "Git Repository" is read by assistive technology for each selected radio option in new workspace dialog
• 34285663 - In Maven Browse page, 'Page Size' is read three times while using assistive technology
• 34285762 - Tooltip in linked builds cannot be invoked using the mouse

The product and documentation were tested for:

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

Application authors can control the presentation order of UI elements on the screen, and when they do, that is reflected in the DOM and in the navigation sequence. The generated application pages are properly linearized without loss of meaning or context.

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

The Product was tested for:

• Text can be resized in the browser up to 200% without loss of functionality

The product and documentation were tested for:

• Images of text are not used

The product and documentation were tested for:

• Vertical and Horizontal scrolling with 400% zoom. With this, there is no loss of information or content overlapping, with the exception noted below.

During testing the following defects were discovered:

• 34284172 - Two dimensional scrolling present in various places throughout the development UI, when zoomed at 400%

The product and documentation were tested for:

• Minimum non-text Contrast of at least 3:1 against adjacent colors.  The presence of visual information for identifying user interface components and states where applicable. Use of graphics required to understand content.

During testing the following defects were discovered:

• 34285737 - In Maven Artifact the Search Page current date in date picker doesn't have enough color contrast

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

During testing the following defects were discovered:

• 34285610 - In Maven Uploader page, 'Classifier' placeholder text gets partially hidden on changing the text spacing
• 34285745 - In Admin Repositories, 'Max Snapshots' label and 'required' icon in input number textfield overlap on text spacing
• 34288540 - File icon and file name in breadcrumbs not aligned when increasing text spacing in Git UI

The product and documentation were tested for:

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

During testing, the following defects were discovered:

• 34285770 - Dismissing popups caused by oj-combobox and oj-label in a table leads to loss of focus from element to row

The product and documentation were 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
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

During testing the following defects were discovered:

• 34285743 - In the Issues Landing Page, user cannot delete a search when assistive technology is running
• 34284196 - In several dialogs in the Environments and Project Admin areas of our UI, when a user clicks enter with a button highlighted while assitive technology is running, it invokes the wrong action.
• 34285751 - Unable to tab to next item when row is expanded in versions table while resolving vulnerability reports in a build
• 34284255 - In Maven Upload page, 'Remove all files' button is not getting activated using Enter Key
• 34288544 - Announcement content preview not reachable by keyboard when assitive technology is running

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

• There are no single character keyboard shortcuts.

The product and documentation were tested for:

• Time limits are not used by default in a generated application.

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 2 Hz and 55 Hz

The product and documentation were tested for:

• A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

The product and documentation were tested for:

• Pages have a meaningful title specified in the TITLE element

The product and documentation were tested for:

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
• The order of navigation is determined by the application author and follows the sequence of components as they occur in the DOM which is also the order in which they are displayed on the page. 

During testing the following defects were discovered:

• 34285732 - Focus lost on clicking Next/Back buttons in date picker in Maven and Node Package Manager
• 34283894 - Focus is lost or broken when tabbing into the Navigation List in Maven and Node Package Manager
• 34283846 - Focus Order and Sequencing Issues in Maven, Node Package Manager, and Announcements

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

• 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 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

During testing the following defects were discovered:

• 34283918 - Focus indicator goes missing when overflow is specified as "hidden/scroll/auto"

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:

• Properly set lang attribute for each page.

The product and documentation were tested for:

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

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

• Images and controls are used and identified consistently throughout the product. Where the author introduces their own icons and components into the app, they should take care to use them consistently.

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

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

The product was tested for:

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

During testing, the following defects were discovered:

• 34284234 - In environments, there is no useful error when the environment name is too long

The documentation was tested for:

• Content does not require user input

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

During testing, the following defects were discovered:

• 29443460 - There is an empty iframe src element on the main page. The iframe on the page is an internal implementation and not intended for display. 
• 33107337 - Some pages do not have a title set by default. The page author can easily add a page title manually for the few cases where it is not created by default.

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

The Product uses standard HTML5 components and Oracle JET components which properly expose name (label) and role. In cases where the author chooses to write a custom UI component, they would need to use the appropriate APIs to expose the name, role, and other relevant attributes.

The product was tested for:

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

During testing the following defects were discovered:

• 32763864 - Message popups shown from application are not read by assistive technology.

The documentation was tested for:

• There are no status messages

The product documentation describes:

• special keystrokes needed to operate controls

Accessibility-related documentation can be found at: https://docs.oracle.com/en/cloud/accessibility/accessibility-features-and-tips-visual-builder-cloud-service.html#GUID-DB272DE2-93[…]E94-A3BBDF25A253

A reference guide for keystrokes and touch gestures can be found at: http://www.oracle.com/pls/topic/lookup?ctx=jetlatest&id=OJACC

Product documentation is in electronic format.