If "required" validation on a field without a #title fails, we display an error region with no message.
Submitting as critical because we just silently fail on a form submission which can give the impression the submission was successful to the end user.
To reproduce the problem,
/contact/feedback by default).When the page loads, even before you try to submit any form, you should see the empty error message.
Instead of using the Contact module, you could use a view with both page and block displays. Then add the block to the page created by the same view. There are alternative steps to reproduce in Comment #61.
The current behavior fails several WCAG requirements:
See Comments #62 and #64 for more information on these accessibility issues.
Display the ID of the form element as opposed to displaying nothing so it is clear that validation failed to developers (and end users - if developers don't find this bug in their own testing)
An error message now appears when validation fails:
or (with the inline_form_errors module enabled and the wording suggested in Comment #61)
N/A
N/A
Needs work
10.1 ✨
Last updated
After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.
Enhances developer experience.
There is consensus among core maintainers that this is a major issue. Only core committers should add this tag.
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.