Accessibility: Application Should Set Focus On Field Affected By Error Message

(Doc ID 2337255.1)

Last updated on FEBRUARY 28, 2018

Applies to:

Siebel eCommunications - Version 15.18 [IP2015] and later
Information in this document applies to any platform.



The following behavior was reported on IP15.18 version:

When an error message is triggered (vanilla or custom)
1. the user clicks a button to dismiss the popup
2. the focus of the application is on the element which triggered the error message, mostly a button
3. if there are several errors in different fields, only the first in sequence is shown, and after the correction the whole process repeats.



An user with vision impairment has difficulties to locate the field which caused the error and may need several attempts to correct more than one error. Therefore, it takes them longer to perform their tasks.
A different behavior was requested:



a. Create two accounts A & B
b. Set account A as parent account of B
c. Select A account, open the Parent field and set B as parent of A
d. Put the focus on another field of A account ( e.g set a status to Regular)
e. Step off the record and an error message occurs saying

Message from webpage
Parent account cannot also be a child of the account.(SBL-SIS-00130)


f. Pushed Ok on the popup error and the focus is on the Status field ( latest
field modified ) instead of the field that generated the error: the parent



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms