-
-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
script to navigate between form invalid fields. #14311
Comments
what an awesome idea!!! |
I think you should add it as an add on, since then various changes could be
debated, and then if it was considered a success it will be put into core. I
agree this problem seems to be rife. There are actually a number of problems
with form fields though, mostly bad authoring on applications forms etc. Its
very easy to put no data in one then wonder why you get bounced back.
Brian
…--
***@***.***
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
***@***.***, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "David CM" ***@***.***>
To: "nvaccess/nvda" ***@***.***>
Cc: "Subscribed" ***@***.***>
Sent: Friday, October 28, 2022 9:03 PM
Subject: [nvaccess/nvda] script to navigate between form invalid fields.
(Issue #14311)
### Is your feature request related to a problem? Please describe.
Is not exactly a problem, but is related with the usability. When filling
out a form, Currently the only way to navigate between invalid fields is
by listening to each field to see which one says invalid. This can be very
tedious when filling out forms with many fields.
### Describe the solution you'd like
I suggest to implement a command to quickly navigate between invalid
entries in a form. I think it would help users a lot.
As a software developer, when we've implemented a quick way to navigate
between invalid entries has resulted in a very pleasant user experience.
But developers shouldn't implement alternative ways to identify invalid
fields if HTML5 already offers that feature natively.
So, I suggest to implement it on the core of NVDA. A gesture should be
assigned because this would be very useful for NVDA users
I know that many developers do not implement the validation attribute
correctly. But this could change if users who use assistive technologies
start to make more use of that feature.
This should work in browse mode only. We would need to think in a good
gesture to assign.
### Describe alternatives you've considered
I thought of using NVDA's search function. But that only works when the
form displays some searchable symbol. Normally, there is no alternative
but to go through the form fields one by one.
Currently, I made a personal add-on to implement the solution, but I
consider this feature too important to delegate it to an add-on.
--
Reply to this email directly or view it on GitHub:
#14311
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
To do this, we expect adding a new type of entry to the elements list and scripts to jump to next and previous invalid field. I'd recommend leaving these scripts without a bound gesture initially. |
feerrenrut
added
p4
https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
feature
triaged
Has been triaged, issue is waiting for implementation.
labels
Nov 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Is not exactly a problem, but is related with the usability. When filling out a form, Currently the only way to navigate between invalid fields is by listening to each field to see which one says invalid. This can be very tedious when filling out forms with many fields.
Describe the solution you'd like
I suggest to implement a command to quickly navigate between invalid entries in a form. I think it would help users a lot.
As a software developer, when we've implemented a quick way to navigate between invalid entries has resulted in a very pleasant user experience. But developers shouldn't implement alternative ways to identify invalid fields if HTML5 already offers that feature natively.
So, I suggest to implement it on the core of NVDA. A gesture should be assigned because this would be very useful for NVDA users
I know that many developers do not implement the validation attribute correctly. But this could change if users who use assistive technologies start to make more use of that feature.
This should work in browse mode only. We would need to think in a good gesture to assign.
Describe alternatives you've considered
I thought of using NVDA's search function. But that only works when the form displays some searchable symbol. Normally, there is no alternative but to go through the form fields one by one.
Currently, I made a personal add-on to implement the solution, but I consider this feature too important to delegate it to an add-on.
The text was updated successfully, but these errors were encountered: