Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

StorageTek Tape Analytics 2.3.1

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 VPAT: The STA Installation process, The STA Utilities, and the STA Browser-based User Interface (BUI). This VPAT also covers the following product user interfaces (UIs) to the extent those UIs are seen in this product:
  • Oracle Weblogic Server 11g Release 1 10.3.6
  • ADF Faces Rich Client Components (output of JDeveloper), 11g R1 PS5 11.1.1.6

 

Date:

25-Jun-2020

Archive Note:

This VPAT applies to only version 2.3.1. It does not apply to any versions of StorageTek Tape Analytics after this. This VPAT has been superseded by StorageTek Tape Analytics 2.5.x.

Contact Information:

accessible_ww@oracle.com

Notes:

For product documentation:

  • PDF, mobi, ePub, and print versions of the product documentation are excluded from the VPAT.
  • Oracle Help Center, Library Edition is excluded from the VPAT

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.

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/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

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 product conforms to the following:

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

  • Bug 28158070 - ALT= Text is Non-specific in Some Non-text Images in Customer Facing Docs
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe product has no multimedia.
1.3.1 Info and Relationships (Level A)Supports

The product was tested for:

  • Hierarchical text structures available via screen reader and similar accessibility tools.

Because the product makes significant use of tables, the following structure/information details were also specifically tested :

  • Table usage – only data tables, as opposed to layout tables, use table elements of TH and CAPTION and table attributes of SUMMARY, SCOPE, and HEADERS.
  • A column of a data table is marked up with TH and SCOPE=”COL”
  • A row of a data table has at least one column marked as the row header with SCOPE=”ROW”
  • Summaries, row headers, and column headers are defined and used.
  • For pivot tables, controls are provided allowing the pivoting and changing of position and relationship of the row and column headers (pivoting).  These controls have meaningful associated text accessible by tabbing and other accessibility access methods (dependent on the technology used).

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.
1.3.2 Meaningful Sequence(Level A)Supports

The product was tested for:

  • Objects in sequence are organized using structures (e.g. tables, IDs, etc) from which their relationships may be determined.

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

  • The product does not restrict the user to a specific display orientation.

The product documentation was tested for:

  • The product documentation does not restrict a user to a specific display orientation.
1.3.5 Identify Input Purpose (Level AA)Not Applicable

The product was tested for:

The product documentation was tested for:

  • Not Applicable.  Documentation contains no input fields of any kind.
1.4.1 Use of Color(Level A)Supports

The product was tested for:

  • Alternative means used for conveying color-related information. 
  • Color coded information is presented in conjunction with either text or symbols which convey the meaning independently from the color used.

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 ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports

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

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

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

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

  • A Dashboard-Only rendition of the product GUI is presented on devices with pixel dimensions of 320x256 (e.g. limited size cellphones) via responsive web pages.
  • At those pixel dimensions, the functionality offered requires no horizontal scrolling (just vertical scrolling).

The product documentation was tested for:

  • Fully supports 320x256 pixels without loss of information, and meets the two-dimensional scrolling criteria.

Exceptions:

  • Bug 31510817 - Provide full-functionality at 320x256 pixels in support of WCAG 1.4.10 Reflow
1.4.11 Non-text Contrast (Level AA)Supports

The product was tested for:

  • User Interface components and states have a contrast ratio of at least 3:1
  • Graphical objects have a contrast ratio of at least 3:1,except when particular presentation prevents this.
  • Access to the graphical data and relationships in equivalent tabular form with no loss of information is provided natively in the product (no assistive technology required).

The product documentation was tested for:

  • Graphical objects have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)Supports

This product was tested for:

  • No loss of content or functionality occurs by setting the line height, spacing, letter spacing, or word spacing properties as detailed in the conformance criteria.

The product documentation was tested for:

  • No loss of content or functionality occurs by setting the line height, spacing, letter spacing, or word spacing properties as detailed in the conformance criteria.
1.4.13 Content on Hover or Focus (Level AA)Supports

The product was tested for:

  • Additional, product-controlled content does not obscure or replace other content.
  • The additional content is both hoverable and persistent, except for when the hover or focus is removed or the information is no longer valid.
  • Tooltips and other user agent controlled content may appear for a limited time controlled by that agent.

The product documentation was tested for:

  • There is no document-controlled additional content.
2.1.1 Keyboard(Level A)Partially Supports

The product was tested for:

  • Tab order through the product controls and selectable elements
  • Use of keyboard to perform selection and actions, without requiring specific timing

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 15750394 - ADF: When in Screen Reader Mode Browser Functions Intermittently
2.1.2 No Keyboard Trap (Level A)Supports

The product 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 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)Not Applicable

The product does not implement any keyboard shortcuts.

The product documentation does not implement any keyboard shortcuts.

2.2.1 Timing Adjustable(Level A)Supports

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

  • Time limits are not used.
2.2.2 Pause, Stop, Hide (Level A)Supports

The product contains the following instances of animation:

  • Status indicator - The status indicator supports alternate text to indicate the state as busy or idle.  It remains in motion as long as the state is busy (which can exceed three seconds).
  • Loading indicator - The loading indicator is a decorative animation image that also has text explaining that the application is loading. It remains in motion as long as the browser is loading a screen.
  • Progress bars - Used to indicate degree of completion of user activity.  Bar grows in accord with amount completed.
  • Other decorative animation effects, such as those presented through Adobe Flash, can be prevented when using "screen reader" mode.

The product documentation was tested for:

  • There is no moving, blinking or scrolling content.
2.3.1 Three Flashes or Below Threshold(Level A)Supports

The product 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 2Hz and 55Hz.
  • No component of the content flashes or flickers for more than three times in any one-second period.
2.4.1 Bypass Blocks(Level A)Supports

The product was tested for:

  • When in screen reader mode, the application contains a "skip to main content" navigation link.
  • Header markup is not used for formatting effects (such as font size), but rather for hierarchical purposes on the screens.
  • Some screen content areas do not contain sufficient headers to allow efficient hierarchical navigation.  User may use serial navigation (less efficient) in these cases.

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

  • Meaningful titles for Pages are provided.

The product documentation was tested for:

  • Pages have meaningful titles specified with the TITLE element.
2.4.3 Focus Order(Level A)Supports

The product was tested for:

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

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.
2.4.4 Link Purpose (In Context)(Level A)Supports

The product was tested for:

  • Links are meaningful from the text of the link alone, or from underlying or alternate text.

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.
2.4.5 Multiple Ways(Level AA)Supports

The product was tested for:

  • Navigation bar for hierarchical access
  • Quick links for instant access in a flattened, non-hierarchical form, and
  • Access via content links on a given page to meaningful items which navigate to other pages.

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

  • Headings and labels are meaningful and descriptive of the page or sub-context which they precede.

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

  • Visual cue or feedback to the position of the cursor within the product
  • Cursor focus is programmatically exposed

The product documentation was tested for:

  • Visual indication of the location of the focus.
2.5.1 Pointer Gestures (Level A)Not Applicable

The product does not implement or use any multipoint or path-based gestures.

The product documentation does not implement or use any multipoint or path-based gestures.

2.5.2 Pointer Cancellation (Level A)Supports

The product was tested for:

  • The down-event of the pointer is not used to execute any part of the function, and
  • Completion of the function is on the up-event, and a mechanism is available to abort the function before completion (relocation of focus).

The product documentation was tested for:

  • The down-event of the pointer is not used to execute any part of the function, and
  • Completion of the function is on the up-event, and a mechanism is available to abort the function before completion (relocation of focus).
2.5.3 Label in Name (Level A)Supports

The product was tested for:

  • Labels that contain text or images of text contain the visually presented text.
  • In the case of graphs and their text and text images, screen reader mode will produce and allow access to the corresponding text.

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)Not Applicable

The product does not implement any device motion or user motion functionality.

The product documentation does not implement any device motion or user motion functionality.

3.1.1 Language of Page(Level A)Supports

The product was tested for:

  • The "lang" attribute is properly set for a given HTML page, and
  • The human language conforms to that set for the platform (OS) or the host system (programmatically determinable from that system).

The product documentation was tested for:

  • Properly set "lang" attribute for a given page.
3.1.2 Language of Parts(Level AA)Supports

The product was tested for:

  • No passages or phrases that differ in language from the page/screen as a whole, and
  • The "lang" attribute is correctly set for a given screen, and
  • The human language used will be that selected for the platform (OS) on which the product runs (programmatically determinable from that system).

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

  • No use of user interface components for which a change in setting results in change of context.

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

  • Ordering of navigational elements remains constant unless a change is initiated by the user.

The product documentation was tested for:

  • Pages that are grouped together into sets with a common navigation mechanism use that mechanism in the same manner, with navigation elements appearing in the same relative order as expected.
3.2.4 Consistent Identification(Level AA)Supports

The product was tested for:

  • Components maintain the same meaning and functionality across the product.

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

  • Wherever possible, the product prevents the user from inputting invalid values.
  • When that is not possible (e.g., a value may be valid or invalid, varying based on other factors), the input error is presented and described in textual form.

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

  • The error text will typically inform the user of the root cause of the error, allowing them to submit input which does not suffer from that same cause.

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

  • No legal, financial, or user-data commitments, modifications, or deletions are made by this product.  No user test responses are submitted by this product.

The product documentation was tested for:

  • There are no legal commitments or financial transactions required to view the product documentation.
4.1.1 Parsing(Level A)Supports

The product was tested for:

  • Pages validate to the HTML specification

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

The product was tested for::

  • Components 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, such as whether a field is required or changed.

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.
4.1.3 Status Messages (Level AA)Not Supported

The product was tested for:

  • Programatically determinable status messages: The product does not provide this currently.  The current user interface framework base (Oracle ADF) does not provide this mechanism.

The product documentation was tested for:

  • Not Applicable.  There are no status messages of any kind presented to the user.

Exceptions:

  • Bug 31510987 - For WCAG 4.1.3, provide programmatically determinable status messages without receiving focus

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

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 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesSupports

The product was tested for:

  • Does not disrupt platform accessibility features.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesSupports

The product was tested for:

  • Responds to platform settings for color, contrast, font type, font size, and focus cursor
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

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

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

The product documentation is provided in an electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle 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.

back to top

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.