Oracle Accessibility Conformance Report

The product 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
• Titles for Objects are provided
• Controls have an associated name
• No time-based media
• Client-side image maps specify the ALT attribute on each AREA element.
• 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
• Titles for Objects and Applets are provided
• Controls have an associated name
• Text summary or alternative is provided for time-based media
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

The product was tested for:

• User interface component labels are associated with the fields they are labeling
• Headings are encoded with HTML heading tags
• List markup is used for marking up lists
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
• Data tables specify SUMMARY or CAPTION in RTF templates
• 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 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
• Data tables specify SUMMARY or CAPTION
• Layout tables use appropriate markup
• Style sheets are used only to change the layout and presentation on the screen

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The documentation was tested for:

• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• Text fields which collect information about the user contain the appropriate autocomplete content attribute

Exception:

• Bug 32046048 - User Preferences input fields do not contain auto complete attribute

The documentation was tested for:

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

The product was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight
• Index or legends are used to convey color associations
• Information conveyed by color has a contrast ratio of at least 3:1

The documentation was tested for:

• Information is not conveyed using color.

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

• Text can be resized up to 200% without 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 documentation 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 was tested for:

• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

The documentation was tested for:

• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

The product was tested for:

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

The documentation was tested for:

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

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

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

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

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

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• There are no single character keyboard shortcuts

The documentation was tested for:

• There are no single character keyboard shortcuts

The product was tested for:

• The user is warned before time expires and given 4 minutes to extend the time limit by clicking OK on the message prompt

The documentation was tested for:

• Time limits are not used

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

• A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page
• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links

The documentation was tested for:

• A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links

The product was tested for:

• Pages have a meaningful title specified in the TITLE element

The documentation was tested for:

• Pages have a meaningful title specified in 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 documentation was tested for:

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

The product was tested for:

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

Exception:

• Bug 38643871 – The purpose of the hyperlink text “here” in the online report processing message is not discernible

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

• Pages are contained in a "site map"
• Pages can be found using the provided "search" function

The documentation was tested for:

• Pages are contained in a "site map"
• Pages are in a site table of contents
• Pages are fully inter-linked to each other

The product was tested for:

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

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

• Visual indication of the location of the focus

The documentation was tested for:

• Visual indication of the location of the focus

The product and documentation were tested for:

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

The documentation was tested for:

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

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

The documentation was tested for:

• There are no single pointer operations

The product has been 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 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:

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

• All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.

Exceptions:

• Bug 38814324 - Add support for using single pointer to rearrange placement of visualizations on a XPT Interactive layout.

The documentation was tested for:

• There is no functionality that uses dragging movements.

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

• Properly set lang attribute for each page

The documentation was tested for:

• Properly set lang attribute for each page

The product was tested for:

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

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

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

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

The product was tested for:

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

The documentation was tested for:

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

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

• None of the following help mechanisms exist: Human contact details, human contact mechanisms, self-help options, automated contact mechanisms.

The product 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:

• When input errors are detected, they are described to the user in text, including identifying the item where the error occurred.

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

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

The documentation was tested for:

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

The product was tested for:

• Data can be reviewed, corrected, and confirmed by the user before they are finalized

The documentation was tested for:

• Data can be reviewed, corrected, and confirmed by the user before they are finalized

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

The documentation was tested for:

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

The product was tested for:

• Steps which utilize a cognitive functional test have an alternative that does not rely upon a cognitive functional test.
• The product supports password entry by password managers.
• The product supports copy and paste while authenticating.

The documentation was tested for:

• Authentication is not required

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

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

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE,  etc.
• State information, properties, and values are programmatically exposed for user interface components

The 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.
• Custom controls have appropriate roles specified using the role attribute
• Frames have a meaningful title specified in the title attribute

The product was tested for:

• Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus

The documentations was tested for:

• There are no status messages

The product was tested for:

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

The product was tested for:

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

See the responses in the WCAG 2.0 section of this report

The product was tested for:

• File conversion preserves accessibility information.
• RTF or XPT template format creates HTML accessible file format.

The product was tested for:

• Tagged PDF generation
• conformance of PDF 1.7 output to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1)

The product was tested for:

• Prompts authors to create content that conforms to WCAG 2.0 AA.

Exception:

• Bug 38813477 – Add support to provide authoring-time prompts to guide users toward WCAG Level A and AA conformance.
   

The product was tested for

• Templates that allow content creation that conforms to level A and level AA success criteria in WCAG 2.0
• The Oracle Analytics Publisher Layouts provide templates for document titles, alternative text for images, Summary Text for Tables, Row Headers, Text Headers

Documentation along with examples on how to use accessibility features using RTF templates & Publisher Layout

• Design Accessible Reports Using RTF Templates
• Design Accessible Reports Using Publisher Layouts

The product was tested for

• Documentation on how to use accessibility features from report consumer perspective

https://docs.oracle.com/en/middleware/bi/analytics-server/user-publisher-oas/accessibility-features.html#GUID-6508DCF5-409C-4A1B-B740-67E8556B0D30

• Documentation on how to use accessibility features from report designer perspective 

https://docs.oracle.com/en/middleware/bi/analytics-server/design-publish/design-accessible-reports.html#GUID-FCD61A9B-F04F-4F15-BF24-23AC401ABE58

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acpmr/design-accessible-reports.html#GUID-FCD61A9B-F04F-4F15-BF24-23AC401ABE58

• Generating Accessible PDF output:

https://docs.oracle.com/en/middleware/bi/analytics-server/design-publish/generate-accessible-pdf-output.html#GUID-2447AD55-840D-430A-BDAD-09E21206A3B3

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acpmr/generate-accessible-pdf-output.html#GUID-2447AD55-840D-430A-BDAD-09E21206A3B3

Product documentation is in electronic format.