- From: Shawn Henry <shawn@w3.org>
- Date: Thu, 18 Jun 2020 22:03:55 -0500
- To: OPERA <opera@kent.ac.uk>
- Cc: "wai-eo-editors@w3.org" <wai-eo-editors@w3.org>
Hi Nik, Thank you for your feedback on the tutorial. The tutorials include good practice beyond the WCAG requirements. The relevant WCAG requirements and techniques are at the bottom of the page: https://www.w3.org/WAI/tutorials/forms/notifications/#related If you would like to get more perspectives on this issue, you are welcome to send it to the W3C WAI Interest Group (IG) discussion list where issues of digital accessibility are discussed. You can search the mailing list archives, to get a feel for the list, through: http://lists.w3.org/Archives/Public/w3c-wai-ig/ You can join the mailing list and post questions by following the instructions about the Discussion List under: https://www.w3.org/WAI/about/groups/waiig/#mailinglist Kind regards, ~ Shawn <http://www.w3.org/People/Shawn/> On 17-Jun-20 5:10 AM, OPERA wrote: > Hi > > I've been reading over the excellent guide on User notifications with forms <https://www.w3.org/WAI/tutorials/forms/notifications/>. > > I have a question on where the documentation mentions that: > "In addition to overall feedback, more specific feedback at or near the form controls can better help users to use your form. This includes feedback to indicate correctly entered input as well as errors in the input." > > From the content on the page, it appears that providing inline feedback is best practice. I was wondering, if there are specific WCAG criteria that states that it is bad practice to load a separate page to provide users with feedback (ie that they have submitted an incorrect entry on a form)? If so could this be referenced on the guidance please? > > I am auditing a website to feedback to the developer and hopefully they will make required edits and will refer them to the guidance. If there is specific WCAG violations then hopefully the developer will prioritise these. I think their site needs a lot of work - it has the form's errror message on a separate page and worse still, the error message uses a <tr> tag 🙁 > > Thanks for your advice. > > Kind regards, > > Nik > > Project Opera - Accessibility at Kent > University of Kent > Room GG3B > Keynes College > Canterbury > Kent > CT2 7NP > > Kent Inclusive Practices (KIPS) <https://www.kent.ac.uk/studentsupport/accessibility/inclusive-practice.html> > Accessibility at Kent <https://www.kent.ac.uk/studentsupport/accessibility/> > Productivity Tools <https://www.kent.ac.uk/studentsupport/accessibility/productivity/index.html> >
Received on Friday, 19 June 2020 03:01:40 UTC