Why does screen become disabled after validation is displayed in data portal with WAI ruleset enabled?
In one of our application portals, we have functionality to look up client requests. There is one required field in the lookup section that must display en error message to the user when not filled. To show this message, there is a property-set-message on click of the search button, since the required validation is not enforced on the portal when the button is clicked (It is enforced when you click in the field and click back out). When the WAI ruleset is NOT enabled, there is no issue when displaying the error, and user is able to freely click around the screen, say to log off. When the WAI ruleset IS enabled, the entire screen becomes disabled on display of the error message, and the user is forced to close the browser window since no other actions can be made on the screen. As an alternative, when a page-set-message is used instead, the screen does not become disabled. Can anyone tell me why this is happening with a property-set-message, and does anyone know how I can correct this behavior?
With PegaWAI 07-10-18 enabled, using PRPC 7.1.9.
No WAI ruleset enabled. User can still log off.
WAI ruleset enabled. Clicking log off does not show menu. Button clicks do not fire.
The issue you are describing will likely need a deep dive via an SR to understand what is going on. But I am curious, do you have client side validation turned off? Because I would have expected you to get a pop up warning you, when you left a required field.
Thanks for your reply Rett. The client side validation is enabled, and if you click in the field and back out, the validation is enforced, but if you click directly on the button once the screen loads the validation is not enforced. The business wants some kind of indication that the field is required.
Accessibility cases can become complex and often have a lot of subtleties that usually are better handled in an SR where we can take a deep dive and have screen shares as needed. I feel this is one of those cases. Let us know if you do end up creating one.
On the same lines, is it normal for a user to be presented with the "value cannot be blank" error until it is populated? On text fields, you see the error once and can move on after clicking ok, but for dropdowns and autocompletes, the error is displayed repeatedly until a user either click cancel or selects a value. Is there a reason why these controls behave differently?
Yes there is a reason. If we simply just add some red text client side, a visually impaired user would have no way of noticing that. So the design is to give you a prompt you have just left a required field and left it blank. Hitting OK will bring you back to the field to correct it. Cancel, will allow you to dismiss and move on if your intention was to just change a flow anyways, or something to that nature.
I don't see the inconsistency on all screens. I'm not sure if it is because the text field is displayed in a modal flow, or if it is because the property is pre-populated, and deleting the value from the field and clicking out has a different effect than being blank on load.