Skip to content

Conversation

mbgower
Copy link
Contributor

@mbgower mbgower commented Oct 17, 2025

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.

Copy link

netlify bot commented Oct 17, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit e20b5ba
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/68f267a7828e2200080690dc
😎 Deploy Preview https://deploy-preview-4694--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Adding second requested change in the document
<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.
</p>
<p>An "input error" is information provided by the user that is not accepted. This includes:</p>
<p>An "input error" is input data that has failed validation. This includes:</p>
Copy link
Contributor Author

@mbgower mbgower Oct 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<p>An "input error" is input data that has failed validation. This includes:</p>
<p>An "input error" is caused by information provided by the user that has failed validation. This includes:</p>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about >>An "input error" is caused by input data that has failed validation. This includes:<<

The data is not the error, but causes it. The data might have been entered by som tool or AI, not by the user.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can remove this sentence entirely, as the normative section already links to the definition: input error

IMO, we can remove enirely:

An "input error" is information provided by the user that is not accepted. This includes:

  • information that is required by the web page but omitted by the user, or
  • information that is provided by the user but that falls outside the required data format or allowed values.

And replace the sentence below:

For example:

with:

Examples of "input error" include:

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The task force was still in the process of debating the wording of the change at line 33. Note that the original suggested wording in the issue was:

An "input error" is input data that has failed validation for the application preventing access to further processing. This includes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Understanding SC 3.3.1:change wording to correctly capture what's in scope of SC 3.3.1 vs. 3.3.3

3 participants