Oracle Accessibility Conformance Report

1.1.1 Non-text Content (Level A)

The product was tested for:

• Informative images include descriptive alternative text (ALT).
• Decorative images use empty ALT attributes (“”) or are styled as CSS background images.
• Every page and object has a clear, descriptive title.
• All controls are labeled with an accessible name.
• Non-text characters have been avoided.
• CAPTCHAs are omitted from the interface.

The product has the following exceptions:

1. Bug 38121003: Cart Page in List view mode - Icon(Edit/Delete/Duplicate/Delivery and Billing) control labels not accessible to keyboard users

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Supports

The Product was tested for:

• There are no audio-only or video-only materials that have been pre-recorded.

1.2.2 Captions (Prerecorded) (Level A)

The product was tested for:

• Pre-recorded videos have captions embedded within the media (which may be provided as an alternative version, if necessary).

The product was tested for:

• Pre-recorded video includes an alternative to the video

No live audio content in video is being used.

1.2.5 Audio Description (Prerecorded) (Level AA)

Supports

The product was tested for:

• Prerecorded video includes synchronized audio descriptions

1.3.1 Info and Relationships (Level A)

The product underwent testing to evaluate the following aspects:

• Labels for user interface components are correctly associated with their corresponding fields.
• Headings are properly structured using HTML heading tags.
• Lists are formatted using appropriate list markup.
• Data tables utilize correct table markup, including the use of row and column headers, as well as captions or summaries where applicable.
• Data tables provide a SUMMARY attribute or CAPTION element.
• Layout tables are constructed using appropriate markup to distinguish them from data tables.
• Groups of related components are marked up together with descriptive information.
• Style sheets are used solely for controlling layout and visual presentation, not for conveying structural or semantic information.

The product has the following exceptions:

1. Bug 33113005: Row headers are missing for the charge account table on the Update Requisition Preferences page.
2. Bug 34025041: On the Catalog Search Results page of the Redwood version of the application, VoiceOver doesn't read the values of the Sold by, Amount and Packaging String attributes (all secondary or tertiary text) for each displayed search result. This is because the card widget used in displaying each search result doesn't have the correct structure for secondary/tertiary texts.
3. Bug 37392906: It isn't clear if the table on the Redwood version of the Requisition Approved FYI notification is a layout or data table.
4. Bug 37209974: It isn't clear if the table on the Redwood version of the Requisition Approval Request notification is a layout or data table.
5. Bug 37337112: It isn't clear if the table on the Redwood version of the Requisition Withdrawn notification is a layout or data table.
6. Bug 37315061: It isn't clear if the table on the Redwood version of the Requisition Returned by Buyer notification is a layout or data table.
7. Bug 37309399: It isn't clear if the table on the Redwood version of the Requisition Canceled notification is a layout or data table.
8. Bug 37227538: It isn't clear if the table on the Redwood version of the Requisition Reassigned notification is a layout or data table.
9. Bug 37805793: No label assigned to the 'Additional Details' link on the requisition line.

1.3.2 Meaningful Sequence(Level A)

The product was tested for:

• The DOM element sequence reflects a logical and accessible reading order.

The product has the following exceptions

1. Bug 25897680: When user navigates from a field in a page to a popup and then closes the popup, focus doesn't go back to the field from which user left the page. Instead focus goes back to the top of the page.

1.3.3 Sensory Characteristics(Level A)

The product was tested for:

• Instructions do not rely exclusively on sensory characteristics such as shape, size, visual position, orientation, color, or sound.
• When instructions refer to graphics, they also mention the associated text alternative.

1.3.4 Orientation (Level AA)

The product was tested for:

• Text remains fully visible and functional in both device orientations. However, in the case of tabular data, horizontal/vertical scrolling may be required to view all content. 

1.3.5 Identify Input Purpose (Level AA)

The interface does not include any text fields intended to gather user data.

1.4.1 Use of Color(Level A)

The conveyance of information does not depend on color alone.

1.4.2 Audio Control(Level A)

There is no use of audio that starts/plays automatically.

1.4.3 Contrast (Minimum) (Level AA)

The product was tested for:

• Large-scale text and images of large-scale text maintain a minimum contrast ratio of 3:1.
• All other text and images of text meet a minimum contrast ratio of 4.5:1.

1.4.4 Resize text(Level AA)

The product was tested for:

• Resizing text up to 200% does not affect content or functionality.

1.4.5 Images of Text(Level AA)

Text is not presented as images.

1.4.10 Reflow (Level AA)

The product was tested for:

• At 400% zoom, text content adjusts to ensure that users need to scroll in only one direction.

The product has the following exceptions

1. Bug 31089292 - When UIs on the non-Redwood version of the App are zoomed to 400%, you need both scroll bars to view/navigate the complete UI.

1.4.11 Non-text Contrast (Level AA)

The product was tested for

• All non-text items maintain at least a 3:1 contrast ratio.

1.4.12 Text Spacing (Level AA)

The product was tested for:

• Modifying only the following text spacing properties to the specified minimum values does not result in any loss of content or functionality:
  1. Line height (line spacing) is set to at least 1.5 times the font size.
  2. Spacing after paragraphs is set to at least 2 times the font size.
  3. Letter spacing (tracking) is set to at least 0.12 times the font size.
  4. Word spacing is set to at least 0.16 times the font size.

1.4.13 Content on Hover or Focus (Level AA)

The product was tested for:

• Dismissable: Content that appears on hover can be dismissed without requiring users to move their pointer or change keyboard focus.
• Hoverable: When additional content is triggered by hovering the pointer, users are able to move the pointer onto the revealed content without causing it to disappear.
• Persistent: The additional content displayed on hover remains visible until one of the following occurs: 
  1. The hover or focus is removed, 
  2. the user dismisses the content, 
  3. or the content becomes irrelevant.

2.1.1 Keyboard(Level A)

The product was tested for:

• All functions are fully operable using only the keyboard, without the need for specific timing of individual keystrokes.
• Unique keystrokes and access keys, including those specified in product documentation, function correctly.
• The product supports use with operating system keyboard accessibility aids, such as StickyKeys and FilterKeys (noting that feature names may vary across platforms).

The product has the following exceptions:

1. Bug 25874895: User is unable to select one or more options (displayed as checkboxes) on the Approvals Action History Page, using just a keyboard.
2. Bug 25878760: The access key to activate the "Done' button on a popup on the Manage Content Zones page is not working.
3. Bug 25907315: The access key to activate the "Done' button on a popup on the Manage User-Defined Attributes page is not working.
4. Bug 33131580: User is unable to trigger the "Charge Account" popup, on the Requisition Details page, to see the segment names using just keyboard. Note that the page itself shows the full values of the different segments of the charge account.
5. Bug 33065968: User is unable to select an agreement from a list of suggested agreements, on the Create/Edit Smart Form page, using just a keyboard.
6. Bug 33113142: Some elements on the Update Preparer and Requester pages are not reachable via keyboard navigation
7. Bug 33163259: Some buttons are not reachable via keyboard navigation on some pages when user is on a Mac and browsing with Firefox.
8. Bug 32614306: When screen reader on the IOS platform is turned on, a user is only able to select part of a value from the list of supplier values on the Create Noncatalog Request page. This defect is only observed on the Redwood version of the application.
9. Bug 34129103: Unable to add item from Catalog search results using keyboard
10. Bug 38140214: Accessibility issues in “Charge To - Combination details” info popup in Cart page

2.1.2 No Keyboard Trap (Level A)

The product was tested for:

• Users can navigate through all controls using only the keyboard, with no keyboard traps that prevent moving focus away from any control.

2.1.4 Character Key Shortcuts (Level A)

Single-character keyboard shortcuts are not used.

2.2.1 Timing Adjustable(Level A)

Users are not subject to time limits.

2.2.2 Pause, Stop, Hide (Level A)

There is no content that moves, blinks, or scrolls automatically.

2.3.1 Three Flashes or Below Threshold(Level A)

The product was tested for:

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

2.4.1 Bypass Blocks(Level A)

The product was tested for:

• Page structure and hierarchy are marked up with header elements, positioned outside recurring navigation links.

2.4.2 Page Titled(Level A)

The product was tested for:

• Each page has a descriptive and meaningful title specified in the TITLE tag.

2.4.3 Focus Order(Level A)

The product was tested for:

• Keyboard navigation moves through focusable components in an order that reflects a coherent and meaningful sequence.

2.4.4 Link Purpose (In Context)(Level A)

The product was tested for:

• Link text, whether in a paragraph, list, or table cell with proper headers provide enough information to understand the link’s purpose.

2.4.5 Multiple Ways(Level AA)

The product was tested for:

• All pages are fully interlinked, allowing easy navigation between them.
• Each page includes controls that enable users to access other pages

2.4.6 Headings and Labels(Level AA)

Supports

The product was tested for:

• Headers accurately convey the topic or purpose of the content that follows.
• Labels clearly indicate the purpose of their associated fields.

The product has the following exceptions:

1. Bug 38140131: Preferences drawer - Subheadings lack semantic tags 

2.4.7 Focus Visible(Level AA)

The product was tested for:

• Visual cue to identify the element that has keyboard focus.

2.4.11 Focus Not Obscured (Level AA)

The product was tested for:

• The initial position of user interface components that receive keyboard focus is never completely obscured by content created by the author.

2.5.1 Pointer Gestures (Level A)

The interface does not use multipoint or path-based gestures' action.

2.5.2 Pointer Cancellation (Level A)

No functionality depends solely on single pointer operations.

2.5.3 Label in Name (Level A)

The product was tested for:

• User interface components with labels that include text or images of text have accessible names containing the same text as is presented visually.

The product has the following exceptions:

1. Bug 38542476: 'Reassign Requisition' drawer name not being announced by JAWS.
2. Bug 38542412: Cell details in View Lifecycle Details table not being announced correctly by JAWS on keyboard navigation.
3. Bug 38492334: JAWS does not announce the 'Item Description' field when navigating the Create Noncatalog Request page with the keyboard.

2.5.4 Motion Actuation (Level A)

No functionality requires device motion.

2.5.7 Dragging Movements (Level AA)

The product was tested for:

• Any functionality that requires a dragging motion can also be performed using a single pointer without dragging.

2.5.8 Target Size (Minimum) (Level AA)

The product was tested for:

• Interactive targets are at least 24×24 CSS pixels in size, including any surrounding white space, and do not share this space with other interactive targets.
• The requirement for minimum target size is considered fulfilled only if:
  1. An alternative control in the same software meets the criterion,
  2. The target is in a sentence or restricted by line-height, or
  3. A specific size is essential or content is legally required.
      

The product has the following exceptions:

1. Bug 36922153: Some interactive targets in the Catalogs work area do not have a minimum size of 24 by 24 CSS pixels.

3.1.1 Language of Page(Level A)

The product was tested for:

• All pages have the appropriate lang attribute defined.

3.1.2 Language of Parts(Level AA)

Supports

The product was tested for:

• A consistent language is used throughout the entire page.

3.2.1 On Focus(Level A)

The product was tested for:

• Any element does not cause a significant change in content, alter keyboard focus, or open additional windows on receiving focus.

3.2.2 On Input(Level A)

The product was tested for:

• Altering a UI component’s value does not lead to significant page changes, additional changes in keyboard focus, or the opening of pop-up windows.

The product has the following exceptions:

1. Bug 33337659: Changing an input value on the Edit Requisition page leads to a change of value for a previous input and the user is not advised of this change.
2. Bug 33066143: Entering the first few characters in an LOV (List of Values) on the Manage Smart Forms page triggers a popup about the user-entry being an incorrect value before it then finds one or more matching records which are displayed in a separate popup without closing the first popup.

3.2.3 Consistent Navigation(Level AA)

The product was tested for:

• Pages within the same group maintain consistent navigation, with elements presented in the same sequence in each Page.

3.2.4 Consistent Identification(Level AA)

The product was tested for:

• Images and controls are consistently implemented and labeled across all parts of the product.

3.2.6 Consistent Help (Level A)

Not Applicable

Help document(or a link to different software containing help) occur in the same order relative to other software content.

3.3.1 Error Identification(Level A)

The product was tested for:

• When input errors are detected, they are described to the user in text, specifying the item where the error occurred.

3.3.2 Labels or Instructions (Level A)

The product was tested for:

• User input fields are accompanied by labels or instructions as needed.

3.3.3 Error Suggestion (Level AA)

The product was tested for:

• The product offers suggestions to users when known fixes for input errors exist.

3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)

The product was tested for:

• Users can Edit/Cancel requisition submissions.
• Data is validated for input errors, providing users the opportunity to correct them.
• Users can review, and modify data before finalizing their submission.

3.3.7 Redundant Entry (Level A)

Supports

The product was tested for:

• Users are not required to re-enter information that they have previously provided.

3.3.8 Accessible Authentication (Minimum) (Level AA)

The product was tested for:

• The product is compatible with password managers for password entry.
• The product allows copy and paste functionality during authentication.

4.1.1 Parsing(Level A)

Not Applicable

Content using HTML or XML is considered to inherently meet this criterion.

4.1.2 Name, Role, Value (Level A)

The product was tested for:

• HTML controls have programmatically associated names derived from appropriate elements and attributes, such as LABEL, TITLE, SUMMARY, and CAPTION.
• Additional state information for HTML controls, such as whether a field is 'required', is programmatically exposed.
• Frames specify a meaningful title using the title attribute.

The product has the following exceptions:

1. Bug 33567816: On the Edit Requisition page of the Redwood version of the application, screen reader doesn't read the contents of the charge account information popup.
2. Bug 38140159: Catalog search box does not have suitable programmatic label

4.1.3 Status Messages (Level AA)

The product was tested for:

• Roles or properties are assigned to status messages so that assistive technology users receive information even when the component does not have focus.

The product has the following exceptions:

1. Bug 31338467: Some confirmation messages cannot be read to the user by assistive technologies because the confirmation messages are not available in accessibility mode.
2. Bug 34120043: When user executes a search for products/services using the Catalog Search field in the Redwood version of the application, user is not informed by assistive technologies when the application has executed the search and returned results.

503.4.1 Caption Controls

The product was tested for:

• The video output is in YouTube which has user controls for the selection of captions which are provided at the same menu level as the user controls for volume or program selection.

503.4.2 Audio Description Controls

The product was tested for:

• The video output is in YouTube which has user controls for audio descriptions which are provided at the same menu level as the user controls for volume or program selection.

See the responses in the WCAG section 2.x of this ACR.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Supports

The product was tested for:

• The format of content remains unchanged per preferences.

504.2.2 PDF Export

Supports

The product was tested for:

• The Authoring Tool does not have the capability for PDF Export.

504.3 Prompts

The product was tested for:

• The product's authoring tool has limited capabilities such as ability to create lists, format (style) text and author content in plain text. The tool automatically generates the html code for any of the styles/formats.

504.4 Templates

No templates are available in the authoring tool

602.2 Accessibility and Compatibility Features

The product documentation describes:

• Accessibility modes available during installation or at runtime
• Special keystrokes required to operate controls
• Documented workarounds for accessibility barriers

The Accessibility chapter in Oracle Applications Cloud Using Common Features contains all accessibility-related documentation.

Product documentation is in electronic format.

603.2 Information on Accessibility and Compatibility Features

Oracle Global Customer Support offers information/guidance on the accessibility features of the product.

603.3 Accommodation of Communication Needs

• Oracle customers can access electronic support through My Oracle Support or by calling Oracle Support at +1.800.223.1711.
• Hearing-impaired customers in the U.S. may speak with an Oracle Support representative using a telecommunications relay service (TRS). Information about TRS can be found at http://www.fcc.gov/cgb/consumerfacts/trs.html , and a list of TRS telephone numbers is available at https://www.fcc.gov/general/trs-state-and-territories.
• International hearing-impaired customers may use TRS by dialing +1.605.224.1837.
• An Oracle Support engineer will respond to technical issues according to the standard service request process.