Update error-identification.html #4694
Open
+4
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Adding second requested change in the document
mbgower
added
Editorial
Understanding
3.3.1 Error Identification
3.3.3 Error suggestion
and removed
3.3.3 Error suggestion
labels
mbgower
commented
Oct 17, 2025
mbgower
commented
Oct 17, 2025
mbgower
commented
Oct 17, 2025
mbgower
commented
Oct 17, 2025
Looked at on TF call
bruce-usab
approved these changes
Oct 31, 2025
Contributor
bruce-usab
left a comment
bruce-usab
left a comment
There was a problem hiding this comment.
Discussed on Backlog call 10/31. Here's the Preview Diff.
alastc
reviewed
Nov 7, 2025
| <a href="error-suggestion">3.3.3 Error Suggestion</a>. | ||
| The error must be indicated in <a>text</a>.</p> | ||
| <p>This SC requires that users be provided with information about the nature of the error, including the identity of the item in error. What the user should do to correct the item in error is covered by | ||
| <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 at the same time. For instance, "Please provide a valid email address" conveys that the email field is empty or invalid, and also how it can be fixed. |
Contributor
There was a problem hiding this comment.
Suggested change
| <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 at the same time. For instance, "Please provide a valid email address" conveys that the email field is empty or invalid, and also how it can be fixed. | |
| <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 at the same time. For instance, "Email is not valid" would pass SC 3.3.1, but "Please provide a valid email address in the format [email protected]" also conveys how it can be fixed and passes both. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #4675 by making suggested modifications clarifying the difference between Error Identification and Error Suggestions, and acknowledging that it's possible to meet both in one message.