Oracle Accessibility Conformance Report

The product and dcoumentation were 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
• 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
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

The product and dcoumentation 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.
• 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:

• Bugs 37709142 : In the Database Metrics Screen for "Start Time" and "End Time" textboxes the visually associated labels in the UI are blank, they need to have a value and match with that of the forms label.
• Bug 37709158:  In the Application properties screen, the row headers for the columns 'Property Key', 'Value' and 'Description' are blank, they should have a value associated with each of the 3 columns.

The product and dcoumentation were tested for:

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

The product and dcoumentation 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.
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic.

The product and dcoumentation were tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.
• A fixed display orientation is required for essential functionality.

The product and documentation were tested for :

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

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

• No automatically playing audio is used.

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

Exceptions:

• Bugs 37709262: Part of “Home Screen”, Large and small labels are not matching the 3:1 and 4.5:1 standards and should be standardized across the screen.  
• Bug 37709311: Part of “AWR Report Screen”, Large and small labels are not matching the 3:1 and 4.5:1 standards and should be standardized across the screen.  .
• Bug 37709405 : Part of “Top SQL Screen”, Large and small labels are not matching the 3:1 and 4.5:1 standards and should be standardized across the screen.  
• Bug 37709414 : Part of “DBMS Jobs Screen”, Large label is not matching the 3:1 standards and should be standardized.  
• Bug 37709485 : Part of “Database Metrics Screen”, Large and small labels are not matching the 3:1 and 4.5:1 standards and should be standardized across the screen.  
• Bug 37709523: Part of “Database Sessions Screen”, Large and small labels are not matching the 3:1 and 4.5:1 standards and should be standardized across the screen.  
• Bug 37709555:  Part of “Application properties” screen, Large and small labels are not matching the 3:1 and 4.5:1 standards and should be standardized across the screen.  

The product and dcoumentation were tested for:

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

The product and dcoumentation were tested for:

• Images of text are not used.

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

Exceptions:

• Bugs 37709875: Part of the "Home Screen", After 400% zoom towards manipulated view, the screen was only partially visible. As a result, User is  unable to navigate to part of screen using slide bars both vertically and horizontally.
• Bug 37709903: Part of the "AWR Reports Screen", After 400% zoom towards manipulated view, the screen was only partially visible. As a result, User is  unable to navigate to part of screen using slide bars both vertically and horizontally.

The product and dcoumentation were tested for:

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

The product and dcoumentation 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 dcoumentation 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.
• Information appears on hover or focus using default browser behavior, such as the title attribute of components.
• There is no content that appears on hover or focus.

The product and dcoumentation 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, including those listed in the product documentation.

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

• There are no single character keyboard shortcuts.

The product and dcoumentation were tested for:

• Time limits are not used.

The product and documentation were tested for :

• There is no moving, blinking, scrolling or auto-updating content.

The product and documentation were tested for:

• There are no portion part of application screens that flickers or flashes with a frequency between 2 Hz and 55 Hz.

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

• Pages have a meaningful title specified in the <title> element.

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

• Pages can be found using the provided "search" function.
• Pages are fully inter-linked to each other.
• Page contains controls that enable reaching all pages.

Exceptions:

• Bug 37709683 : Currently  the navigation option exists as the option to reach all the UI screens from within the Task flow and search box function in the Task Flow is missing. That Search Box option could provide user the 2nd alternative option to navigate as per the requirement.

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

• Visual indication of the location of the focus.

The product and documentation were 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 dcoumentation 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.
• When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event.
• There are no single pointer operations.

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

• All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.
• The functionality of dragging movements are determined by the user agent and not modified by the author.

The product and dcoumentation 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 function can be achieved through a different control in the same software that meets this criterion.

• The target is in a sentence or its size is otherwise constrained by the line-height of non-target text.

The product and dcoumentation were tested for:

• Properly set lang attribute for each page.

The product and dcoumentation 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 dcoumentation 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 dcoumentation 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.
• In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components.

The product and dcoumentation 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 every time.

The product and dcoumentation were tested for:

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

The product and dcoumentation were tested for:

• None of the following help mechanisms exist: Human contact details, human contact mechanisms, self-help options, automated contact mechanisms.

The product and dcoumentation were tested for:

• When input errors are detected, they are described to the user in text, including identifying the item where the error occurred.

Exceptions:

• Bug 37709759 : In the "Database Metrics" screen, the input error for the 'Start Time' and 'End Time' fields  is not detected and visible to the end user.

The product and dcoumentation were tested for:

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

The product and documentation were tested for :

• User input is not required.

The product and documentation were tested for:

• Changes to data are not allowed.

The product was tested for: 

• There are no occurrences of information that the user needs to enter which has been previously entered.

The product and dcoumentation were tested for:

• Authentication does not rely upon a cognitive functional test.

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

The product and dcoumentation were tested for:

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

The product and dcoumentation were tested for:

• The accessibility features are documented in the Retail Data Store User Guide.

Exceptions:

• Bug 37709803 : Some of the core accessibility features such as keystrokes required to navigate the UI, compatibility with a screen reader or other assistive technologies, ability to read alternative texts for images without texts in the product need to be described in the RDS documentation including user guide, security guide, admin guides and/or install guides as applicable.

Product documentation is in electronic format.