Oracle Accessibility Conformance Report

VPAT® Version 2.5

Name of Product:

Oracle Fusion Global Human Resources 11.13.25.04.0

Product Description:

Oracle Fusion Applications are a suite of web-based enterprise software business products.  This ACR covers six (6) products. Bugs referenced in the technical criteria in this ACR use the following acronyms to indicate which product they apply to.

  • Fusion Global Human Resources (GHR)
  • Fusion HCM Central Components (HCC)
  • Fusion Workforce Modelling (WM)
  • Fusion Workforce Predictions (WP)
  • Fusion Workforce Directory Management (WDM)
  • Oracle Fusion Checklist (OFC)

We have 2 distinct market segments with our Global Human Resources product as one is for companies taking up the full solution and that is Global Human Resources. Also we have companies taking up just a talent management solution, they need a subset of features of the Global Human Resources product which we term as Fusion Workforce Directory Management.  Fusion Workforce Directory Management is a subset of the features contained within Fusion Global Human Resources. Fusion HCM Central Components covers HCM-wide components. Likewise, Oracle Fusion Checklist functionality is utilized across HCM for capturing related sequential tasks, as used in Journeys.

These product applications are mobile responsive. The new and redesigned HCM Responsive User Experience is available and promoted as our standard. The employee and manager self-service pages have been redesigned to look and behave the same on desktop and mobile devices, including iOS.

The responses to many of the technical standards are based on functionality provided by underlying technologies; please see the ACRs listed in the Dependent Products section for more information.

Report Date:

03-Apr-2025

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

  • PDF and ePub files

Oracle Fusion Applications has several runtime modes, set via accessibility preferences, such as screen reader, high contrast, and large fonts modes.  Consult Oracle Fusion Applications Help for detailed information on accessibility preferences. 

Dependent Products


This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.2Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports
The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Partially Supports
Some functionality of the product does not meet the criteria.
Does Not Support
Majority of functionality of the product does not meet the criteria.
Not Applicable
The criteria are not relevant to the product.

WCAG 2.2 Report

Table 1 also documents conformance with:

  • Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria
Conformance Level
Remarks and Explanations
1.1.1 Non-text Content (Level A)Partially Supports

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.
  • CAPTCHAs are not used.

Exceptions:

  • Bug 37295465 (GHR): On the Redwood Document Delivery Preferences, the label doesn't match the trashcan icon on the Check-in Nudge The secondary action is the same label as the Action label to "Add to Check-in"; however the corresponding icon is a trashcan which would mean it will remove the nudge item which is not intuitive to any user.
  • Bug 37251136 (GHR): Redwood Approval History on transaction flow icons are missing alt text.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe product has no multimedia.
1.3.1 Info and Relationships (Level A)Partially Supports

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 34480204 (WDM): Unlabeled form controls appear in Directory advanced search.
  • Bug 34459136 (WDM): Directory heading structure is not properly reflected.
  • Bug 34482182 (GHR): Inappropriate heading structure for Documents of Record
  • Bug 34486116 (GHR): List mark-up is missing for Documents of Record "Last Updated" advanced search filter.
  • Bug 34661025 (HCC): Incorrect headings are identified for section headings in Change Manager, Change Location, Change Working Hours, Terminate Work Relationship, Transfer, and Change Assignment.
  • Bug 35323800, 35323794 (GHR) and 35331927 (HCC): Screen reader is unable to distinguish corresponding edit button labels for each Document Delivery Preference and Document Record rows, so the user doesn't know which item or object is being edited.
  • Bug 35759462 (GHR): Transaction Console Summary is missing labels for the select all header, from and to date range pop-up window, plus incorrect label reference when filtering transaction table results.
  • Bug 35738724 (GHR): Document Records expand button is not providing information regarding which specific document is being acted on for a screen reader user.
  • Bug 34451798 (GHR): Approval rules and Approval rule testing page structure headings are missing, and landmarks do not have a unique role or role/label/title combination.
  • Bug 35850747 (HCC): Info to Include questionnaire switches are missing labels in the Request a New Position, Request a Position Change. The Employment Change transaction contains a page with Position Override options, where an error identifies that the data table/grid is missing accessible text.
  • Bug 36080463 (HCC): Info to Include questionnaire switches are missing labels/accessible name in the Requisitions, (Recruiting) Positions, Offer CGP, Edit Employment, Request a New Position, Request a Position Change, and other compact guided process (CGP) questionnaire pages, and anywhere switches are used within a process flow, such as Convert Pending Worker, Position Override, Change Assignment, and Add Pending Worker.
  • Bug 35070429 (HCC): Redwood search filter button on is missing a descriptive label on all pages where search filtering is available, such as Person Benefit Group page.
  • Bug 37524645 (GHR): Document Security Profile's data table/grid is missing accessible text.
  • Bug 35302675 (HCC): Nudges list missing accessible text.
  • Bug 37422211 (GHR): When adding a pending "Other communications details" entry is created and is pending approvals, the “Pending Approval” banner heading results in an error that required ARIA attributes must be provided.
  • Bug 37110884 (HCC): When creating a new row, there are missing labels on Grade Ladder page. Grade ladder search results for effective date, status and rate type require that elements with an ARIA role have parent roles.
  • Bug 36639417 (HCC): Screen reader reads a user's Talent Competency Evaluation graph point as if no rating is present, when a value is present.
  • Bug 37466797 (HCC): Redwood Calculate Payroll page contains search filter chips that contain elements with an ARIA role of listitem that require parent roles contain them.  Process and Person Message Text contains errors that the table/grid is missing accessible text.
  • Bug 37526471 (HCC): The Oracle Search filter chips on the Redwood Accounting Overhead Rules, Cost Processing Run Control, and Cost Component Mappings pages have a role of listitem although there is no parent of list defined.
  • Bug 37593769 (HCC): Secondary header with configurable attributes, such as person and assignment number, should be coded as a Heading and it’s not.  
  • Bug 36897239 (HCC): On Redwood Current Timecard and Time Totals, when CSS is turned off for use with screen reader, it doesn't represent the table's column and row and data cell detail semantically from an information and relationship perspective.
  • Bug 37443845 (GHR): HCM Approvals in progress reflect a heading without an associated level number.
  • Bug 36471803 (HCC), 36492724: On My Team Activity Center and other pages with search filter chips, a screen reader is reading out incorrect ("Press delete to remove") message when focus is on the filter chip. 
  • Bug 35379675 (HCC), 35894519: On My Learning page, a screen reader is reading LOV items twice listed in all filter chips combo box in the Redwood Learner search.
  • Bug 37081402 (HCC): A screen reader displays the button names for the search filters on responsive Workforce Health and Safety Incidents page multiple times. For example, the button label for Location search filter is set multiple times and repeats multiple times, i.e., "LocationLocation Location Button". Same filter label issue for Target Completion Date, Level of Severity, Event Type, Status, and When Incident Was Reported?
  • Bug 37343751 (HCC): On responsive Personal Info, Onboarding, Checklist Tasks, Roles, Delegations, Account Management, and Time and Absences pages, a screen reader announces the button labels multiple times when users land on the page and focus is automatically set to the 'Back' icon.
  • Bug 36541239 (WDM): Missing header on Notes section.
  • Bug 37465228 (HCC): Screen reader reads the item that is in focus, then the other form elements in the fragments used in Requisition, Campaign, Event creation compact guided process pages.
  • Bug 37194338 (HCC): On Redwood My Team Learning Filters side panel drawer, a screen reader reads filters names from beginning after a value is selected from LOV. After a value is selected, it should just read the selected value.
  • Bug 37026707 (HCC): In My Learning, because the visible label is missing ‘Suggested Filter Chip’ a user cannot select the filter chip using speech recognition software.
1.3.2 Meaningful Sequence(Level A)Partially Supports

The product was tested for:

  • The sequence of elements in the DOM matches a logical reading sequence.

Exception:

  • Bug 37132273 (HCC): When a Manager is adding a goal, the presentation of the panel drawer appears at the top of the body and that seems to override the initial linear page sequence. "Add Goal" drawer items are listed before the main content of the page which is not meaningful to users.
1.3.3 Sensory Characteristics(Level A)Supports

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 included a reference to the text alternative of the graphic.
1.3.4 Orientation (Level AA)Supports

The product was tested for

  • Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)Supports

The product was tested for:

  • There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)Partially Supports

The product was tested for:

  • Information is not conveyed using color.

Exceptions:

  • Bug 37490737(HCC), 36911909(HCC): On Redwood Check-in Document color is the only distinguishing factor indicating that the "Name" cell value is a link to select an employee.
  • Bug 36690390 (HCC): On the Timecard entry, color is the only indicator of meaning on the timecard tables, i.e. a blue triangle is a comment whilst a red triangle is an error.
1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports

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.
1.4.4 Resize text(Level AA)Supports

The product was tested for:

  • Text can be resized up to 200% without loss of content or functionality.
1.4.5 Images of Text(Level AA)Supports

The product was tested for:

  • Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential.
1.4.10 Reflow (Level AA)Not Supported

The product and documentation were tested for

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

Exceptions:

  • Bug 31089292: When Redwood pages are not enabled and user interfaces are zoomed to 400%, users may need both scroll bars to view/navigate the complete screen.
  • Bug 37362677 (GHR), 37381553: When editing an attachment link from the Redwood Contact Info page, from the Other communication account section, when editing a value, there are multiple fields that run over the page to the right side, so content can be lost.  Additionally, the Save button is not visible when 400% zoom is enabled.
  • Bug 37270509 (HCC): Users are unable to view the Opportunity Marketplace Search Filter Chip options with the 'oj-hcm-search' component when zoom is set to 400%.
  • Bug 37009111 (HCC), 37227617: Opportunity Marketplace Manage Gigs start and end date Search Filter Chips don't allow users to see the full calendar when zoom is set to 400%.
  • Bug 35999374 (HCC): The next and previous icons are not visible when browser zooms to 400% on Redwood Browse Recommended tab under Learning's Recommended by colleagues, Recommendations by learning department, Topics popular in my role, and Recommendations for skills I'm developing sections.
  • Bug 35980673 (HCC), 37365505: After 250% zoom and above, Opportunity Marketplace's Gig Detail buttons are not visible.
1.4.11 Non-text Contrast (Level AA)Partially Supports

The product was tested for:

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

Exceptions:

  • Bug 34486278 (GHR), 34490331 (GHR): Color contrast is too low for documents of record search icon, and cog icons. 
  • Bug 36883333 (HCC): The table rows and border coloring on Redwood View Calculated Time doesn't meet contrast minimum.
1.4.12 Text Spacing (Level AA)Partially Supports

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.

Exceptions: 

  • Bug 34205928 (HCC): Some HCM pages, such as My Public Info, Personal Details, and Roles and Delegations, etc. cut off the heading, subsection heading, or search text gets cut off when users try to access the page with text spacing styles turned on.  Users with low vision, or users with learning impairments may find it difficult to read the text.
  • Bug 34988156 (GHR): Employee Document Delivery Preference H1 and H2 header text appears cut off horizontally.
1.4.13 Content on Hover or Focus (Level AA)Supports

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.
2.1.1 Keyboard(Level A)Partially Supports

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 37413766 (HCC): Screen reader user is not able to access the rich text editor on the Redwood Career and Performance > Goal page. Users can access the first rich text editor, but not the second rich text editor.
  • Bug 36769363 (HCC): In Redwood HCM Search component, on single press of escape button, a user is not coming out of input email text dialog field of the filter chip search. Two presses of escape button will close the email input field, however. 
  • Bug 36609528 (HCC): When using HCM search filter chips the screen reader says to "use arrow keys" which are not working to select the value. Instead, we have to use "enter key" to access filter options inside the filter chip selection.
  • Bug 36182028 (HCC): On the Redwood Opportunity Market's Submitted Applications Jobs page, focus shifts from the expand icon/inside row to the whole row itself. So, in order for a keyboard user to reach the "Schedule Interview" link, users have to press Function-F2 and then press Tab to reach it.
  • Bug 37158530 (HCC): On Redwood My Team's Request Feedback page, keyboard users are restricted since table cells cannot be tabbed to due to a tab index of -1 on the first cell in each row.
2.1.2 No Keyboard Trap (Level A)Supports

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.
2.1.4 Character Key Shortcuts (Level A)Supports

The product was tested for:

  • There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)Supports

The product was tested for:

  • Time limits in the product can be turned off before they are encountered.
  • Time limits in the product can be extended with at least 20 seconds warning up to 10 times.
  • Time limits are longer than 20 hours.
2.2.2 Pause, Stop, Hide (Level A)Supports

The product was tested for:

  • There is no moving, blinking or scrolling content.
2.3.1 Three Flashes or Below Threshold(Level A)Supports

The product was tested for:

  • No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
2.4.1 Bypass Blocks(Level A)Supports

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.
2.4.2 Page Titled(Level A)Supports

The product was tested for:

  • Pages have a meaningful title specified in the TITLE element.
2.4.3 Focus Order(Level A)Partially Supports

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 34490288: Inaccurate focus order with advanced search.
  • Bug 37418121 (HCC): Redwood Skills and Qualifications page has a focus issue when the expand section button is activated, the focus supposed to be on the +Add button. But the focus is directed to the next expand section button, if the section is empty otherwise, focus goes to the content of the section.
  • Bug 37257265 (HCC): On the Candidate Profile's Citizenship or National identifiers sections, when adding a new item, the cursor focus doesn't go to the first field of the new object's attributes. It skips to the next existing item in the list and the user has to move the cursor back to the attributes in the new row.
  • Bug 37148999 (HCC): On the Create Offer questionnaire page, if a keyboard user chooses tab once again and selects enter, then the toggle is changing but the control moves to the cancel button instead of staying on the toggle.
  • Bug 36745037 (HCC), 37485407, 37446545 (GHR): After editing the Redwood Personal Details, Person Addresses region, and Candidate Profile pages, the cursor focus is not returned to the expected place.
  • Bug 36951775 (HCC): On Redwood Job Application, a screen reader reads out the questions multiple times in the 'oj-hcm-questionnaire' component when a user moves focus, the question is read again. 
  • Bug 37296354 (GHR): When navigating or tabbing through My Activity Center, the cursor focus is not returned to the expected place. Users should only have to tab through interactive fields and not be forced to tab through non-interactive fields (like a read-only field). When tabbing from back button, the cursor moves to the Person Number value which is not interactable.
  • Bug 37295465 (GHR): Document Delivery Preferences cursor focus doesn't move as expected or is lost during navigation. 
2.4.4 Link Purpose (In Context)(Level A)Partially Supports

The product was tested for:

  • The text of links and their surrounding paragraph, list, table cell (with marked up table headers), is sufficient to describe their purpose.

Exceptions:

  • Bug 37135270 (HCC), 36977260: For a screen reader user in the Assigned to Me section on the Fusion home page, refer to the Things to Finish section and task cards contain links with text that is getting cropped. 
  • Bug 37021556 (HCC): On Team Activity Center and the Compensation tab is active, there is no label on the current salary link when there is no salary.
2.4.5 Multiple Ways(Level AA)Supports

The product was tested for:

  • Pages can be found using the provided "search" function.
  • Pages are fully inter-linked to each other.
2.4.6 Headings and Labels(Level AA)Partially Supports

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 35382870 (GHR): Hire and Add Pending Worker flows header 1 structure does not provide a label with discernible text describing the content of the respective sections for the addresses, passport info, drivers license, visas and permits.
  • Bug 35616968 (HCC): When using a button list on the Redwood Skills and Qualifications Page, a screen reader user isn't taken to the correct Add button for the corresponding section. Also screen reader cannot uniquely distinguish the "edit", show details, and expand/collapse buttons.
  • Bug 36920686 (HCC): On Redwood Learning page when searching by activity, because there are duplicate labels a user cannot hide/show details using speech recognition software.
  • Bug 37064008 (HCC): The label on  Go Back (<) button on My Activity Center page is not meaningful. 
  • Bug 37215384 (HCC): On Redwood Manager Evaluation of Workers page, when a screen reader user wants to access a button list to shortcut their navigation, the expand buttons are reflecting 'Show Details Button'; all with same label name.
2.4.7 Focus Visible(Level AA)Partially Supports

The product was tested for:

  • Visual indication of the location of the focus.

Exceptions:

  • Bug 36815010 (HCC): On Redwood Search Learning Enrollments page, when attempting to select the search field using the Dragon Voice dictation command: [click search learning enrollments], a user can't gain focus on the search edit box.
  • Bug 36637722 (HCC), 36648341: On the Redwood search for My Journeys, My Learning Experiences, and Change Manager flows when a filter chip is populated and it becomes white, then cursor focus is not shown. When this happens, there is no focus around the filter chip when the user tabs to it, so it's impossible to see where the focus is.
  • Bug 35619943 (HCC): Cursor focus isn't shown when the Document Records search filter chip contains a value.
  • Bug 36868024 (GHR): On Redwood Personal Info in the Document Records section, when a filter chip is populated and it becomes white, then focus is not shown.
2.4.11 Focus Not Obscured (Level AA)Supports

The product was tested for:

  • The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.
2.5.1 Pointer Gestures (Level A)Supports

The product was tested for:

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Supports

The product was tested for:

  • There are no single pointer operations.
2.5.3 Label in Name (Level A)Partially Supports

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:

  • Bug 36797000 (HCC): On the Redwood Add Check-in Document page, the filter search or field search LOVs, such as Job Name or Job Code don't contain the actual field label in the accessible name. A generic name, i.e., "Search field" is used instead.
  • Bug 37191876 (HCC): Redwood Manage Personal Contribution page contains elements with an ARIA role that require elements labelled through their content have visible text as part of their accessible name.
2.5.4 Motion Actuation (Level A)Supports

The product was tested for:

  • There are no functions that require motion of the device.
2.5.7 Dragging Movements (Level AA)Supports

The product was tested for:

  • All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.
2.5.8 Target Size (Minimum) (Level AA)Partially Supports

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.

Exception:

  • Bug 37025384 (HCC): Redwood viewing calculated timecards is difficult for voiceover users. The View Calculated Time page, there is a small vertical scroll bar to move info across, and this bar is too small of a target to use mouse grid on.
3.1.1 Language of Page(Level A)Supports

The product was tested for:

  • Properly set language attribute for each page.
3.1.2 Language of Parts(Level AA)Supports

The product was tested for:

  • Proper use of lang attribute for text passages that are in a different language than that of the page.
3.2.1 On Focus(Level A)Supports

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.
3.2.2 On Input(Level A)Supports

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.
3.2.3 Consistent Navigation(Level AA)Supports

The product was tested for:

  • There are no navigational mechanisms that are repeated.
3.2.4 Consistent Identification(Level AA)Supports

The product was tested for:

  • Images and controls are used and identified consistently throughout the product
3.2.6 Consistent Help (Level A)Partially Supports

The product was tested for:

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

Exclusion:

3.3.1 Error Identification(Level A)Partially Supports

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.

Exception:

  • Bug 37099758 (HCC): Error messages aren't clearly linked to the corresponding date field, such as appearing on the Redwood Team Time Cards.
3.3.2 Labels or Instructions (Level A)Partially Supports

The product was tested for:

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

Exceptions:

  • Bug 28830908 (GHR): Adding documents of record attachments with required fields results in an error.
  • Bug 34182693: Missing label for select or multi-select action checkboxes; this results in user not understanding the purpose of these checkboxes on the page. 
  • Bug 34486175 (GHR): Unclear functionality range specified. The functionality associated with the Documents of Record "Range (specify)" link present in the "Last Updated" section is unclear for screen reader users. 
  • Bug 36891071 (HCC): The search component in  Document Records or Change Assignment search components is missing a label.
  • Bug 36920862 (HCC): Check-in Document label is not meaningful.
3.3.3 Error Suggestion (Level AA)Supports

The product was tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

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.
3.3.7 Redundant Entry (Level A)Supports

The product was tested for:

  • Information previously entered by or provided to the user that is required to be entered again in the same process is available for the user to select.
3.3.8 Accessible Authentication (Minimum) (Level AA)Supports

The product was tested for:

  • The product supports copy and paste while authenticating.

  • Authentication does not rely upon a cognitive functional test.

4.1.1 Parsing(Level A)Not ApplicableThis criterion is considered as always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)Partially Supports

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

Exceptions:

  • Bug 32164294: The grid/table that is displayed in the popup when interacting with the drop-down (i.e., input search component) is not correctly identifying the data in the table. In addition, the location of the popup can be displayed out of the viewport and does not get focus. The issue occurs when editing/adding information to the personal information feature.
  • Bug 34520362 (WDM): ARIA roles are defined incorrectly under Managers and Directs section of My Public Info.
  • Bug 34486213 (GHR): Link states not defined in advanced search on Document Records, Directory and My Organization Chart.
  • Bug 37417279 (HCC): Redwood Document Records, including document type LOV, use the incorrect role usage.
  • Bug 37404000 (GHR): The table of historic changes on Redwood Employment Info has incorrect role usage.
  • Bug 36824868 (GHR): In the Redwood Termination flow, when assignment flexfield attribute “affordable hra offered” is incorrectly setting aria-readonly on a span.
  • Bug 37381094 (GHR): Screen reader can't read the Address page fragment when there are no values for certain fields.
  • Bug 37295465 (GHR): Document Delivery Preferences text fields are missing associated labels.
  • Bug 37448039 (HCC): Redwood Employment Info contains a table of historic changes that is represented as a grid which overrides the semantic list structure used. However, this grid structure uses the role="gridcell" to contain all the information within the whole grid row.
  • Bug 37383468 (HCC), 37426372: When screen reader user is adding a condition on the Condition Builder page fragment, the user is not reading that attributes are required. 
  • Bug 37157927 (HCC): On Redwood Manager Feedback landing page, ARIA attributes are invalid as a role has not been specified. This affects all filter chips. On the filter chip panel drawer, the modal does not have an accessible name and the aria-modal=true attribute is on the wrong element. On each attribute search, such as Job Code, the Search (magnifying glass) button does not have the relevant role or ARIA attributes. The aria-modal=true attribute is on the wrong element.
  • Bug 36433716 (HCC): In HCM Search component, the filter chips are not marked as buttons.
  • Bug 37133481 (HCC): On Redwood Hiring-> Job Requisitions and My Team Learning pages, for the Search filter chips, the labels are read multiple times with incorrect instructions to use arrow keys to go to next item, etc.
  • Bug 37121478 (HCC): On Redwood Recruiting Events list, and Candidate Profile, the Search component has incorrect attribute for its role and it requires a parent attribute.
  • Bug 37017493 (HCC): On Team Activity Center, on the HCM Search, when a screen reader user navigates forward to the Search box button (magnifying glass) is reading as  "group", but when we reverse tab to navigate backwards, it is reading correctly as "...Search button".
  • Bug 36920591 (HCC): From My Activity Center page, the screen reader doesn’t read the selected assignment name information when a user chooses a new assignment from the Multiple Assignments action menu. Role isn’t set correctly and needs alt-text.
  • Bug 36484541 (HCC): The notifications icon in the Opportunity Marketplace page header is announced as a link, but it should be a button with aria-haspopup='true'.
  • Bug 36851570 (HCC): In Redwood Purchase Order's Order Life Cycle tab, the schedules table contains input fields that do not have associated labels.
  • Bug 36851195 (HCC): On Purchase Order and Purchase Order History pages, links are not read correctly or duplicated when using a screen reader. 
  • Bug 36843972 (HCC): On Order History page, a screen reader repetitive ”Level 2 Submit” link list names.  The Expand/Collapse button names are not intuitive.
  • Bug 37474146 (HCC): The search lookup and search filters on the responsive Workforce Health and Safety Incidents landing page and the global searches for people and actions found at the top of the Create Incident and Create Projects pages, have ARIA roles with all required ARIA attributes.
  • Bug 37462861 (HCC): Mobile phone user is unable to select options using Redwood Search filter chip items using swipe. Also user is unable to close the expanded filters. This issue exists for all filter types.
  • Bug 37484912 (GHR): On the add document subpage, the drop-down results table should have a role of table or grid instead of application.
  • Bug 37484527 (GHR): On the Employment Info, the table of historic changes incorrectly uses the role="gridcell" to contain all the information within the whole grid row.
  • Bug 36968706 (HCC): Error in Opportunity Marketplace's Referred Candidates page related to 'aria-level' attribute in 'oj-hcm-expandable-list-view' component.
  • Bug 37355061 - Redwood Personal Info and Family and Emergency Contacts date picker dialog component doesn't have an accessible name.
  • Bug 37191876 (HCC):  Redwood Manage Personal Contribution page contains elements with an ARIA role that require child roles contain them. When adding a row,, the dialog is missing an accessible name.
  • Bug 36071751 (HCC) - Redwood Promote and Resign flow’s Salary compensation-related page flows contains navigation list that requires child roles.  The Salary Basis combobox is missing required ARIA attributes.
  • Bug 36530746 (HCC): Redwood Change Salary flow’s navigational area contains a tablist that requires child roles.
  • Bug 36668312 (HCC): On the Redwood Correct Termination the Info to Include, the Additional Assignment information card  contains nested controls. On the When and Why page, there's an error on the What are you Terminating field  is a div which incorrectly contains attribute aria-readonly.
  • Bug 36208519 (HCC): On the Redwood Create Work Relationship, the Info to Include page cards incorrectly have nested controls.
  • Bug 37313685 (HCC): Redwood search filter chip buttons should not be nested.
  • Bug 37238178 (HCC): Redwood Team Time cards and Existing Time Card pages, for the search component, the filter chip’s  close button is coded as an anchor link rather than a button.
  • Bug 36674646 (HCC): Redwood Recruiting's Detail tab page has oj-sp-information-organizer tab list which hasn’t defined any tabs as children. Also the Screening  tab has errors due to incorrectly use of ARIA level on a DIV.
  • Bug 35409875 (HCC): Redwood Add Position labels are not associated to form fields in dynamic form. 
  • Bug 37122420 (HCC): On the Redwood Learning Evaluation Process, fields are missing associated labels.
  • Bug 37112337 (HCC): When adding a rate to the Redwood Grade Ladder page, missing an associated label to input field in Rates table.
  • Bug 37580402 (HCC): The global search field on Fusion homepage is missing required ARIA attributes, and the Me, My Team, My Client Groups and other tabs have interactive controls nesting issues.
  •  Bug 36235611 (HCC): On the Digital Learning page, HCM Search filter for Skill Level dialog does not have a title/accessible name.
  • Bug 35931689 (HCC): Required ARIA parent role not present in HCM Search Filters on Areas of Responsibility person search, My Team Learning, Learning Instructors and Mass Processing pages.
  • Bug 36732649 (GHR): On the Document Records page, the From Date and Issued On date dialogs don’t have an accessible name.
  • Bug 36419081 (HCC): HCM Search filter chip (oj-sp-filter-chip) component has nested interactive controls.
  • Bug 36911369 (GHR): Document Record filter chip's clear functionality is labelled as a link but behaves like a button. The search and date picker LOVs don’t inform users that the search must be activated or that data entry is required. Filter chip role can be interpreted incorrectly.
4.1.3 Status Messages (Level AA)Supports

The product was tested for:

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

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria
Conformance Level
Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot ApplicableThe product is designed to be isolated from the underlying platform.
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

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.

Redwood "Frequently used keyboard controls" documentation can be found here: https://redwood.oracle.com/?pageId=CORE8675467956044C288A7E0B6428015E66&shell=guideline#CORE5A95061481E94E699EAE064E32C3854A.

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Product documentation is provided in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. 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.

back to top

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.