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
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table), or the containers of the complex images are filled with simple image children whose information is exposed via AccessibleName and/or AccessibleDescription
• Data tables include a summary or caption, programmatically connected with the table as the AccessibleTable's AccessibleSummary
• Controls have an AccessibleName, or a label control with an AccessibleName has been programmatically associated with it
• Non-text characters are not used or have meaningful alternative text
• Text summary or alternative is provided for time-based media are not used
• CAPTCHAs are not used

The Documentation was tested for:

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

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
• Lists are contained within a List component
• Tables are contained within a Table component, implement the Accessible Table interface, provide an Accessible Summary, and contain include row and column headers where appropriate

Exceptions:

Bug 31604503 - Screen reader is reading drop down items list count incorrect. i.e. The index of drop down list item says the position index out of considering all sub menu items instead of particular submenu.

Bug 31604203 - Screen reader is incorrectly reading position of combo box menu item in set debug dialog.

Bug 31571308 - Screen reader announces 4 when the cross phase selection dialog has only 3 radio buttons.

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

The product was tested for:

• The accessibility hierarchy is logical
• The FlowsFrom and FlowsTo relations are used for multi-column text or where text flow doesn't follow the accessibility hierarchy

The Documentation was tested for:

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

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

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

The product and documentation were tested for:

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

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

The 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

The product was tested for:

• Text can be resized up to 200% without loss of content or functionality using the application's built-in resize/zoom functionality

Exception:

Bug 31540002 - Resetting zoom level in webworkspace window leads to smaller window size.

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 (Oracle logo)

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.

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

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

The product was tested for:

• The product does not have content implemented using markup languages that support editing the text style properties in this criteria

The 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 1.5 times the font size
  • Spacing following paragraphs to 2 times the font size
  • Letter spacing (tracking) to at 0.12 times the font size
  • Word spacing to 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 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)

Exceptions:

Bug 31604555 - Screen reader fails to read saying hit spacebar to open comobo box items in sort dialogs.

Bug 31594227 - Screen reader fails to read content in call history panel of call history window in web call entry application.

Bug 31593768 - screen reader fails to read content in tables present in FLISR tab of Event Details window.

Bug 31582867 - Screen reader does not read the content properly when navigated to middle pane in DMS Summary.

Bug 30071833 - User can not access several elements (devices) and SVG symbols listed on GIS based viewer map, however user can perform most of the actions on these devices using tools provided.

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

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

The documentation was tested for:

• There are no single character keyboard shortcuts.

The product was tested for:

• Time limits in the product can be turned off before they are encountered
• Before the session expires User is given a warning message and is able to extend the time limit by clicking on OK button.

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

• No portion of the screen flickers or flashes with a frequency between 2 Hz 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.
• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
• WAI-ARIA Landmark elements are used outside of repetitive navigation links

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

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

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

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

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

Exception:

Bug 31556915  - Focus is missing for pin, unpin, help, close, refresh, solution details buttons in power flow tab of device details balloon dialog in viewer.

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

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

The product and documentation were tested for:

• Properly set locale/language

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

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

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

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.

The product was tested for:

• Data is checked for input errors with an opportunity for the user to correct them.

The documentation does not allow for changes to data.

The product tested for:

• Markup languages aren't used to generate the user interface.

The documentation was tested for:

• Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique Ids

The product was tested for:

• User interface components have a programmatically associated AccessibleName and AccessibleRole as defined by the Java Accessibility API
• State information, properties, and values are programmatically exposed for user interface 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

Exception:

Bug 29321211  - Layout table could be confused for a data table by screen reader in Acronyms section of user guide.

The product and documentation were tested for:

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

The product was tested for:

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

The product was tested for:

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

The product documentation describes:

• Using NMS with a Screen Reader
• How to use the application using keyboard controls
• How to adjust the screen scaling of the application
• Choosing a high contrast color scheme

Accessibility-related documentation can be found at:  NMS User Guide, in the Accessibility Information chapter

Documentation is in electronic format.