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 32651879: On the Service Request create and edit forms, the icon to open the selector for the Product field does not have alternate text.
• BUG 32347576: On the Service Request details page, when Contacts are filtered from the left panel, the buttons on the list of contacts do not have alternate text.
• BUG 32324079: When composing a conversation message, the attachment cancel icon does not have alternate text.

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 32527794: On the Service Request details page, the Recommendation region does not provide text to differentiate the type of item that is being recommended.
• BUG 32420065: On the Service Request details page, actions that appear in the Recommendation region do not provide text of the specific action name and the combo button is not read by a screenreader.
• BUG 32705302: When the Service Request activity stream is filtered, the screen reader does not read the labels for currently active filter chips nor the affordance to remove the filters.
• BUG 32495080: When the Product picker is opened on a Service Request form the "select a group" product heading is not read by a screen reader.
• BUG 33133670: The page header of the Service Request details page should be set to Level 1.
• BUG 32494823: The levels of headers do not accurately depict the page structure on the Create Service Request page, Service Request details page, Service Request list page
• BUG 33020907: When the Contact list is displayed on the Service Request details page using filters, some of the elements in the table are missing text labels
• 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 32885471: In the Conversation Messages page the column headers are not read when a particular cell item is read by a screen reader. Additionally, when the list page is searched the screen reader does not read the results count and results contents.
• 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.

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.

Exceptions

• BUG 31605397:  When viewing the Service Request full details in portrait orientation, the Add Team Member selector is not rendered properly and the user must switch to landscape orientation to perform the action.
• BUG 31550066:  When the Engagement Component is active in the Service Request details page, a user will not be able to view the content of the component if the browser is in portrait orientation or if the overall browser width is too small.

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

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

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

Exception

• BUG 32557829:  On the Service Request list page, the text for the Severity badge and Critical badge is not center aligned.

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 32651862:  On the Service Request create and edit forms, the icons to clear the values from the Account and Contact fields are not selectable using the keyboard.
• BUG 32584444:  On the Service Request create and edit forms, when editing the Account and Contact fields, pressing down arrow does not show any options and the down arrow button does not receive any focus.  
• BUG 32576334: When navigating the Service Request message composer with a keyboard, the links to Edit Draft and Discard Draft and the CC and BCC fields are not selectable.
• BUG 33020901:  When contacts are filtered on the Service Request details page using the left panel, the button to navigate to the Contact full details page is not selectable using a keyboard.
• BUG 33020868:  When navigating the left panel of the Service Request details page using a keyboard, the user is unable to select the link to filter related contacts.

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 32494823: The page title of the Create Service Request and Service Requests List pages should be set
• 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 32495080: When the product picker is opened on a Service Request form, the focus immediately moves to the first product in the tree rather than the search box
• BUG 32348501: On the Service Request details page, when a link for a related item is selected in the left panel, the focus does not shift to the filter area in right side of the page immediately. The focus goes back to the page URL/header so the user must tab many times to get to the filters
• BUG 32920221: While composing a reply message in the Conversation Messages page, when the page is first loaded the focus is on the top of the page instead of the first text field in the page. When navigating thru the right section of the Conversation Messages page using the keyboard, the focus goes to each frame instead of each text item inside the frame
• BUG 31748439: After posting a message to a conversation thread using the keyboard,  the focus goes to the top of the left panel rather than to the header of the message that was just sent
• 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.

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

Exception

• BUG 32494986: On the Service Request full detail page, the Edit button on the summary form is not clearly labeled to indicate it applies to the summary section

The product was tested for:

• Visual indication of the location of the focus

Exceptions

• BUG 32469039:  When editing an Internal Note using the keyboard, there is no indication of focus when navigating to the Add Attachment icon
• BUG 32986919: When viewing the Service Dashboard using a screen reader, there is no indication of focus when naviagting to the Add Analysis to Dashboard element

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.

Exceptions

• BUG 31931769: The link for the count of associated Action Plans that is displayed in the left hand panel of the Service Request details page does not include the visible text as part of the accessible name.

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

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.
• BUG 32630929: On the Service Request list page, if an error appears the screen reader is not able to read the text of the error.

The product was tested for:

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

Exceptions

• BUG 31512580: The toolbar controls for Font Style and Font Size in the message composer do not have their visible text as part of their accessible name
• BUG 32495185: When editing the Account field on a Service Request form, the user is not prompted to use Enter or Space button to select
• 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 33021484: On the Service Request full record page, the Contacts table contains elements that do not have unique IDs
• 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

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 32420191: On the Service Request details page, when an Action Plan action is initiated there is no announcement that the new UI region was loaded successfully.
• BUG 32495185: When editing the Contact field on a Service Request form, the user is not notified if the user interface is still loading values.
• BUG 32420065: On the Service Request details page, there is no text based message to indicate to the user when they have exited the Recommendation region.
• Bug 32871855:  In the Service Request list, when the user Assigns the SR to oneself, a notification appears.  There is additional unrelated text read out by the screen reader in additional to reading out the content of the notification.

The product documentation describes :

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

Accessibility-related documentation can be found at:

Oracle Applications Cloud Using Common Features, Chapter 13 Accessibility

Product documentation is in electronic format.