#108443Modal alert for required fields doesn’t name the affected field or tab
Description
*Description*
The modal alert shown for missing required fields is too generic: it does not mention the specific field nor its tab. With multiple errors, neither the count nor an overview is provided, making corrections cumbersome.
- Open a backend form with at least one required field.
- Leave at least one required field empty.
- Trigger “Save.”
- Observe the modal alert: message is generic, without field/tab names.
- Increased time to fix, as users must search for the failing field.
- Risk of incomplete or incorrect data remaining.
- Poor UX, especially in forms with many tabs/fields.
- Extend the validation collector to gather context: for each failing required field, determine field label and tab label.
- Message logic:
> * Exactly one error → include field and tab by name in the modal.
> * Multiple errors → include the error count n and optionally provide a list/link to an error overview.
- For a single error, the modal names the exact field label and tab.
- For multiple errors, the count n is shown; optionally provide a list or navigation hint.
- Saving with exactly one empty required field shows: “Please correct the required field ‘{FieldLabel}’ in tab ‘{TabName}’.”
- Saving with multiple empty required fields shows: “There are n required fields incomplete.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[BUGFIX] Modal alert for required fields doesn’t name the affected field or tab Resolves: #108443 Releases: main
Files 2
History 5
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2025-12-09T15:45:10+00:00" > 12/09/25, 15:45 </span> -
Anonymous commented and changed attached input-error-keyboard.mov <span data-processor="relativetime" data-value="2025-12-10T11:38:26+00:00" > 12/10/25, 11:38 </span>
Garvin Hicking wrote in #note-1:
> Did you notice the “(i)” button on the top right?For context: I’m a colleague of Christian. We are processing findings from an accessibility audit.
In the given context, the error response in the dialog is the primary feedback and fails the WCAG Success Criterion 3.3.1 Error Identification:
“If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.“
https://www.w3.org/TR/WCAG22/#error-identification> Clicking on it shows a list of all failed validations and clicking on an item jumps to the field…?
Viewing the list of errors needs prior additional interaction because it is hidden in a disclosure widget, and to get there, users need to discover it and depend on visual clues that are spread over large area of the graphical user interface. That is a significant problem for users of assistive technology like magnifiers, let alone screen readers.
Even once this behaviour is known to returning users, that disclosure widget opens a cascade of keyboard problems due to missing focus management. When the popup is closed, the focus is automatically set on the body element of the main window’s document object. That is expected browser behaviour when a fragment that contains the last known focus is hidden or removed.
I have attached a screencast showing the keyboard behaviour for the heading component, with additional watch expressions for the focussed element in the main window and the editor window. Focussing that (i)-button after closing the popup requires 20+ tab stops. After opening the popover with the list of anchors, it would take another 20+ tab stops to focus the anchor that leads to the invalid input element. With the keyboard, that element was already manually focussed halfway.
Without big architectural impact, a simple solution would be to display at least the first error that is now hidden in the disclosure widget in the dialog itself. Upon activation, the dialog should be programmatically closed and the form control focussed. That would solve both the identification and the keyboard problem.
A better solution would probably be to remove the dialog altogether, and immediately show the list of errors at the start of the form, first anchor focussed programmatically. This is also a very common pattern.
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-12-10T16:06:36+00:00" > 12/10/25, 16:06 </span>
Hi Nevin,
thanks so much for getting back to this quickly and explaining the background and details. I was already feeling this would be an a11y report related issue.
Will there be more/further issues from you concerning the report? It would surely make sense to combine the efforts. Also the GSB team is working on a11y reports and we should pool resources about this to effectively address solutions. (edit: I recognized you’re from Adesso, so propably this already is part of this effort, so sorry if I triaged an issue that was on other people’s radar).
As you’ve outlined, the changes need to be seen in a bigger picture and scope of our backend UI refresh, so this is a very good time to be addressed.
It is not my personal area of expertise, but I’ve reached out to a core team member for awareness, so that we can address it.
Best regards,
Garvin -
Anonymous commented <span data-processor="relativetime" data-value="2025-12-12T13:53:42+00:00" > 12/12/25, 13:53 </span>
Garvin Hicking wrote in #note-3:
> Will there be more/further issues from you concerning the report? It would surely make sense to combine the efforts. Also the GSB team is working on a11y reports and we should pool resources about this to effectively address solutions. (edit: I recognized you’re from Adesso, so propably this already is part of this effort, so sorry if I triaged an issue that was on other people’s radar).Cheers Garvin. There will definitely be more issues, I’ve also joined the Slack today. :)
-
Jennifer Geiß commented <span data-processor="relativetime" data-value="2026-06-17T11:45:33+00:00" > 06/17/26, 11:45 </span>
Hi,
I’m working on a few accessibility issues in the GSB context together with Christian (who originally raised the ticket).
Is any further feedback needed here?
Did you notice the “(i)” button on the top right? Clicking on it shows a list of all failed validations and clicking on an item jumps to the field…?