Skip to content
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

Input: Form field errors are not associated with their corresponding field #4830

Closed
sjasaniel opened this issue Feb 10, 2021 · 2 comments · Fixed by #4869
Closed

Input: Form field errors are not associated with their corresponding field #4830

sjasaniel opened this issue Feb 10, 2021 · 2 comments · Fixed by #4869
Assignees
Labels
focus: accessibility Main focus is for accessibility priority: high team: landmark For Landmark issues type: bug 🐛 [3] Velocity rating (Fibonacci)

Comments

@sjasaniel
Copy link

Describe the bug
Error messages are not associated with inputs. Screen reader users may not be able to identify the relationships between inputs and error messages.

Expected behavior
Developers should provide a programmatic association between inputs and error messages. This can be done using the aria-described attribute on the input, referencing the ID of the error message.
Note: adding aria-invalid="true" to inputs with errors will further aid screen reader users in completing forms and correcting their errors.

[Compliant Code Sample]

<label for="nationality">
<input aria-describedby="nationality-error" aria-invalid="true" type="text" id="nationality">
<div id="nationality-error">Field Nationality is required</div>

Version
IDS Enterprise Components - v4.36.2

Platform
Infor Application/Team Name: Landmark Client
Device: (if applicable) : N\A
OS Version: Windows 10
Browser Name: Chrome
Browser Version: 88.0.4324.146 (Official Build) (64-bit)

Additional context
https://jira.lawson.com/browse/LMCLIENT-34281

@tmcconechy tmcconechy added [3] Velocity rating (Fibonacci) focus: accessibility Main focus is for accessibility priority: high team: landmark For Landmark issues type: bug 🐛 labels Feb 10, 2021
@tmcconechy tmcconechy added this to To do in Enterprise 4.38.x (Feb 2021) Sprint via automation Feb 10, 2021
@tmcconechy tmcconechy changed the title Form field errors are not associated with their corresponding field Input: Form field errors are not associated with their corresponding field Feb 10, 2021
@tmcconechy
Copy link
Member

How are you guys attaching these errors - i would make sure you not doing something custom. And that it works like either this:

https://master-enterprise.demo.design.infor.com/components/validation/example-index.html
or this
https://master-enterprise.demo.design.infor.com/components/validation/test-message-types.html (i think its this)

@tmcconechy tmcconechy moved this from To do to In progress in Enterprise 4.38.x (Feb 2021) Sprint Feb 22, 2021
@tmcconechy tmcconechy self-assigned this Feb 22, 2021
@tmcconechy tmcconechy moved this from In progress to Pending Review in Enterprise 4.38.x (Feb 2021) Sprint Feb 22, 2021
@tmcconechy tmcconechy moved this from Pending Review to Ready for QA (beta) in Enterprise 4.38.x (Feb 2021) Sprint Feb 23, 2021
@CindyMercadoReyes
Copy link
Collaborator

This issue is now resolved.

@CindyMercadoReyes CindyMercadoReyes moved this from Ready for QA (beta) to Done in Enterprise 4.38.x (Feb 2021) Sprint Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
focus: accessibility Main focus is for accessibility priority: high team: landmark For Landmark issues type: bug 🐛 [3] Velocity rating (Fibonacci)
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants