Julia Zakrocka WCAG 2.1 – Criterion 3.3.3 – Error Suggestion (Level AA)
- Przejdź do artykułów z tagiem A11Y
- Przejdź do artykułów z tagiem accessibility
- Przejdź do artykułów z tagiem accessibilityMatters
- Przejdź do artykułów z tagiem WCAG
- Przejdź do artykułów z tagiem WCAG 2.1
- Przejdź do artykułów z tagiem Web Content Accessibility Guidelines
Article content
We all like to know when we’ve made a mistake, right? Well, maybe not all of us… Ideally, it’s best not to make them, but since they happen, it’s nice to know how to correct them.
WCAG 3.3.3 Error Suggestion
This is where the WCAG 3.3.3 Error Suggestion criterion (level AA) helps us. It applies to forms and error messages, which should be sufficient enough so that our User knows what needs to be corrected or what issues were missed.
What should we NOT do?
- Write very general error messages – “This field is required.” Great, but what now?
- Describe what will happen after completing the form field – “You will receive a verification code on this phone number.” We have other tools, like labels and instructions (WCAG 3.3.2).
What are sufficient error correction suggestions?
Here are a few examples:
- “The email address is invalid. Example of a valid format: example@email.com”;
- “The password is too short, use at least 8 characters”;
- “The postal code should contain 5 digits and be in the format XX-XXX.”
Remember that the error message should be appropriately linked to the specific form field so that users using assistive technology know where the error occurred and can conveniently navigate to it. There are a few techniques in this area. If you’d like to read more, we invite you to check out the article that expands on the topic of WCAG 3.3.3 Error Suggestion.
Piotr Źrołka
Accessibility expert & CEO
Recommended articles
-
14.03.2023UX / UIHow to write in plain language?
Not without reason, plain language is an integral part of UX writing. Are you creating content for your website, writing…
-
14.01.2023AccessibilityWCAG 2.1 – Criterion 1.1.1 – Text Alternatives (Level A)
New year – new step! We’re starting a weekly Friday series “Understanding Digital Accessibility Based on WCAG 2.1”. WCAG is…
-
03.04.2023AccessibilityWCAG 2.1 – Criterion 1.3.1 – Information and Relationships: (Level A) Part 3
It’s Friday so let’s start with our schedule! Another WCAG-related post – the third part of criterion 1.3.1! Speaking of…