Oracle Accessibility Conformance Report

The product 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)
• Client-side image maps specify the ALT attribute on each AREA element.
• CAPTCHAs are not used

Exception:

• Bug 34835454: The Dashboard icon(which is a non text content) at the top left is missing alternate text across the product.

The Documentation was tested for:

• Images that are decorative are marked up using ALT=”” or CSS background images.

Exception:

• Doc Bug 34890775: The images present across the documentation pages do not have alternate text or a role of none or presentation.

The product 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 captions/summaries where appropriate

Exception:

• Bug 34834730: Dashboard pages with tables across the product have confusion between layout tables and data tables which can cause the user to read incorrect data.

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
• Layout tables use appropriate markup
• Groups of components are marked up with their description

Exception:

• Doc Bug 34890726: Pages with tables across the product documentation does not have accessible text which can restrict the user to find, navigate and understand the tables present.

The product and documentation was tested for:

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

The product and documentation was tested for:

• Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation or sound.

The product and documentation was tested for:

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

The product and documentation was tested for:

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

The product and documentation was tested for:

• Information conveyed by color has a contrast ratio of at least 3:1

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

• Bug 34835734: The minimum required contrast ratio between foreground and background colors in tabs of Apex tool is not maintained. This can result in incorrect visual representation for the user. 
• Bug 34835514: The minimum required contrast ratio between foreground and background colors in Current Outages and Historical Outages dashboards of Oracle Analytics Server is not maintained. This can result in incorrect visual representation for the user. 

The product and documentation was tested for:

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

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

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

Exception:

• Doc Bug 34890671: At 400% zoom, the content in the document is not visible. Only search button is visible. The same is reflected for all different pages in the documentation.

The product and documentation was tested for:

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

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

The documentation was tested for:

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

The product and documentation was tested for:

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

The product and documentation was tested for:

• Movement of focus through controls only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.

The product and documentation was tested for:

• There are no single character keyboard shortcuts.

The product was tested for:

• Time limits in the product can be adjusted to at least 10 times longer before encountered.

The documentation was tested for:

• Time limits are not used

The product and documentation was tested for:

• There is no moving, blinking or scrolling content
• No auto updating information that starts automatically or is presented in parallel with other content.

The product and documentation was tested for:

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

The product and documentation was tested for:

• There are no repeated blocks of content on multiple webpages.

The product and documentation was tested for:

• Pages have a meaningful title specified in the TITLE element 

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

Exception:

• Doc Bug 34890831: Links across the pages of the documentation do not have discernible text which describe their purpose to the users.

The product and documentation was tested for:

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

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

• Visual indication of the location of the focus

The product and documentation was tested for:

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

The product and documentation was tested for:

• There are no single pointer operations

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

Exception:

• Bug 34834664: Label/Form is either missing or their content does not have visible text as part of their accessible name in login page and in all dashboards under Outage analytics and Distribution analytics. This will restrict the user to get the names, roles or state (collapsed/expanded).

The product and documentation was tested for:

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

The product and documentation was tested for:

• Properly set lang attribute for pages.

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

• There are no navigational mechanisms that are repeated.

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

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

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:

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

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

The documentation was tested for:

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

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

Exception:

• Bug 34835540: Violations for Structure in the dashboard as the id attributes are not unique across all the pages.
• Doc Bug 34890805: Violations for Structure across all the pages of the documentation as the lists attributes are structured incorrectly.

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

Exception:

• Bug 34834519: Screen reader is unable to read Hyperlinks and dropdowns in 6 pages (i.e Network Management Systems => Events=> Event Profile, Network Management Systems => Switching => Abnormal Device=> Abnormal devices table page, Network Management Systems => Switching => Switch Plans, Network Management Systems =>Damage Assessments=>Damage Assessments Summary, Network Management Systems => Storm Analysis=>Storm Analysis, Network Management Systems =>Reliability=>Reliability by Control zone hierarchy Overview in Network Management Systems (NMS) product. This may cause difficulty for the user to read colors or values present in its color range.
• Bug 34834550: Screen reader is unable to read dropdowns, search icon, window popup in Product Instance,Server Configuration,Schedule Configuration and Job Execution pages of APEX. The result may cause difficulty for the user to navigate and understand the functionality of these UI components.

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
• Custom controls have a meaningful programmatically exposed name
• Frames have a meaningful title specified in the title attribute

The product and documentation was tested for:

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

Oracle® Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition has instructions on how to configure accessibility.

Product documents are in electronic format.