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
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
• Titles for Objects and Applets are provided
• CAPTCHAs are not used

Exceptions:

• BUG 32324079: When composing a conversation message, the attachment cancel icon does not have alternate text.
• BUG 34333456 - When viewing a message with attachments in the Service Request activity stream, a screen reader does not inform the user that the attachment contains a control for downloading the attachment.

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

Exceptions

• BUG 32420136: On the Service Request details page, the Recommendation region does not provide text to differentiate between the Recommended region and other regions.
• BUG 33357413: On the Create Service Request page, a screen reader does not read the page header.
• BUG 33357974: On the Service Request summary form, a screen reader does not read the next cell values in the drop down table on the Account and Primary Contact fields.
• BUG 32920221: In the To field on the Conversation Message composer, the start brace and end brace characters should not be read by the screen reader.  The beginning of the banner region should not be read  along with the Parent Page Button.
• BUG 32696844: When viewing a conversation message thread, the subject field is read as an H2 tag, rather than a span tag.
• BUG 32432321: When composing a conversation message, when recipients are added in the TO, CC, and BCC fields, the screen reader interprets the option to add another recipient as an extra recipient, leading the user to misunderstand the current number of recipients.
• BUG 32986700: While viewing the Service Dashboard using a screen reader,  text is not read for the Hide button on infolets nor the three-dot icon and associated menu. Also, no message is read after showing or hiding an infolet.
• BUG 32986151: After adding or removing an infolet from the Service Dashboard, the screen reader reads out the complete tree related details and location details before confirming that the infolet was added successfully.
• BUG 32986038: On the Service Dashboard, the screen reader reads out two different functions at the same time (Show or hide catalog and browse catalog) for the BI Catalog button
• BUG 32986007:  On the Service Dashboard, the visual label for the page should be a Level 1 heading.  The infolet names and the expand and collapse buttons should be headings.
• BUG 33984766 - In the Service Request foldout view, when focused on the Relationships panel, a screen reader only reads the title for each record and does not read the rest of the related information.
• BUG 34642396 - The service request audit view does not provide a label for every form element.
• BUG 33774072 - On the service request full details page, when the user tabs to the Title field, the instructional text explaining the 400 character limit is repeated three times by a screen reader.
• BUG 33769366 - In the Transfer Service Request component, the instructional text "Type # to bring up smart texts" is read twice by a screen reader.
• BUG 33769346 - In the Resolve Service Request component, the instructional text "Type # to bring up smart texts" is read twice by a screen reader.
• BUG 33764410 - In the Service Request full details page, when the user navigates to the Problem Description, a screen reader reads the instructional text "Type # to bring up smart texts" four times.
• BUG 33764373 - In the Service Request full details page, when the user navigates to the Solution Details, a screen reader reads the instructional text "Type # to bring up smart texts" two times.
• BUG 33759193 - When using a screen reader, the items are read twice in the Pending area of the service request activity stream page.
• BUG 33758974 - In the Service Request foldout page, a screen reader will read the recent items two times in the Activity panel.

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
• Instructions provided which refer to graphics include 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 product was tested for:

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

The product was tested for:

• Information is not conveyed using color

Exceptions

• BUG 33357534: On the Service Request list page, a screen reader reads the severity badge color as the incorrect color (brown rather than red).

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

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

The product was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom

Exceptions

• BUG 33112780 - On the Create Service Request page, a user is required to scroll in two dimensions to access all available actions.
• BUG 34272231 - In the service request message composer, the rich text editor controls are not visible at a browser 400% zoom level

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.

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

Exceptions:

• BUG 33760057 - When the Pending items area of the activity stream page displays multiple types of items, the user is not able to navigate the list as a a single table.
• BUG 33673001 - The user is not able to use a keyboard to navigate to the Reply button on an internal conversation in the activity stream.

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

• Single character keyboard shortcuts can be turned off.
• Single character keyboard shortcuts can be remapped.
• Single character keyboard shortcuts are only active when that component has focus.

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

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
• WAI-ARIA Landmark elements are used outside of repetitive navigation links

The product was tested for:

• Pages have a meaningful title specified in the TITLE element

Exceptions:

• BUG 32653525:  When the Create Service Request page is opened as a new browser tab, the screen reader does not read the header of the new page to indicate that a new tab has been opened.

The product was tested for:

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

Exceptions

• BUG 32879980: When a user navigates into the product picker using the keyboard, the focus goes to the create service request page rather than into the product picker pop-up
• BUG 32432321: When composing a conversation message, when the user focuses on the TO field to hear the list of current recipients, the focus goes to the end of the line of recipients instead of the beginning
• BUG 32986151: When navigating the Service Dashboard using the keyboard, if the user tabs back after adding a new infolet, the focus goes down to the next tile instead
• BUG 32923597: When the user uses the right arrow to expand a node in the hierarchy when editing the Service Dashboard, the focus moves back to the parent node
• BUG 32986919: When using the Configure action on the Service Dashboard, the focus goes to the drag and drop area rather than the browse catalog button.  Additionally, the user cannot then move the focus to the browse catalog button.
• BUG 32986919: When configuring the Service Dashboard, after expanding the catalog, focus goes to top of page rather than the expanded tree.
• BUG 33611624 - When the user navigates from the Service request foldout to the Activity Stream page, the focus for a screen reader is not placed at the top of the view starting with the recommendation panel; rather it begins reading the items in the dated history section.

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 can be found using the provided "search" function

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

Exceptions

• BUG 32986919: When viewing the Service Dashboard using a screen reader, there is no indication of focus when navigating to the Add Analysis to Dashboard element
• BUG 34678854 - In the Service Request foldout page, the focus does not move to the'Create a Relationship now link' in the Relationships panel.

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

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

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

Exceptions

• BUG 34217173 - the activity stream entries related to Actions and Action Plans do not always follow the same date/time format as defined in the user preference

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

Exceptions

• BUG 31753515: When a user attempts to create a Service Request without a Title, the error message is not read by a screen reader and when the user presses the down arrow clear instructions are not provided.

The product was tested for:

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

Exceptions

• BUG 32814308: On the Service Request and Case details page, when the user begins typing characters into the Assistant, the Assistant should instruct the user to use a down arrow to select one of the displayed values.

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 can be reversed by 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

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

Exceptions

• BUG 33020907: When the Contact list is displayed on the Service Request details page using filters, some of the fields contain elements that do not have unique IDs and table is missing text labels

The product was 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’.
• 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 have a meaningful title specified in the title attribute

Exceptions

• BUG 33357502 - On the Service Request list page, the screen reader 'T' keystroke does not read the table structure because it has a role of 'application' rather than 'table'.
• BUG 33759233 - The pinned area of the Service Request activity stream page does not allow a screen reader to indicate whether the region is expanded or collapsed.

The product was tested for:

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

Exceptions

• BUG 30868117:  After saving a new record on the Create Service Request page, no notification is given to indicate the Service Request was created.
• BUG 33624829 - When the user navigates from the Service request foldout to the Activity Stream page, a screen reader does not indicate when the page has been loaded.
• BUG 34510000 - On the Action Plan viewer within the activity stream, when the user selects any of the actions from the action menu, a screen reader does not provide feedback to indicate the result of each action being applied and the user must listen to the entire list actions to understand the state.

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.