Criteria
Conformance Level
Remarks and Explanations
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
-
Exceptions:
Below are the open product bugs on Oracle Utilities Network Management System (NMS) product for this guideline
Bug 29290151 - Tables do not have an accessible summary. NMS tables do not lend themselves to an Accessible Summary. Its purpose is for complicated tables that need an extra explanation to use or for crosstab type files where the actual values might not be obvious.
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
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
Exceptions:
Bug 29900394 - Screen Reader reports wrong number of radio buttons when buttons are hidden. This is due to a Java bug 29920469
Bug 29837139 - Screen Reader fails to read JTextFields correctly within Accessible Selection. This is due to a Java bug 29903117
Bug 29861574 - Screen reader is not announcing editable fields in tables where fields in tables do not have any visual cue to show which columns are editable. Hitting on space bar only brings up visual indication of editable field for that cell.
The Application 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 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 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
Exceptions:
Bug 29314785 - User guide titles / headers has insufficient color contrast 2.84
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
Exceptions:
Bug 30031077 - Part of text and two button are not visible at 200% zoom level in transfer log window of web workspace
Bug 30030678 - All text is not visible in device details balloon dialog at 200% zoom level
Bug 29931260 - All text boxes are not visible at 200% zoom level in middle pane DMS (Distribution Management System) summary
Bug 29859894 - Graph and text are not zoomed up to 200% in state transition tab of configuration assistant. Also scroll bars are missing at 200% zoom level for mobile user administration tab.
Bug 29846964 - In call history dialog, call history table section is not visible at 200% zoom level. User can only see it by expanding call history dialog.
Bug 29836687 - Part of UI (User Interface) content is not visible in 'perform next call backs', 'perform call backs' dialogs in web call backs application at 200% zoom level. User can only view it by expanding the dialog.
Bug 29833168 - In 'Parameters' tab of 'Service Alerts', parameter information section content goes out of scope of visibility at 200% zoom level.
Bug 30030652 - Dialogs like 'Authority', 'Subscribe' etc.. opened from web workspace application are not returning to its original size with zoom out action (ctrl + 0) after zooming in. However text is coming back to its original size. User needs to resize these windows manually to bring back to its original 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:
- 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 29900473 - Trouble summary trend graph and SCADA (Supervisory Control and Data Acquisition) trend graph are not accessible. These graphs are not accessible because of java deficiency https://bugs.openjdk.java.net/browse/JDK-8177382
Bug 29283473 - Tool tips are not displaying for menu options when user navigates through key board keys like arrows. This is due to a java bug 29884396 - ctrl-F1 does not show the tool tip of a menu item (JMenuItems)
Bug 29861732 - ActionListeners on JRadioButtons don't get notified when selection is changed with arrow keys. This is due to java bug 29966143
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:
- 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 was tested for:
- There is no moving, blinking or scrolling content
The documentation was tested for:
- There is no moving, blinking or scrolling 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:
- Blocks of content are not repeated.
Oracle non-Web software products, including bundles and suites of software, do not behave as aset of software programsas 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 was tested for:
- Logical movement through the focusable component using only the keyboard in an order that follows a meaningful sequence.
Exceptions:
Bug 29283962 - Initial focus indicator is not showing up on new windows opened, however user can see this focus by clicking tab button. Focus works fine, if user hits tab button after opening any new window.
Bug 30071833 - User can not access all 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. user also can not switch between viewer and couple of tools - commissioning tool and assessment tool.
The documentation was 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.
Exception: Bug 30066305 - Hyperlink text not read by screen reader in multi line text format in power flow solution details dialog. This is due to a Java bug https://bugs.openjdk.java.net/browse/JDK-6193818
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 aset of software programsas 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 29283962 - Initial focus indicator is not showing up on new windows opened, however user can see this focus by clicking tab button. Focus works fine, if user hits tab button after opening any new window.
The product and documentation was tested for:
- Properly set locale/language
Exception: Bug 29315383 - No lang attribute found on HTML element in user guide.
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 circ*mstances 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 aset of software programsas 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 was tested for:
- Images and controls are used and identified consistently throughout the product.
The product and documentation 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 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 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 and documentation was tested for:
- Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique Ids
Exception: Bug 29294635 - Access Bridge returning html instead of text. This is due to a Java bug 29954696 .
The Application 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
Exceptions:
Bug 29315679 - Discernible text missing for some links in user guide
Bug 29321211 - Layout table could be confused for a data table by screen reader in user guide
