Oracle Accessibility Conformance Report

 The product was tested for:

• Control and input field has an associated label that describes its purpose.
• Images that convey information have meaningful alternative text using ALT.
• Images that are decorative are marked up using ALT="".
• No time based media is used.
• CAPTCHAs are not used.
• Non-text characters are not used or have meaningful alternative text.
• Title for Objects and Applets are provided.
• Information shown in complex images such as charts is also available in an alternative textual form.

The product was tested for:

• User interface component labels are associated with the fields they are labeling.
• Row and column headers are identified for all data tables
• Headings are encoded with HTML heading tags.
• Data tables specify SUMMARY or CAPTION
• Layout tables use appropriate markup
• Groups of components are marked up with their descriptions.
• Style sheets are used only to change the layout and presentation on the screen.

Exceptions:

• 34087712: During a chat, improperly formatted text which is hidden, allows the Screen reader to read the hiddn text,  "Status", at the bottom of the chat_landing dialog
• 34194679: Improperly formatted text on the back of Agent Insight Cards allows the screen reader to read the text that is hidden.
• 32705725: No label is defined for checkboxes in Report Preferences
• 33319438: In Chat Preferences, "Max Active Chat" and "Stagger Incoming Chat" text boxes are unlabeled

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:

• A fixed display orientation is required for essential functionality.

The product was tested for:

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

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

Reports can be configured by the customers to modify the text font color/size as a result of the data meeting a configured conditional.  In these cases, the customer has configured the reports themselves and will have to ensure the shape and/or font weight address accessibility concerns. 

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

• Ensure that text can be resized up to 200% without loss of content or functionality.

Note:

• The user interfaces for individual object types are configured by the customer; it is your responsibility to ensure that these configurations resize appropriately.

The product was tested for:

• Besides the Oracle logo, images of text are not used.

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 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 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 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 product was 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)

Exception:

• 35382190: Unable to navigate to the Delete button in Recent Items
• 35499501: No keyboard navigation through pagination toolbar and access the pages in incident archiving 
• 33453827: Reset Password toolbar button on contact workspace  is not accessible using keyboard

The product was tested for:

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

The product was tested for:

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

The product was tested for:

• The user is given a two minute notice before they are logged out when their session expires and they can click a button during those two minutes to remain logged in.  We do not have any other time limits in our application.

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

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

Exceptions:

• 31894446: Unable to go to tabs such as incoming Email, Security and Audit log using keyboard tabbing in the mailbox

The product 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 fully inter-linked to each other.
• Page contains controls that enable reaching all pages.

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

• There are no single pointer operations

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

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

The product was tested for:

• Properly setting the language based on the language setting for the user in the .Net client.

The product was tested for:

• Passages or phrases in the content other than proper names and technical terms are rendered in the language specified in the interface.

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

• In circumstances where changing the value of the components causes a substantial change to the page, warning is given prior to the user interacting with those user-interface components.
• With Rules, our customers can configure scenarios where user input will shift the context of our application, potentially unexpectedly and unavoidably.

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 

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

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

• Submissions are reversible.
• Data entered by the user is checked for input errors with and the user is provided an opportunity for the user to correct them
• Data can be reviewed, corrected, and confirmed by the user before they are finalized
• A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

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
• Pages validate to the HTML specification

Exception:

• 32548951: The new contacts page has static elements with the same id attribute 

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

Exceptions:

• 32699075: When creating a new contact, the error warning image that appears on the alternate email field when the alternate email is not unique has a role of button instead of the correct role of image.
• 33724078: The expand/collapse button on a thread in a bug report is not labeled correctly causing the screen reader to ignore it.
• 33996748: In the User Preferences page there is no accessiblie name on slider input control for volume.

The product was tested for:

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

See WCAG 2.0 Section

The product does not contain functionality to convert from one format type to another.

The product does not provide capabilities to export or save any content in pdf format.

The product editor allows for content authoring within the product, and Oracle does not yet support prompting of user with accessibility information.

Exception:

• 35929649 - When adding text to threads in a bug report, there is no prompting for making the text accessibile

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:

• special keystrokes needed to operate control
• workarounds

Accessibility-related documentation can be found at:

http://documentation.custhelp.com/euf/assets/devdocs/bui/topicrefs/c_bui_Using_keystrokes_to_navigate_the_Agent_Browser_UI_6de27275.html?hl=f8 

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.