Accessibility Issue: Error Messages are not Properly Tagged for Screen Reader When Adding an Invalid Bank Routing Number on the Direct Deposit Request.
(Doc ID 3022765.1)
Last updated on MAY 29, 2024
Applies to:
PeopleSoft Enterprise CS Student Financials - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
When using JAWS Screen Reader for a sighted person, and an error message is returned from entering an incorrect routing number for the Direct Deposit Form via Fluid, the error is not read/announced to the User.
The expectation is that the error message should announce the error from the page to the User.
The issue can be reproduced at will with the following steps:
1. The user logged in with Screen Reader Mode Enabled using Jaws 2024.
2. If an invalid value is entered for the Routing Number, the error message on the page is not read/announced.
3. If a field is missed (or has a mismatched bank account) and click the submit button, the error message is not properly tagged to generate an announcement for the screen reader.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |