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

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

The product was tested for:

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

The product 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
• Information conveyed by color has a contrast ratio of at least 3:1

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

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

The product was tested for:

• Images of text are not used

Infolet shows two scrolbars when zoomed to 400% (Bug 33662617).

The product 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 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.
• Information appears on hover or focus using default browser behavior, such as the title attribute of components.

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

There is no way for the end user to remap (bug 33638223) or turn off (bug 33638227) single character keyboard shortcuts.

The product was tested for:

• Time limits are not used

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

This is a component which is embedded into an application's web page, and so does not include web pages of its own.

This is a component which is embedded into an application's web page, and so does not include web pages of its own.

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

This is a component which is embedded into an application's web page, and so does not include web pages of its own..

The product was tested for:

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

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

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

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

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

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

• There are no status messages.

This component is embedded in web pages that are embedded in other applications, which define the contents of the page. There is no stand alone documentation on Infolet. As a result, the user-facing accessibility information is provided by the applications that embed the Infolet component.  Information on accessibility, will be included in this documentation. 

Product documentation is in electronic format.