Oracle Accessibility Conformance Report

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

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.

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.

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.

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.

The product was tested for:

• Not Applicable.  There are no identifying input fields serving a purpose identified in the Input Purposes for User Interface Components section.

The product documentation was tested for:

• Not Applicable.  Documentation contains no input fields of any kind.

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.

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.

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.

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.

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

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

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.

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.

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

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.

The product does not implement any keyboard shortcuts.

The product documentation does not implement any keyboard shortcuts.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

The product was tested for:

• Does not disrupt platform accessibility features.

The product was tested for:

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

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

The product documentation is provided in an electronic format.