Oracle Accessibility Conformance Report

The product and documentation were tested for:

• Images that convey information have meaningful alternative text using ALT and if necessary, LONGDESC
• Images that are decorative are marked up using ALT=”” or CSS background images
• Data shown in dynamically generated images such as charts is also available in an alternative textual form (e.g. a data table).
• Data tables specify SUMMARY or CAPTION
• Titles for Pages, Objects and Applets are provided.
• CAPTCHA elements convey information that have meaningful alternative text using ALT.

The product and documentation were 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 tables, including row and column headers and table caption/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

Exceptions:

• Bug 32651114: The input boxes (From and To) to select a date range in the Filters of the Moderation dashboards pop up is missing labels
• Bug 34087711: In a disconnected chat, the following text is formatted incorrectly and should be hidden so that the screen reader does not read element on chat landing dialog:: "Type your message here, then click Send or press"
• Bug 34087712: In a connected chat, the following text is formatted incorrectly and should be hidden so that the screen reader does not read element on chat landing dialog: "Status"

The product and documentation were tested for:

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

The product and documentation were 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 the text alternative of the graphic

The product and documentation were tested for:

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

The product and documentation were tested for:

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

The product and documentation were tested for:

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

The product and documentation were tested for:

• Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
• All other text and images of text have a contrast ratio of at least 4.5:1
• Colors can be set by altering the associated style sheet.

The product and documentation were tested for:

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

The product and documentation were tested for:

• Images that convey information have meaningful alternative text

The product and documentation were tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.
• An alternative mobile user interface is available and is accessed from the main application.
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

This product and documentation were tested for: 

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

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

This product and documentation were tested for:

• Ability to perform functions from the keyboard only
• Logical movement of focus through the controls
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

This product and documentation were tested for:

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

The product and documentation was tested for:

• There are no single-character keyboard shortcuts.

The product and documentation were tested for:

• Content that automatically updates, or time limits, can be adjusted by the user.

The product and documentation was tested for:

• There is no moving, blinking, or scrolling information. 

The product and documentation were tested for:

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

The product and documentation were 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

The product and documentation were tested for:

• Pages have a meaningful title specified in the TITLE element

The product and documentation was tested for:

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

Exception:

• Bug 34113136: User name menu first link not focused on first down arrow key press on some browsers

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

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

The product and documentation were tested for:

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

The product and documentation were tested for:

• Visual indication of the location of the focus

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, 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 and documentation were 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.

The product and documentation were tested for:

• Properly set lang attribute for each page

The product and documentation were tested for:

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

The product and documentation were tested for:

• Ability to perform functions from the keyboard only
• Logical movement of focus through the controls
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation

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

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

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:

• Content does not require user input

The product and documentation were tested for:

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

Exceptions:

• Bug 32651114: The input boxes (From and To) to select a date range in the Filters of the Moderation dashboards pop up is missing labels

The product and documentation were tested for:

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

 The documentation was tested for:

• Content does not require user input

The product was tested for:

• 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

The documentation was tested for:

• The documentation does not require user input that modifies user controllable data.

The product and documentation were 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 and documentation were 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 and iFRAMES are titled with meaningful text

The product and documentation were tested for:

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

The product and documentation were tested for:

• The authoring tool provides a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for all supported features and, as applicable, to file formats supported by the authoring tool.
• The authoring tool permits authors the option of overriding information required for accessibility.

Customer portal does not contain functionality to convert from one format type to another.

Customer portal does not provide capabilities to export or save any content in pdf format.

• Bug 35922845: Customer Portal Social community page editors do not support prompting to make content accessible

The use of the product editor is for users to format content, and does not provide any capabilities for the user to select a template.

The product documentation describes:

• accessibility modes, either at installation or runtime
• special keystrokes needed to operate controls
• workarounds

Accessibility-related documentation can be found in the Accessibility Chapter of Oracle Applications Cloud Using Common Features.

Product documentation is in electronic format.

Oracle Service Cloud Support can provide information about accessibility features of the product.

Oracle customers have access to electronic support through http://cx.rightnow.com or by calling Oracle Service Cloud Technical Support at 1.800.806.6592.  Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support Representative may use a telecommunications relay service (TRS).  Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory.  International hearing-impaired customers should use the TRS at +1.605.224.1837.  An Oracle Support Engineer will respond to technical issues according to the standard service request process.