RTC a11y NPM Resource Changed UI/UX PR-6.3-dev Pending

User tests: Successful: Unsuccessful:

avatar brianteeman
brianteeman
15 Oct 2026

Pull Request resolves #48616 #37889

  • I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

This is a draft - the idea is that it will list all fields that are invalid on submitting a form

I dont know if it catches all validations

If this is the correct approach then the next step is to ensure that you can click on the message to focus on the speciftic field (tricky with tab groups)

I have updated the js (with AI assistance) so that each of the listed invalid fields now indicates which tab the field is in and the list is now clickable to the exact field

An additional and final update from me is to highlight any tab that contains invalid fields - this is a visual only indicator so more of a UX improvement than accessibility

See #48616 for detailed proposal

@Fedik does this look like a good approach

@mbeganyi-a11y this should resolve a11y issues with form validation

Testing Instructions

this is a js change so either use a pre-built package or npm i

Submit any form in the Joomla admin without completing a required field - New User is a good one

Actual result BEFORE applying this Pull Request

image

Expected result AFTER applying this Pull Request

image

Link to documentations

Please select:

  • Documentation link for guide.joomla.org:

  • No documentation changes for guide.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

avatar brianteeman brianteeman - open - 15 Oct 2026
avatar brianteeman brianteeman - change - 15 Oct 2026
Status New ⇒ Pending
avatar joomla-cms-bot joomla-cms-bot - change - 15 Oct 2026
Category ⇒ JavaScript NPM Change
avatar Fedik
Fedik - comment - 15 Oct 2026

I think we had something like this in past already. But was removed at some point.

The approach look good, but we probably need to limit it for the backend or make it configurable.
I mean, we also have the message near the invalid field. And for a simple forms on the frontend it will lead to duplicated messages.

Maybe would be not a bad to use this approach to show only the fields which is hidden behind the tab or inside the accordion. But not sure. Just an idea.

In general the code look fine. Can be improved in few places. But we probably need to agree on approach first.

avatar mbeganyi-a11y
mbeganyi-a11y - comment - 15 Oct 2026

@brianteeman Thanks for tagging me here and for taking this on. This will help all users, as accessibility often does, so very cool!

I have tested and have two questions about the implementation, so please help me understand (as consistency across the entire Joomla platform is important, too):

  1. Does it make sense to move programmatic keyboard focus to the container of the error message upon submission instead of leaving focus on the triggering element? This way, keyboard users could press Tab to immediately get back into the form.
  2. Does the error message container require a "Close" button? Is there any harm in leaving the error permanently visible? It uses an aria-label and isn't particularly specific as it's simply conveyed as "Close" to assistive technology, so these users may not know exactly what they're closing.

I mean, we also have the message near the invalid field. And for a simple forms on the frontend it will lead to duplicated messages.

Yeah this is an interesting problem to solve. When using a screen reader and navigating away from the form field that's required but invalid, the invalid error message isn't conveyed, so that's tricky. Upstream error messaging is generally problematic, but duplicated messages are also frustrating.

avatar brianteeman
brianteeman - comment - 16 Oct 2026

I would not want to programtically change the focus on form submission to the first invalid field. On a simple form that might be ok but on a complex form I think you would end up confused why you are on that field and more importantly what the field is expecting.

As I stated this is an initial release and I would plan to make the list of fields links in the next iteration of this draft before making it a final pr

avatar brianteeman brianteeman - change - 16 Oct 2026
Labels Added: NPM Resource Changed PR-6.3-dev
avatar mbeganyi-a11y
mbeganyi-a11y - comment - 16 Oct 2026

I would not want to programtically change the focus on form submission to the first invalid field. On a simple form that might be ok but on a complex form I think you would end up confused why you are on that field and more importantly what the field is expecting.

Sorry if I wasn't clear. I didn't mean the first field in error, I meant the container that holds the error messaging. That way, when the list of fields in error within the container become links, keyboard users can tab to the list then activate, or move past the links into the form. Leaving focus on the triggering element adds a few extra Tab stops, that's all.

As I stated this is an initial release and I would plan to make the list of fields links in the next iteration of this draft before making it a final pr

Yep, that's cool; just throwing ideas around. Let me know if I can help with anything.

avatar brianteeman brianteeman - change - 22 Oct 2026
The description was changed
avatar brianteeman brianteeman - edited - 22 Oct 2026
avatar brianteeman
brianteeman - comment - 22 Oct 2026

I have updated the js (with AI assistance) so that each of the listed invalid fields now indicates which tab the field is in and the list is now clickable to the exact field
image

avatar mbeganyi-a11y
mbeganyi-a11y - comment - 22 Oct 2026

Nice work. Would you like me to take a look?

avatar brianteeman brianteeman - change - 22 Oct 2026
The description was changed
avatar brianteeman brianteeman - edited - 22 Oct 2026
avatar brianteeman
brianteeman - comment - 22 Oct 2026

An additional and final update from me is to highlight any tab that contains invalid fields - this is a visual only indicator so more of a UX improvement than accessibility

image

it is now ready for review and no longer a draft

avatar brianteeman
brianteeman - comment - 22 Oct 2026

@Fedik most of the JS is ai generated so I would really appreciate your skilled review of the js

avatar brianteeman brianteeman - change - 22 Oct 2026
The description was changed
avatar brianteeman brianteeman - edited - 22 Oct 2026
avatar brianteeman brianteeman - edited - 22 Oct 2026
avatar Fedik
Fedik - comment - 22 Oct 2026

In general looks not so bad :)

avatar richard67 richard67 - change - 27 Oct 2026
Title
…
[6.3]Improve form validation error messages [a11y] [ux]
[6.3] Improve form validation error messages [a11y] [ux]
avatar richard67 richard67 - edited - 27 Oct 2026
avatar brianteeman brianteeman - change - 28 Oct 2026
The description was changed
avatar brianteeman brianteeman - edited - 28 Oct 2026
avatar webnet-assmann webnet-assmann - test_item - 29 Oct 2026 - Tested successfully
avatar webnet-assmann
webnet-assmann - comment - 29 Oct 2026

I have tested this item ✅ successfully on 6397370


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48623.

avatar webnet-assmann
webnet-assmann - comment - 29 Oct 2026

I have tested this item ✅ successfully on 6397370


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48623.

avatar exlemor exlemor - test_item - 29 Oct 2026 - Tested successfully
avatar exlemor
exlemor - comment - 29 Oct 2026

I have tested this item ✅ successfully on 6397370

I have successfully tested this! Thanks @brianteeman. Nice User feedback improvement.

And it seems to fallback/trickle down nicely (fallback or trickle down is probably 'not' the right term but can't think of different ones):

If I put in:

1adfy824t$^)(%^ for Name and Login Name* and exlemor@ gmal.com for Email* (intentional space in the email), I get your

The form cannot be submitted as it's missing required data.
Please correct the marked fields and try again.
Account Details → Email

If I put in:

1adfy824t$^)(%^ for Name and Login Name* and exlemor@gmal.com for Email*, I get your

Save failed with the following error: Please enter a valid username. No space at beginning or end, at least 2 characters, must not have the following characters: < > \ " ' % ; ( ) & and be less than 150 characters long.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48623.
avatar exlemor
exlemor - comment - 29 Oct 2026

I have tested this item ✅ successfully on 6397370

I have successfully tested this! Thanks @brianteeman. Nice User feedback improvement.

And it seems to fallback/trickle down nicely (fallback or trickle down is probably 'not' the right term but can't think of different ones):

If I put in:

1adfy824t$^)(%^ for Name and Login Name* and exlemor@ gmal.com for Email* (intentional space in the email), I get your

The form cannot be submitted as it's missing required data.
Please correct the marked fields and try again.
Account Details → Email

If I put in:

1adfy824t$^)(%^ for Name and Login Name* and exlemor@gmal.com for Email*, I get your

Save failed with the following error: Please enter a valid username. No space at beginning or end, at least 2 characters, must not have the following characters: < > \ " ' % ; ( ) & and be less than 150 characters long.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48623.
avatar brianteeman
brianteeman - comment - 29 Oct 2026

That's because we have a mix of client and server side validation

avatar richard67 richard67 - change - 31 Oct 2026
Status Pending ⇒ Ready to Commit
avatar richard67
richard67 - comment - 31 Oct 2026

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48623.

avatar richard67
richard67 - comment - 31 Oct 2026

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48623.

avatar rdeutz rdeutz - change - 2 Nov 2026
Status Ready to Commit ⇒ Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 ⇒ 2026-11-02 14:15:55
Closed_By ⇒ rdeutz
Labels Added: RTC a11y UI/UX
avatar rdeutz rdeutz - close - 2 Nov 2026
avatar rdeutz rdeutz - merge - 2 Nov 2026
avatar brianteeman
brianteeman - comment - 2 Nov 2026

Thank you

Add a Comment

Login with GitHub to post a comment