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.

Sign up for GitHub

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

Jump to bottom

Admin: Form error validation not spoken to screen reader users, errors not spoken when tabbing to invalid inputs. #607

Open
9 of 10 tasks
JohnHewittCriterion opened this issue Mar 15, 2018 · 0 comments
Open
9 of 10 tasks

Admin: Form error validation not spoken to screen reader users, errors not spoken when tabbing to invalid inputs. #607

JohnHewittCriterion opened this issue Mar 15, 2018 · 0 comments
Assignees
@sethalt
Labels
508
Milestone
Sprint 12

Comments

@JohnHewittCriterion
Copy link

JohnHewittCriterion commented Mar 15, 2018 •
edited by sadlerw
Loading

Notes

The form errors are not spoken on invalid input focus. The invalid state is not spoken either. If there are 3 errors for an input then all 3 must be connected to the input. This is true for all the inputs not just the date shown below.

Use aria-invalid and aria-describedby http://pauljadam.com/csunmobile/form-aria.html

image.png

Linkage: CTF-87
WCAG: 3.3.1 Error Identification

Acceptance criteria

  • all inputs correctly labelledby for errors

Tasks

  • analyze why afs.readerror isn't working (seth)
  • fix issue (seth)

Definition of Done

  • Code unit / e2e tested and comply with QWASP
  • No new security vulnerabilities
  • Internal team code review
  • Documentation / readme.md / CircleCI updated
  • Docker updated
  • Compare finished design with mockup
  • Usability tested
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sethalt sethalt

Labels
508
Projects
None yet
Milestone
Sprint 12
Development

No branches or pull requests
3 participants
@sadlerw @sethalt @JohnHewittCriterion