Oracle Accessibility Conformance Report

• 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)
• Client-side image maps are not used
• CAPTCHAs are not used

No pre-recorded audio-only or video-only content is being used

No pre-recorded video content is being used

No pre-recorded video content is being used

No live audio content in video is being used

No pre-recorded video content is being used

The product was tested for:

• User interface component labels are associated with the fields they are labeling
• Groups of components are marked up with their description
• Style sheets are used only to change the layout and presentation on the screen

The product does not contain any data tables, headings or lists

Bug 24921899: Screen reader issue: Titles on Infolet cards are not flagged with 'heading' tags and so will not be as easy to identify with a screen reader

The product was tested for:

• The sequence of elements in the DOM matches a 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

• Information conveyed by color is available in alternative formats, such as shape, text, font weight

No automatically playing audio is used

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

Bug 23302115: High Contrast Issue: Titles of Infolet cards with 'more details' links will show up as dark blue on a black background in some browsers.

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

Images of text are not used

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
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

Bug 24964827: Navigation Issue: If the arrow keys are used to change the focus between bars of a bar graph, or segments of a ring or pie chart, they will trigger an automatic navigation to the appropriate target page.  "Control" needs to be held down while using the arrow keys to change the focus without this navigation.  

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

Time limits are not used

There is no moving, blinking or scrolling content

The product was tested for:

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

Bug 22338458: Navigation Issue: If an Infolet card is flipped with the keyboard focus on the card, the keyboard focus will move off the card and the user will need to navigate back to the card.

Bug 24964827: Navigation Issue: If the arrow keys are used to change the focus between bars of a bar graph, or segments of a ring or pie chart, they will trigger an automatic navigation to the appropriate target page.  "Control" needs to be held down while using the arrow keys to change the focus without this navigation.  

• 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 will be embedded in web pages that are embedded in other applications - locating web pages will be handled by the containing web app.

No headings or labels are generated by the product.  All descriptive text is provided by the application that embeds the product.

Bug 24921899: Screen reader issue: Titles on Infolet cards are not flagged with 'heading' tags and so will not be as easy to identify with a screen reader

• Visual indication of the location of the focus

Bug 24585009: Keyboard Focus Issue: The keyboard focus indicator is in general visible, however, on Edge and IE browsers the title of cards will not show a focus indicator.  Other browsers work correctly.

• Properly set lang attribute for each page.

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

• 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

Bug 24964827: Keyboard Focus Issue:  If the arrow keys are used to change the focus between bars of a bar graph, or segments of a ring or pie chart, they will trigger an automatic navigation to the appropriate target page.  "Control" needs to be held down while using the arrow keys to change the focus without this navigation.

• In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components

The product will be embedded in web pages that are embedded in other applications - page-level navigational mechanisms will be handled by the containing web app.

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

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

The product will be embedded in web pages that are embedded in other applications.   Labels and instructions will be provided by the embedding application

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

• Data is checked for input errors with an opportunity for the user to correct them
• Data can be reviewed, corrected, and confirmed by the user before they are finalized

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

• 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 appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes
• Custom controls have a meaningful programmatically exposed name
• Frames and Forms are not used

The product will be embedded in web pages that are embedded in other applications, which will define the contents of the page. As a result, the user-facing accessibility information must be provided by the applications that embed the product.  Information on accessibility, including keyboard shortcuts,  will be included in this documentation. The framework is capable of rendering content as described below, when a developer uses it according to guidance provided in the containing web app’s reference manual and follows all other applicable accessibility standards and guidelines.

Product documentation is in electronic format.