[PP-1] Enable the Inline Form Errors module in the Standard profile and recipe

Certainly a plus one from me! I would even like IFE during install ;-)

This would be great to get into Core. I've tried this out on SimplyTest.me and it worked fine. Attached a couple screenshots so that there are some visuals to go along with the patch.

+1

Who else should look at it before it is RTBC'd?

Don't know Mike.

This is as straight forward as they get.

Nice idea. This would be good for the product team to review and sign off on.

Thanks folks!

@xjm pointed out that while #2504847: [meta] Roadmap for stabilizing Inline Form Errors module (IFE) is closed, there are some issues that were originally a requirement but not actually resolved. Particularly #2856950: Add a possibility to disable inline form errors for a complete form and even more so #2848507: Indicate that grouping elements have child element errors for ux and a11y. Without the later issue, fieldsets are quite broken. We can use this issue to track the remaining work needed to enable in the standard profile as well. Leaving the product manager tag on since other product managers could provide feedback on this well :)

Let's do this -- add those two issues to the summary and postone this one until they're ready?

Edit: Oops, missed the bit in #8 about leaving the tag on. But since we know those two issues are outstanding issues with having IFE as the default, let's have product manager review once they're fixed so that they'll be reviewing the final thing. :)

These two issues look reasonable postponement criteria. They are the only two outstanding should-haves from #2504847: [meta] Roadmap for stabilizing Inline Form Errors module (IFE).

A year has passed. What's the status of this?

#2856950: Add a possibility to disable inline form errors for a complete form landed. #2848507: Indicate that grouping elements have child element errors for ux and a11y is still in progress, and is blocked on review..

+1 on this. This came up in the Olivero issue queue #3154357: Enable Inline Form Errors module in install profile process.

Should this be closed due to #3159848: [Policy] Always install Drupal with Standard on the UI, pared down of use case specific elements (content types, node listing, commenting, theme)

Or postpone this also on #3159848: [Policy] Always install Drupal with Standard on the UI, pared down of use case specific elements (content types, node listing, commenting, theme), then repurpose this to enable IFE in the standard recipe?

Usability review

We discussed this issue at #3587931: Drupal Usability Meeting 2026-05-08. That issue will have a link to a recording of the meeting. The attendees at the usability meeting were: @benjifisher, @pallavi singh3013, and @rkoller.

We've briefly discussed the issue close to the end of the meeting. In short, the group had a clear consensus that it would be still desirable to get the Inline Form Errors module into the standard profile (or standard recipe). In regard to the question what is necessary before it could go in and how to move things forward, the most important issue that is still required to get fixed first, is the one this issue is postponed on: #2848507: Indicate that grouping elements have child element errors for ux and a11y. Aside that, it would be also good if the accessibility related issues that got raised and discussed in https://drupal.slack.com/archives/C2ANFUGGG/p1777902680634679 could get solved and the current state of the module reevaluated if there are more potential a11y related blockers. But in general it should be tried to get the "move the inline form errors module into the standard profile" endeavor moved forward - and we would try to help on that.

If you want more feedback from the usability team, a good way to reach out is in the #ux channel in Slack.

The Standard profile / recipe will still exist, just in a modified form. #3159848: [Policy] Always install Drupal with Standard on the UI, pared down of use case specific elements (content types, node listing, commenting, theme) is at Needs review, but IMO we can do this before that lands anyway.

Still, this is also waiting on #2848507: Indicate that grouping elements have child element errors for ux and a11y.

Very cool. We talked about this for most of the A11y Office Hours today.

I have updated the issue summary and tagged for product manager review.

I am adding this as a child of the issue that is reviewing Standard. While that is currently focused on removing extensions, it seems the best place to put this.

As discussed in Slack with @quietone

RE #27:

Aside that, it would be also good if the accessibility related issues that got raised and discussed in https://drupal.slack.com/archives/C2ANFUGGG/p1777902680634679 could get solved

I believe that's:

• #3557245: Use $element['#attributes]['id'] instead of $element['#id'] to create a link anchor (corresponding Slack message). IMO this is a blocker.

and the current state of the module reevaluated if there are more potential a11y related blockers.

There are a few a11y issues open.

Does the fact that the module has been marked as stable in core since 8.4.0 provide confidence that we can go by the current issue queue regarding blockers?

IMO #2848307: Inline errors not working on form table elements should also be a blocker.

I'm also curious if we can phase the outstanding issues in for beta1 vs rc1 vs final.

Something like:

Classify blockers for 11.5.0-beta1, blockers for 11.5.0-rc1, and blockers for 11.5.0.

Adding #3619127: Forms sidebar doesn't open with error links from Inline Form Errors module as blocker because of this from #3576488: [meta] Admin theme: path to beta and stable:

#3619127: Forms sidebar doesn't open with error links from Inline Form Errors module

1. There appears to be a dependency on the other issue that KentR is working on. Don’t feel this is a blocker since IFE is not enabled by default
2. [Mike G] I do see this as being a blocker if we want to have IFE in core and finally moving from an experimental module. Core is changing a lot though, so….
3. [Mike H] It’s a blocker for IFE in core, but not Admin theme being stable

Added blockers based on discussion with @mgifford.