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.
• Controls have an associated name.
• Text summary or alternative is provided for time-based media.
• Non-text characters are not used or have meaningful alternative text.
• CAPTCHAs are not used.

Exceptions:

• RSCC-63: Main Home Page - The Notification Icon does not have an accessible name and should include a descriptive accessible name using aria-label, aria-labelledby, or a programmatically associated visible label.
• RSCC-64: Create ASN (Advanced Shipment Notice) - Combobox elements lack programmatic labels and should include accessible names using label, aria-label, or aria-labelledby.
• RSCC-65: Create Document - The document date picker has no associated label and should be programmatically associated with a visible or hidden label.
• RSCC-66: Item Management - The item image lacks alternative text and should include meaningful alt text or an aria-label describing its content or function.
• RSCC-67: Appointments Home - The calendar's parent element has missing or incorrect ARIA label/title and should include a valid aria-label or title to ensure correct interpretation of child elements by assistive technologies.

Supply Chain Hub does not have prerecorded audio-only or prerecorded video-only media

Supply Chain Hub does not have prerecorded audio media

Supply Chain Hub does not have prerecorded audio-only or prerecorded video-only media

Supply Chain Hub does not have prerecorded audio-only or prerecorded video-only media

Supply Chain Hub does not have prerecorded audio-only or prerecorded video-only media

The product was tested for:

• User interface component labels are associated with the fields they are labeling.
• Headings are encoded with HTML heading tags.
• 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:

• RSCC-68: Create PO (Purchase Order) - The tab section contains structural errors where ARIA or semantic heading markup is not applied correctly. Tabs should use proper ARIA roles or semantic HTML headings to convey hierarchy and relationships for screen reader users.
• RSCC-69: Create Document - Data tables lack proper headers, accessible summaries, or captions. Tables should include scoped headers, aria-describedby for summaries, or elements to communicate structure and relationships.
• RSCC-70: Issues Page & Items Management - ARIA roles are missing required child elements. ARIA parent roles must include valid child roles to expose correct structural relationships to assistive technologies.
• RSCC-71: Queries & Attachments - An undefined region is detected. The page section must have explicit landmarks with descriptive aria-label or aria-labelledby attributes for screen reader navigation.
• RSCC-72: Appointments Home - The calendar component uses incorrect ARIA role structure. It should implement a valid ARIA pattern that correctly exposes data relationships and supports logical keyboard navigation.

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.

• Note: The Supply Chain Hub is designed for desktop use only and does not restrict orientation.

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.

Supply Chain Hub does not have prerecorded audio-only or prerecorded video-only media

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.

Exceptions:

• RSCC-51: Appointments Home - The 'Slots Available' status text on the calendar has insufficient color contrast (light green on white), failing to meet the minimum contrast ratio requirement. Text should have a contrast ratio of at least 4.5:1 against its background to ensure readability for users with visual impairments.

The product was tested for:

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

Exceptions:

• RSCC-48: Issues Page - The error message is not fully visible and the 'Close' button is either cut off or inaccessible when zoom is applied. When text is resized up to 200%, the entire error message and the 'Close' button should remain fully visible and accessible without any part being cut off.
• RSCC-73: Procure To Pay Home Page - The absence of a horizontal scrollbar prevents users from accessing the full content of PO (Purchase Order) rows, hiding critical data. A horizontal scrollbar should appear, or the content should reflow responsively, so that data in the PO rows remains fully visible and accessible.
• RSCC-74: Create PO (Purchase Order) - Field labels (e.g., 'Supplier', 'Department') are truncated or cut off, making them hard to understand and reducing form usability. When text is resized up to 200%, field labels should remain fully visible and readable, preserving the form's usability.

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.
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

Exceptions:

• RSCC-50: Attachments - The modal window does not adapt correctly at high zoom, content becomes truncated or partially inaccessible. The modal window should reflow its content responsively so that information and UI elements remain fully visible and usable.
• RSCC-75: Create ASN (Advanced Shipment Notice) - It is not possible to see the content of some regions (eg.: 'Containers', 'POs'), the content within these regions should remain visible and operable at 400% zoom, using vertical scrolling only and avoiding content clipping.
• RSCC-76: Create Document - Navigation becomes complex at high zoom. It is not possible to select a PO to create the document. Interface elements should reflow to maintain logical navigation and operability, ensuring PO selection remains possible.
• RSCC-77: Procure To Pay Home Page - Existing POs (Purchase Orders) and related actions on the home page are difficult or impossible to access. The main page buttons and actions should remain visible and operable.
• RSCC-78: Issues Page - Error messages in the issues list are not readable. Error messages should remain fully visible and readable when the content is zoomed up to 400%, with no overlapping or cut-off content.
• RSCC-79: Upload Page - The main content of the modal is neither visible nor accessible when 400% to zoomed. The modal content should reflow or allow vertical scrolling so that no part of the user interface is cut off, hidden, or inaccessible.
• RSCC-80: Appointment Home - Slots are not visible or accessible at 400% zoom. The calendar and its available slots should reflow appropriately to ensure visibility and full accessibility at small viewport sizes.

The product was tested for:

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

• 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 (select as applicable):

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

• RSCC-39: Create Documents & Attachments - The keyboard focus does not reach the third modal, preventing keyboard-only users from interacting with it. Keyboard focus should move sequentially and reach open modal dialogs, allowing full operability without a mouse.
• RSCC-81: Create ASN (Advanced Shipment Notice) - In modals such as 'Add POs', 'Add Containers', and 'Add Items', the ESC key does not close the modal. Pressing the ESC key should dismiss the modal dialog.

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

• There are no single character keyboard shortcuts.

The product was tested for:

• Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times;

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:

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

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.

Exceptions:

• RSCC-44: Upload & Queries - In the 'Upload PO' (Purchase Order) and 'Queries' modals, interactive elements are not programmatically exposed as proper links or buttons. This prevents screen reader users from navigating or understanding their purpose. The links or interactive actions should have accessible names and be correctly marked up using semantic HTML with descriptive text.
• RSCC-82: Procure To Pay Home Page - 'Issues' column needs refactoring, especially for empty columns. Links should have clear text or be placed in an accessible table with properly labeled headers to clarify their function.
• RSCC-83: Create ASN (Advanced Shipment Notice) - Key headers like Shipment Date, Estimated Arrival Date, and Container Level are not programmatically exposed, making the link context incomplete. These elements should be marked up semantically so their purpose is understandable when navigating.
• RSCC-84: Attachments - The ‘Upload File’ button opens a modal but is not programmatically identified as a link or button, and its purpose is not announced. The button should be coded correctly and include an accessible name so its function is clear to assistive technologies.

The product was tested for:

• Pages can be found using the provided "search" function
• Pages are fully inter-linked to each other.
• Page contains controls that enable reaching pages.

Exceptions:

• RSCC-55: Alternative navigation options, such as search functionality or shortcut icons, are missing on several pages. Only the Queries Page provides multiple access points, from both the PO (Purchase Order) Home Page and within the PO itself.

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:

• The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

Supply Chain Hub does not use pointer gestures

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

Exceptions:

• RSCC-38: Main Home Page - The notification icon does not have an accessible name. The icon should have an accessible name that matches the visible label or clearly describes its function.
• RSCC-85: Queries - The 'Next' and 'Previous' buttons lack a proper label and are not properly recognized by screen readers. These buttons should have accessible names that correspond to their visible text or purpose, enabling screen readers to identify them properly.
• RSCC-86: Appointments Home - Facet filter options such as ASN (Advanced Shipment Notice) and RTV (Return To Vendor) are missing programmatic labels. These filter options should have programmatic labels that match their visible text to ensure accessibility.

The product was tested for:

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

The product was tested for: 

• All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.

Note: The Supply Chain Hub does not use dragging gestures or drag-and-drop functionality. All interactions are based on clicks or keyboard navigation.

The product was tested for:

• Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.

• The function can be achieved through a different control in the same software that meets this criterion

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:

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

Exceptions:

• RSCC-46: Procure To Pay Home Page & Appointments Home - When selecting a new value in a filter control results in an immediate change to the page content without prior notice or user confirmation. Users should be warned in advance before a change of context occurs, so they are prepared for the update and not disrupted, especially important for users relying on assistive technologies or keyboard navigation.

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.

Supply Chain Hub does not have help mechanisms 

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 or instructions are provided when the product requires user input.

Exception:

• RSCC-45: Main Home Page - The notification icon lacks an accessible label or instruction. The notification icon should have an accessible label or instruction clearly describing its purpose.
• RSCC-87: Queries - The "Next" and "Previous" buttons and submitted query comments are not programmatically identified. These buttons and comments should be programmatically identified with descriptive labels so that assistive technologies can properly announce them.
• RSCC-88: Create ASN (Advanced Shipment Notice) - Landmark regions do not have unique or accessible names. Landmark regions should have unique and accessible names to help users navigate the page effectively using assistive technologies.
• RSCC-89: Create Document - The Document Date Picker is missing an accessible label. Additionally, an element visually presented as a button does not function as one and should not be identified as a button. The Document Date Picker must have an accessible label. 

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:

• There are no occurrences of information that the user needs to enter which has been previously entered.

Authentication for Supply Chain Hub is provided by IDCS

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.

Exception:

• RSCC-43: Main Home Page - The notification icon is not properly announced by screen readers. The notification icon content must be correctly exposed with valid ARIA attributes to be properly announced by screen readers.
• RSCC-90: Upload - Three elements are visible under 'Template Name,' but screen readers announce four. Screen readers should announce the exact number of elements visible to users to avoid confusion.
• RSCC-91: Queries - The 'Next' and 'Previous' buttons and submitted comments are not read by screen readers. These buttons and comments must have appropriate ARIA roles and names to be announced correctly.
• RSCC-92: Attachments - The 'Uploaded File' modal and its interactive elements are not detected or announced by screen readers. The modal and its controls must be programmatically exposed with proper roles and labels.
• RSCC-93: Create PO (Purchase Order) - Elements use unsupported ARIA attributes (aria-sort="ascending"). Only supported ARIA attributes with valid values should be used.
• RSCC-94: Items Management - Date picker controls are missing announcements or labels for assistive technologies. Date pickers must have accessible labels and state information for assistive technology users.

The product was tested for:

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

Exception:

• RSCC-42: Create ASN (Advanced Shipment Notice) - Creation and cancellation messages are not fully announced by assistive technologies. Numerical values are read in Portuguese instead of the expected language. Status messages must be fully announced and in the correct language for users relying on assistive technologies.
• RSCC-95: Procure To Pay Home Page & Appointments Home - Facet filter updates trigger announcements only at the start of the update, but do not announce completion or changes in state. The “Please select a location” message from Appointment Home is not announced. The status changes, including creation, completion, and state updates, must be announced. Important messages like “Please select a location” should be communicated by assistive technologies.
• RSCC-96: Upload, Queries & Attachments - No success or error confirmation messages are announced after file uploads, query submissions, or attachment removals. Success and error messages must be programmatically exposed so they are announced by assistive technologies without requiring focus.

Documentation is not yet available to test

RSCC-56 has been raised to monitor the progress of documentation 

Product documentation is in electronic format.