| Description | When survey is grouped by pages, validation could not pass, leading the participant to read a modal message explaining nature of errors encountered.
Modal window is not accessible, auxiliary devices such as screen readers are skipping it and reading the whole page from scratch. Instead of blocking form submission and only reading the alert warning. More, modal buttons are skipped also because not accessible.
Questions forms should implement browser's built-in HTML5 client side Validation Form's API by avoiding to submit the page if validation is unsuccessful.
https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation#using_built-in_form_validation |
|---|
| Steps To Reproduce | Steps to reproduce
- install latest 6.x
- create a survey with grouped questions (pages)
- set mandatory or validated questions
- test the page's submission by using a screen reader such as: NVDA, JAWS, Voiceover Apple, Windows assistant.
Expected result
- Page must not be reloaded if validation can't pass.
- Modal window's body text must have
role="alert" so that auxiliary screen readers are able to read the message when popping up.
- Modal window's button must be accessible buttons, not malformed links.
Actual result
Whenever you click "NEXT" button in page, the page is reloaded also if invalid data is submitted and the screen reader restarts reading it from scratch.
Modal window message is totally skipped by the reader because is missing accessibility attributes: "role=alert" and WAI-ARIA attributes.
Modal window html source is situated at the end of html-body, can't be seen.
Additional notes
If you decide to not alter the functional logic, and keep a reloading page also while missing validation, is ok. But modal window must be removed and alert message should be put inline, >before< the form, without a modal interface but inside the page. Having accessibility attributes mentioned before. |
|---|
