Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

StorageTek Tape Analytics 2.5.x

Product Description:

Oracle's StorageTek Tape Analytics (STA) is a product which helps customers assess performance, utilization, issues, and other aspects of automated tape libraries, tape drives, media, and other tape-library-related components. It is an intelligent monitoring application available exclusively for Oracle's StorageTek Modular Tape Libraries. It simplifies tape storage management and allows you to make informed decisions about future tape storage investments based on the current health of your environment. STA allows you to monitor globally dispersed libraries from a single, browser-based user interface. You can manage open systems and mainframe mixed-media, and mixed-drive environments across multiple library platforms.

There are three user-visible interfaces covered by this ACR: The STA Installation process, The STA Utilities, and the STA Browser-based User Interface (BUI).

This ACR also covers the following product user interfaces (UIs) to the extent those UIs are seen in this product:

Oracle Weblogic Server 12c Release 12.2.1.4.0
ADF Faces Rich Client Components (output of JDeveloper), 12c Release 12.2.1.4.x

Date:

14-Sep-2023

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following:

PDF, mobi, ePub, and print versions of the product documentation
Oracle Help Center, Library Edition

Dependent Products

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

Oracle ADF Faces Rich Client Components VPAT (output of JDeveloper) (updated) 12.2.1.4.0

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/index.html

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.1	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.1 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.1 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)	Partially Supports	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 are provided Controls have an associated name There is no use of time-based media Client-side image maps specify the ALT attribute on an element. Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used The CLI was tested for: Images are not used Non-text characters are not used CAPTCHAs are not used The product documentation 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 Controls have an associated name Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used Does not include client-side image maps Does not include time-based media Exceptions: Bug 35612769 - Dashboard, Analysis, & Overview screens - Graphs/Charts: When presented by screen reader mode as tables with numeric data, multiple invalid tables are produced.
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)	Partially Supports	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. 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. The CLI was tested for: Headings follow standard text patterns for rendering headings. Lists follow standard text patterns for rendering lists. Paragraphs follow standard text patterns for rendering paragraphs. Tables follow standard text patterns for rendering tables. The product documentation was tested for: User interface component labels are associated with the fields they label. Data tables specify SUMMARY or CAPTION. Style sheets are used only to change the layout and presentation on the screen. 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. Headings are encoded with HTML heading tags. List markup is used for marking up lists. Exceptions: Bug 35636947 - All Overview screens - On tables with quick filters (top of each column), there is no feedback that quick filter has been applied. Bug 35576611 - All Analysis screens - Pivot tables converted by screen reader mode is not producing the needed pivot action icons.
1.3.2 Meaningful Sequence(Level A)	Supports	The Web UI was tested for: The sequence of elements in the DOM matches a logical reading sequence. The CLI was tested for: The correct reading sequence is discernible when output is rendered to a file. The product documentation was tested for: HTML markup and coding of text provides a correct and logical reading sequence.
1.3.3 Sensory Characteristics(Level A)	Supports	The Web UI 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. Instructions provided which refer to graphics included a reference to the text alternative of the graphic. The CLI 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 documentation was tested for: Instructions do not refer to things based solely on their sensory characteristics such as shape, size, visual location, orientation, color, or sound.
1.3.4 Orientation (Level AA)	Supports	The Web UI was tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text. The CLI was tested for: Text display orientation in a command line user interface is based on the ability of the terminal application used. The product documentation was 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)	Supports	The Web UI was tested for: There are no text fields that collect information about the user. The CLI was tested for: Markup languages aren't used to generate the user interface. The product documentation was tested for: There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)	Supports	The Web UI was tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight. The CLI was tested for: Information conveyed by color is available in text. The product documentation was tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight.
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Supports	The Web UI was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 The other text and images of text have a contrast ratio of at least 4.5:1 The CLI was tested for: Text has a contrast ratio of at least 4.5:1 The product 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.
1.4.4 Resize text(Level AA)	Supports	The Web UI was tested for: Text can be resized up to 200% without loss of content or functionality The CLI was tested for: Text can be resized up to 200% without loss of content or functionality when rendered in a GUI-based terminal application that supports text rendering sizes up to 200% larger than normal The product documentation was tested for: Text can be resized up to 200% with no loss of content or functionality.
1.4.5 Images of Text(Level AA)	Supports	The Web UI 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 CLI was tested for: Images of text are not used. The product documentation was tested for: Images of text are not used except when presentation of text is essential to the information being conveyed.
1.4.10 Reflow (Level AA)	Partially Supports	The Web UI was tested for: An alternative mobile user interface is available and is accessed from the main application. The CLI was tested for: Text information can reflow with only one direction of scrolling when rendered in a GUI-based terminal application that supports text rendering sizes up to 400% larger than normal. The product documentation was 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: Bug 31510817 - STA BUI: When zooming to 400% content is clipped and unavailable.
1.4.11 Non-text Contrast (Level AA)	Supports	The Web UI was tested for: Non-text items have a contrast ratio of at least 3:1. The CLI was tested for: Graphics are not used. Non-text characters are not used. The product documentation was tested for: Non-text items have a contrast ratio of at least 3:1.
1.4.12 Text Spacing (Level AA)	Supports	The Web UI 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 CLI was tested for: Text is not rendered using markup languages. The product 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.
1.4.13 Content on Hover or Focus (Level AA)	Supports	The Web UI 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. Information appears on hover or focus using default browser behavior, such as the title attribute of components. The CLI was tested for: There is no content that appears on hover or focus. The product documentation was tested for: There is no content that appears on hover or focus.
2.1.1 Keyboard(Level A)	Partially Supports	The Web UI 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 CLI was tested for: ability to perform functions from the keyboard only proper operation of unique keystrokes, including those listed in the product documentation The product 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. Exceptions: Bug 35693051 - Configuration: Lib Connections screen - Unable to select third or higher Library Connection Profile without using mouse. Bug 35688569 - STA BUI Popups - Arrow keys allow navigation and use of action icons outside of popup (the popup/dialog should remain the focus until dismissed). Bug 35688440 - All Analysis screens - Change Attributes popup - No way to access the help button without using mouse Bug 35688430 - All Analysis screens - Change Attributes popup - Cannot remove selected attributes using the move-left button in the popup without using a mouse Bug 35576626 - All Analysis screens - Pivot tables "totals" links (in tables) require actual mouse button to activate (no keyboard activation available). Bug 35576590 - Dashboard - Monitored Device Trends pane disables use of arrow keys in pane, no access to content (can tab out of pane).
2.1.2 No Keyboard Trap (Level A)	Supports	The Web UI was tested for: Movement of focus through a control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control. The CLI was tested for: Keyboard focus is not used. The product documentation was tested for: Movement of focus through a given 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 Web UI was tested for: There are no single character keyboard shortcuts. The CLI was tested for: There are no single character keyboard shortcuts. The product documentation was tested for: There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)	Supports	The Web UI was tested for: Time limits in the product can be adjusted to at least 10 times longer before encountered. Time limits used are part of a real-time event, or an essential activity. Time limits are longer than 20 hours. The CLI was tested for: Time limits are not used. The product documentation was tested for: Time limits are not used.
2.2.2 Pause, Stop, Hide (Level A)	Partially Supports	The Web UI was tested for: Moving, blinking, or scrolling information that is non-essential and designed to last for more than five seconds can be paused. Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden. The CLI was tested for: There is no moving, blinking or scrolling content. The product documentation was tested for: There is no moving, blinking or scrolling content. Exceptions: Bug 35631019 - Logical Groups screen - Scrolling the Defined Logical Groups table causes Assigned Entities content to change dynamically with no notification to user.
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The Web UI was tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz. The CLI was tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz. The product documentation was 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 Web UI was tested for: Structure and hierarchy is marked up with Header elements outside of repetitive navigation links. For the CLI: 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 is always automatically met. The product documentation was tested for: A "Go 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.
2.4.2 Page Titled(Level A)	Supports	The Web UI was tested for: Pages have a meaningful title specified in the TITLE element. The CLI was tested for: The name of the software application is meaningful. The product documentation was tested for: Pages have meaningful titles specified with the TITLE element.
2.4.3 Focus Order(Level A)	Partially Supports	The Web UI was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence. The CLI was tested for: Keyboard focus is not used. The product documentation was tested for: Logical movement through the focusable components can be accomplished using only the keyboard, and in an order that follows a meaningful sequence. Exceptions: Bug 35576579 - Dashboard - Tabbed widget navigation path changes dynamically. Bug 35576536 - Dashboard - Widget table cells that contain links are navigated over TWICE.
2.4.4 Link Purpose (In Context)(Level A)	Partially Supports	The Web UI was tested for: Links are meaningful from the text of the link alone, or from underlying or alternate text. The CLI was tested for: Links are not used in the CLI. The product documentation was tested for: The text of links and their surrounding paragraph, list, or table cell (with marked up table headers) are sufficient to describe their content. Exceptions: Bug 35650945 - Dashboard, Analysis, & Overview screens - Graphs/Charts: When presented by screen reader mode as table with numeric data, no access to text telling the function of a link.
2.4.5 Multiple Ways(Level AA)	Supports	The Web UI was tested for: Pages are in a site table of contents. Navigation bar for hierarchical access Quick links for instant access in a flattened, non-hierarchical form, Pages are inter-linked to each other. Access via content links on a given page to meaningful items which navigate to other pages. For the CLI: 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 is always automatically met. The product documentation was tested for: Pages can be found using the provided "Search" function. Pages are in a site table of contents. Pages are fully inter-linked to one another. Pages contain controls that enable reaching other pages.
2.4.6 Headings and Labels(Level AA)	Supports	The Web UI was tested for: Headers describe the topic or purpose of the content below them. Labels describe the purpose of the associated field. The CLI was tested for: Headers describe the topic or purpose of the content below them. Labels are not used. The product documentation was 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 Web UI was tested for: Visual indication of the location of the focus. The CLI was tested for: Keyboard focus is not used. The product documentation was tested for: Visual indication of the location of the focus.
2.5.1 Pointer Gestures (Level A)	Supports	The Web UI was tested for: There are no multipoint or path-based gesture actions. The CLI was tested for: There are no multipoint or path-based gesture actions. The product documentation was tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Supports	The Web UI was 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. The CLI was tested for: There are no single pointer operations. The product documentation was 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.
2.5.3 Label in Name (Level A)	Supports	The Web UI was tested for: Labels that contain text or images of text contain the visually presented text. The CLI has been tested for: User interface components are not used. The product documentation was tested for: Labels that contain text or images of text contain the visually presented text.
2.5.4 Motion Actuation (Level A)	Supports	The Web UI was tested for: There are no functions that require motion of the device. The CLI was tested for: There are no functions that require motion of the device. The product documentation was tested for: There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)	Supports	The Web UI was tested for: Properly set lang attribute for each page. The CLI was tested for: This application only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable. The product documentation was tested for: Properly set lang attribute for each page.
3.1.2 Language of Parts(Level AA)	Supports	The Web UI was tested for: There are no passages or phrases that differ from the language of the page. The CLI was tested for: This application only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable. The product documentation was tested for: Proper use of the 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 Web UI 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 CLI was tested for: Keyboard focus is not used. The product 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.
3.2.2 On Input(Level A)	Supports	The Web UI was tested for: Changes in the value of user interface components do not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window. The CLI was tested for: User interface components are not used. The product documentation was tested for: Changes in the value of user interface components do 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.3 Consistent Navigation(Level AA)	Supports	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. For the CLI: 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 is always automatically met. The product 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.
3.2.4 Consistent Identification(Level AA)	Supports	The Web UI was tested for: Images and controls are used and identified consistently throughout the documentation. The CLI was tested for: Images and controls are not used. The product documentation was tested for: Images and controls are used and identified consistently throughout the documentation.
3.3.1 Error Identification(Level A)	Supports	The Web UI 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 CLI 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 documentation was tested for: The documentation does not have input fields, except for the Search field.
3.3.2 Labels or Instructions (Level A)	Supports	The Web UI was tested for: Labels or instructions are provided when the product requires user input. The CLI was tested for: Labels or instructions are provided when the product requires user input. The product documentation was tested for: The documentation does not require user input.
3.3.3 Error Suggestion (Level AA)	Supports	The Web UI was tested for: Where suggestions for fixing an input error are known, they are provided to the user. The CLI was tested for: Where suggestions for fixing an input error are known, they are provided to the user. The product documentation was tested for: The documentation does not require user input.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The Web UI was tested for: 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 CLI was tested for: 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 product documentation was tested for: The documentation does not require user input that modifies user controllable data.
4.1.1 Parsing(Level A)	Supports	The Web UI was tested for: Pages validate to the HTML specification. The CLI was tested for: Markup languages aren't used to generate the user interface. The product 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. Pages validate to the HTML specification.
4.1.2 Name, Role, Value (Level A)	Partially Supports	The Web UI was tested for:: Components have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc. Custom controls have a meaningful programmatically exposed name. Additional state information is programmatically exposed, such as whether a field is required or changed. The CLI was tested for: User interface components are not used. The product 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 35693760 - Setup&Admin - Media Validation screen - Add /Edit media validation policy wizard - Does not read review values when using screen reader. Bug 35637155 - Setup&Admin - Library Connections screen - Add Library Connection wizard - Values not reported/read when using screen reader.
4.1.3 Status Messages (Level AA)	Partially Supports	The CLI was tested for: Markup languages aren't used to generate the user interface. The product documentation was tested for: There are no status messages. Exceptions: Bug 31510987 - The Web UI does not provide programmatically determinable status messages.

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 Web UI was tested for: Does not disrupt platform accessibility features. The CLI was tested for: Does not disrupt platform accessibility features.
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 Web UI was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor. The CLI 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	Product documentation was tested for: Describes special keystrokes needed to operate controls. Describes workarounds. Describes how to use the hardware and software accessibility features that are part of the product and that provide compatibility with assistive technology. Accessibility related documentation can be found within the product documentation. Documentation for user accessibility options is provided in the" StorageTek Tape Analytics Screen Basics Guide." (STA Version 2.3) Note: For Post 2.3 versions, this information is provided in the STA User's Guide, Chapter 2, "Users and Preferences".
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	The product documentation is provided in an 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 applicableStandards/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.