Oracle Accessibility Conformance Report

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
• CAPTCHAs are not used

The Essbase Server and CLI was tested for:

• Images are not used
• Non-text characters are not used
• CAPTCHAs are not used

The 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
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
• Controls have an associated name
• CAPTCHAs are not used

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
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate

The Essbase Server and CLI was tested for:

• Headings follow standard text patterns for rendering headings
• Tables follow standard text patterns for rendering tables
• Paragraphs follow standard text patterns for rendering paragraphs

The Documentation 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.
• Style sheets are used only to change the layout and presentation on the screen.

The Web UI was tested for:

• The sequence of elements in the DOM matches a logical reading sequence

The Essbase Server and CLI was tested for:

• The correct reading sequence is discernible when output is rendered to a file

The Documentation was tested for:

• The sequence of elements in the DOM matches a logical reading sequence

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 Essbase Server and 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 Documentation was tested for:

• Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The Web UI was tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.

The Essbase Server and CLI was tested for:

• Text display orientation in a command line user interface is based on the ability of the terminal application used.

The Documentation was tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.

The Web UI was tested for:

• There are no text fields that collect information about the user

The Essbase Server and CLI was tested for:

• There are no text fields that collect information about the user

The Documentation was tested for:

• There are no text fields that collect information about the user

The Web UI was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight
• Information conveyed by color has a contrast ratio of at least 3:1

The Essbase Server and CLI was tested for:

• Information conveyed by color is available in text

The Documentation was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight
• Information conveyed by color has a contrast ratio of at least 3:1

The Web UI 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 Essbase Server and CLI was tested for:

• Text has a contrast ratio of at least 4.5:1

The Documentation was tested for:

• Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
• Other text and images of text have a contrast ratio of at least 4.5:1

The Web UI was tested for:

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

The Essbase Server and 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 Documentation was tested for:

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

The Web UI was tested for:

• Images of text are not used

The Essbase Server and CLI was tested for:

• Images of text are not used

The Documentation was tested for:

• Images of text are only used when the technology can't create the desired visual presentation, the particular image is essential.

The Web UI was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.

Exceptions for the Web UI:

• Bug 36941825: Not all columns are visible while at 400% zoom on the Applications page when in List View mode. Workaround is to use Card View mode.

The Essbase Server and 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 Documentation was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

 The Web UI was tested for:

• Non-text items have a contrast ratio of at least 3:1

The Essbase Server and CLI was tested for:

• Graphics are not used
• Non-text characters are not used

The Documentation was tested for:

• Non-text items have a contrast ratio of at least 3:1

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 1.5 times the font size
  • Spacing following paragraphs to 2 times the font size
  • Letter spacing (tracking) to at 0.12 times the font size
  • Word spacing to 0.16 times the font size

The Essbase Server and CLI was tested for:

• Text is not rendered using using markup languages.

The 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 1.5 times the font size
  • Spacing following paragraphs to 2 times the font size
  • Letter spacing (tracking) to at 0.12 times the font size
  • Word spacing to 0.16 times the font size

The Web UI was tested for:

• Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing.

The Essbase Server and CLI was tested for:

• There is no content that appears on hover or focus.

The Documentation was tested for:

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

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

Exceptions for the Web UI:

• Bug 36925257: When navigating the script editors using keyboard shortcuts, you cannot exit out of them with tab key. Workaround: Use the Escape key to exit the script editors.
• Bug 36896407: A user cannot see the keyboard tab control if it is in the Main Menu WebLogic and on the left hand side menu due of the background color.

The Essbase Server and CLI was tested for:

• The CLI is explicitly designed to be used entirely through a keyboard interface.

The Documentation was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation

The Web UI was tested for:

• Movement of focus through control using only the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

The Essbase Server and CLI was tested for:

• Keyboard focus is not used

The Documentation was tested for:

• Movement of focus through control using only the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

The Web UI was tested for:

• There are no single character keyboard shortcuts.

The Essbase Server and CLI was tested for:

• There are no single character keyboard shortcuts.

The Documentation was tested for:

• Single character keyboard shortcuts are only active when that component has focus.

The Web UI was tested for:

• Time limits used are part of a real-time event, or an essential activity.

The Essbase Server and CLI was tested for:

• Time limits used are part of a real-time event, or an essential activity.

The Documentation was tested for:

• Time limits are not used.

The Web UI was tested for:

• There is no moving, blinking or scrolling content

The Essbase Server and CLI was tested for:

• There is no moving, blinking or scrolling content

The Documentation was tested for:

• There is no moving, blinking or scrolling content

The Web UI was tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

The Essbase Server and CLI was tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

The Documentation was tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

The Web UI was tested for:

• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links.

The Essbase Server and CLI 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 is always automatically met.

The Documentation was tested for:

• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links.

The Web UI was tested for:

• Pages have a meaningful title specified in the TITLE element

The Essbase Server and CLI was tested for:

• The name of the software application is meaningful.

The Documentation was tested for:

• Pages have a meaningful title specified in the TITLE element

The Web UI was tested for:

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

The Essbase Server and CLI was tested for:

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

The Documentation was tested for:

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

The Web UI was tested for:

• The text of links and their surrounding paragraph, list, or table cell (with marked up table headers), is sufficient to describe their purpose

The Essbase Server and CLI was tested for:

• Links are not used in the product

The Documentation was tested for:

• The text of links and their surrounding paragraph, list, or table cell (with marked up table headers), is sufficient to describe their purpose

The Web UI was tested for:

• Pages are fully inter-linked to each other
• Page contains controls that enable reaching all pages

The Essbase Server and CLI 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 is automatically met.

The Documentation was tested for:

• Pages can be found using the provided "search" function
• Pages are in a site table of contents
• Page contains controls that enable reaching all pages

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 Essbase Server and CLI was tested for:

• Headers describe the topic or purpose of the content below them

The Documentation was tested for:

• Headers describe the topic or purpose of the content below them
• Labels describe the purpose of the associated field

The Web UI was tested for:

• Visual indication of the location of the focus

The Essbase Server and CLI was tested for:

• Keyboard focus is not used

The Documentation was tested for:

• Visual indication of the location of the focus

The Web UI was tested for:

• The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

The Essbase Server and CLI was tested for:

• Keyboard focus is not used

The Documentation was tested for:

• The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

The Web UI was tested for:

• There are no multipoint or path-based gesture actions.

The Essbase Server and CLI was tested for:

• There are no multipoint or path-based gesture actions.

The Documentation was tested for:

• There are no multipoint or path-based gesture actions.

The Web UI was tested for:

• 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 Essbase Server and CLI was tested for:

• There are no single pointer operations

The Documentation was tested for:

• There are no single pointer operations.

The Web UI was 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.

The Essbase Server and CLI was tested for:

• There are no user interface components labeled with text or images of text.

The Documentation was 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.

The Web UI was tested for:

• There are no functions that require motion of the device.

The Essbase Server and CLI was tested for:

• There are no functions that require motion of the device.

The Documentation was tested for:

• There are no functions that require motion of the device.

The Web UI was tested for:

• All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.
• The functionality of dragging movements are determined by the user agent and not modified by the author.

The Essbase Server and CLI was tested for:

• There is no functionality that uses dragging movements.

The Documentation was tested for:

• There is no functionality that uses dragging movements.

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.

• The function can be achieved through a different control in the same software that meets this criterion.

• The target is in a sentence or its size is otherwise constrained by the line-height of non-target text.

• A particular presentation of the target is essential or is legally required for the information being conveyed.

The Essbase Server and CLI was tested for:

• The product does not contain interactive targets.

The Documentation 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.

• The function can be achieved through a different control in the same software that meets this criterion.

The Web UI was tested for:

• Properly set lang attribute for each page

This guideline is Not Applicable for the Essbase Server and CLI:

• This CLI only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable.

The Documentation was tested for:

• Properly set lang attribute for each page

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.

This guideline is Not Applicable for the Essbase Server and CLI:

• This CLI only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable.

The Documentation was tested for:

• Proper use of lang attribute for text passages that are in a different language than that of the page.

The 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

Exceptions for the Web UI:

• Bug 36946762: On the Create applications page under Actions, the focus is not returned during a Rename or Delete.
• Bug 37479617: When a screen reader is turned on, and if an event triggers a banner message then the screen reader will reading the content of it twice and the close button thrice.  This issue depends on a fix on JavaScript Extension Toolkit (JET-58204).
• Bug 36896407: A user cannot see the keyboard tab control if it is in the Main Menu WebLogic and on the left hand side menu due of the background color.

The Essbase Server and CLI was tested for:

• Keyboard focus is not used

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

• Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window

The  Essbase Server and CLI was tested for:

• User interface components are not used

The Documentation was tested for:

• Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window

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.

The Essbase Server and CLI 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 is automatically met.

The Documentation was tested for:

• Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order.

The Web UI was tested for:

• Images and controls are used and identified consistently throughout the product

The  Essbase Server and CLI was tested for:

• Images and controls are not used

The Documentation was tested for:

• Images and controls are used and identified consistently throughout the product

The Web UI was tested for:

• Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.

The  Essbase Server and CLI 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 is always automatically met.

The Documentation was tested for:

• Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.

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 Essbase Server and 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 Documentation was tested for:

• The documentation does not allow for input or changes to data.

The Web UI was tested for:

• Labels or instructions are provided when the product requires user input

The Essbase Server and CLI was tested for:

• Labels or instructions are provided when the product requires user input

The Documentation was tested for:

• Labels or instructions are provided when the product requires user input

The Web UI was tested for:

• Where suggestions for fixing an input error are known, they are provided to the user

The Essbase Server and CLI was tested for:

• Where suggestions for fixing an input error are known, they are provided to the user

The Documentation was tested for:

• The documentation does not detect input errors and does not allow for input or changes to data.

The Web UI was tested for:

• Data is checked for input errors with an opportunity for the user to correct them

The Essbase Server and CLI was tested for:

• Data is checked for input errors with an opportunity for the user to correct them

The Documentation was tested for:

• The documentation does not detect input errors and does not allow for input or changes to data.

The Web UI was tested for:

• Information previously entered by or provided to the user that is required to be entered again in the same process is auto-populated by the application.
• Information previously entered by or provided to the user that is required to be entered again in the same process is available for the user to select.
• Re-entering information previously entered by or provided to the user is essential.
• Re-entering information previously entered by or provided to the user is required to ensure the security of content.
• Previously entered information is not valid at the time that the user is asked re-enter the information.
• There are no occurrences of information that the user needs to enter which has been previously entered.

The Essbase Server and CLI was tested for:

• There are no occurrences of information that the user needs to enter which has been previously entered.

The Documentation was tested for:

• This criteria is not applicable.

The Web UI was tested for:

• The product supports password entry by password managers.
• The product supports copy and paste while authenticating.

The Essbase Server and CLI was tested for:

• The product supports password entry by password managers.
• The product supports copy and paste while authenticating.

The Documentation was tested for:

• This criteria is not applicable.

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

Exceptions for the Web UI:

• Bug 37479617: When a screen reader is turned on, and if an event triggers a banner message then the screen reader will reading the content of it twice and the close button thrice.  This issue depends on a fix on JavaScript Extension Toolkit (JET-58204).

The Essbase Server and CLI was tested for:

• User interface components are not used

The Documentation was tested for:

• Frames have a meaningful title specified in the title attribute

The Web UI was tested for:

• There are no status messages.

The Essbase Server and CLI was tested for:

• There are no status messages.

The Documentation was tested for:

• There are no status messages.

The Web UI was tested for:

• This criteria is not applicable.

The Essbase Server and CLI was tested for:

• Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts

The Documentation was tested for:

• This criteria is not applicable.

The Web UI was tested for:

• This criteria is not applicable.

The Essbase Server and CLI was tested for:

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

The Documentation was tested for:

• This criteria is not applicable.

See WCAG 2.0 Section

No Format Conversion is performed.

No PDF Export is performed.

The Exports are in excel form and are accessible. The exported Excel has a strict format that allows the users to choose the format in which the dimensions can be exported (Either Parent-child or Generation based).

Excel Templates are provided that are accessible.

Accessibility features in Oracle Essbase Plus help make navigating and using the product easier for persons with disabilities and for the aging population. Standards-based assistive-technology hardware and software (such as Freedom Scientific JAWS or Microsoft Narrator) are used. Keyboard equivalents to some mouse actions are always available. Users can enable support for screen readers and magnifiers, high contrast color, and large on-screen fonts, after you sign into the service.

Accessibility Documentation can be found here:  https://docs.oracle.com/en/database/other-databases/essbase/21/essst/oracle-essbase-accessibility.html

Documentation is provided in Electronic format.