VPAT - Oracle Utilities Network Management System (NMS) 2.6.0.2

Notes:

Dependent Products

This product interacts with or is built with the other Oracle products listed in this section. Click below to view information about the accessibility of these dependent products. Products listed are the versions available at the time of publication of this document; newer documents may be available that supersede these versions.

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/Guideline	Included In Report
Web Content Accessibility Guidelines 2.0	Level A - Yes Level AA - Yes Level AAA - No
Web Content Accessibility Guidelines 2.1	Level A - Yes Level AA - Yes Level AAA - No
Web Content Accessibility Guidelines 2.2	Level A - Yes Level AA - Yes Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018	Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports: The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Partially Supports: Some functionality of the product does not meet the criteria.
Does Not Support: Majority of functionality of the product does not meet the criteria.
Not Applicable: The criteria are not relevant to the product.

WCAG 2.2 Report

Table 1 also documents conformance with:

Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports	The Java Swing UI 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 Web UI was 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. Controls have an associated name. Text summary or alternative is provided for time-based media. Client-side image maps specify the ALT attribute on each AREA element. Non-text characters are not used or have meaningful alternative text. CAPTCHAs are not used.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.4 Captions (Live) (Level AA)	Not Applicable	The product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	The product has no multimedia.
1.3.1 Info and Relationships (Level A)	Supports	The Java Swing UI 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 Web UI 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. Data tables specify SUMMARY or CAPTION.
1.3.2 Meaningful Sequence (Level A)	Supports	The Java Swing UI 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 Web UI was tested for: The sequence of elements in the DOM matches a logical reading sequence.
1.3.3 Sensory Characteristics (Level A)	Supports	The Java Swing UI and the Web UI 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.
1.3.4 Orientation (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)	Not Applicable	The Java Swing UI and the Web UI were tested for: There are no text fields that collect information about the user.
1.4.1 Use of Color (Level A)	Supports	The Java Swing UI and the Web UI 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.
1.4.2 Audio Control (Level A)	Not Applicable	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Supports	The Java Swing UI and the Web UI 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
1.4.4 Resize text (Level AA)	Partially Supports	The Java Swing UI and the Web UI were 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 38334354 - In 'Tools' Menu, 'Actions' Menu Of Web Workspace And Work Agenda Windows, 'Demo / Test', 'Create Follow-Up Event' Menu Options Are Not Fully Visible At 200% Zoom Level.
1.4.5 Images of Text (Level AA)	Supports	The Java Swing UI and the Web UI were 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)
1.4.10 Reflow (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom.
1.4.11 Non-text Contrast (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: Non-text items have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)	Supports	The Java Swing UI was tested for: The product does not have content implemented using markup languages that support editing the text style properties in this criteria. The Web UI 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.
1.4.13 Content on Hover or Focus (Level AA)	Supports	The Java Swing UI and the Web UI 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.
2.1.1 Keyboard (Level A)	Partially Supports	The Java Swing UI and the Web UI 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 ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms Exceptions: Bug 35093566 - Cannot Toggle On/Off the Filter in FEP Monitor and IED Monitor in the SCADA Status Screen With Spacebar Key While Using Keyboard Navigation.
2.1.2 No Keyboard Trap (Level A)	Supports	The Java Swing UI and the Web UI 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
2.1.4 Character Key Shortcuts (Level A)	Supports	The Java Swing UI and the Web UI were tested for: Single character keyboard shortcuts are only active when that component has focus.
2.2.1 Timing Adjustable (Level A)	Supports	The Java Swing UI and the Web UI were 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.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The Java Swing UI and the Web UI were tested for: There is no moving, blinking, scrolling or auto-updating content
2.3.1 Three Flashes or Below Threshold (Level A)	Supports	The Java Swing UI and the Web UI were tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
2.4.1 Bypass Blocks (Level A)	Supports	The Java Swing UI 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 Web UI 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.
2.4.2 Page Titled (Level A)	Supports	The Java Swing UI was tested for: The name of the software application is meaningful. The Web UI was tested for: Pages have a meaningful title specified in the TITLE element.
2.4.3 Focus Order (Level A)	Supports	The Java Swing UI and the Web UI were tested for: Logical movement through the focusable component using only the keyboard in an order that follows a meaningful sequence.
2.4.4 Link Purpose (In Context) (Level A)	Supports	The Java Swing UI and the Web UI 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.
2.4.5 Multiple Ways (Level AA)	Supports	The Java Swing UI 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 Web UI was tested for: Pages are fully inter-linked to each other. Page contains controls that enable reaching all pages.
2.4.6 Headings and Labels (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field
2.4.7 Focus Visible (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: Visual indication of the location of the focus
2.4.11 Focus Not Obscured (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.
2.5.1 Pointer Gestures (Level A)	Not Applicable	The Java Swing UI and the Web UI were tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Not Applicable	The Java Swing UI and the Web UI were tested for: There are no single pointer operations
2.5.3 Label in Name (Level A)	Supports	The Java Swing UI and the Web UI 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.
2.5.4 Motion Actuation (Level A)	Not Applicable	The Java Swing UI and the Web UI were tested for: There are no functions that require motion of the device.
2.5.7 Dragging Movements (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.
2.5.8 Target Size (Minimum) (Level AA)	Partially Supports	The Java Swing UI was tested for: The Java Swing UI has not yet been evaluated for this criterion. The Web UI was 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.
3.1.1 Language of Page (Level A)	Supports	The Java Swing UI was tested for: Properly set locale/language The Web UI was tested for: Properly set lang attribute for each page.
3.1.2 Language of Parts (Level AA)	Supports	The Java Swing UI was tested for: Properly set locale/language for text passages that are in a different language than that of the software The Web UI was tested for: Proper use of lang attribute for text passages that are in a different language than that of the page.
3.2.1 On Focus (Level A)	Supports	The Java Swing UI and the Web UI 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.
3.2.2 On Input (Level A)	Supports	The Java Swing UI and the Web UI were 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.
3.2.3 Consistent Navigation (Level AA)	Supports	The Java Swing UI 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 Web UI 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.
3.2.4 Consistent Identification (Level AA)	Supports	The Web UI was tested for: Images and controls are used and identified consistently throughout the product.
3.2.6 Consistent Help (Level A)	Supports	The Java Swing UI and the Web UI were tested for: Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.
3.3.1 Error Identification (Level A)	Supports	The Java Swing UI and the Web UI were tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred.
3.3.2 Labels or Instructions (Level A)	Supports	The Java Swing UI and the Web UI were tested for: Labels or instructions are provided when the product requires user input.
3.3.3 Error Suggestion (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: Where suggestions for fixing an input error are known, they are provided to the user.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: Data is checked for input errors with an opportunity for the user to correct them.
3.3.7 Redundant Entry (Level A)	Not Applicable	The Java Swing UI and the Web UI were tested for: There are no occurrences of information that the user needs to enter which has been previously entered.
3.3.8 Accessible Authentication (Minimum) (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: Support for password entry by browsers or password managers to address the memorization cognitive function test Support for copy and paste to help address the transcription cognitive function test.
4.1.1 Parsing (Level A)	Not Applicable	This criterion is considered as always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)	Supports	The Java Swing UI 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 Event notification of changes to names, states, properties, and values is available to assistive technologies The Web UI 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’. Frames have a meaningful title specified in the title attribute.
4.1.3 Status Messages (Level AA)	Supports	The Java Swing UI and the Web UI were tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of Color	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without Speech	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited Manipulation	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and Strength	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria	Conformance Level	Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive Technology	Heading cell - no response required	Heading cell - no response required
502.2.1 User Control of Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility Features	Supports	The Java Swing UI was tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and Headers	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.4 Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.6 Label Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.8 Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.10 List of Actions	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on Objects	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.14 Event Notification	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Supports	The Java Swing UI was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor
503.3 Alternative User Interfaces	Not Applicable	The product does not have assistive technology features.
503.4 User Controls for Captions and Audio Description	Heading cell - no response required	Heading cell - no response required
503.4.1 Caption Controls	Not Applicable	The product has no multimedia.
503.4.2 Audio Description Controls	Not Applicable	The product has no multimedia.
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
602 Support Documentation	Heading cell - no response required	Heading cell - no response required
602.2 Accessibility and Compatibility Features	Supports	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
602.3 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support Documentation	Not Applicable	Documentation is in electronic format.
603 Support Services	Heading cell - no response required	Heading cell - no response required
603.2 Information on Accessibility and Compatibility Features	Supports	Oracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication Needs	Supports	Oracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicable Standards/Guidelines, subject to Oracle's interpretation of those standards (available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.

Oracle Accessibility Conformance Report

Name of Product:

Product Description:

Report Date:

Contact Information: