Skip to content

Commit f3e80a1

Browse files
committed
Update/correct 3.3.1 understanding
* change reference to "WCAG 2.0" to just "WCAG" * remove the now outdated "Currently, few technologies support this kind of programmatic information", as that's not true anymore * clarify that programmatic information is not covered by this SC, but that others like 4.1.2 apply * corrects link to error suggestion from "3.3.1" to "3.3.3" Closes #1797
1 parent c9e2cfc commit f3e80a1

File tree

1 file changed

+6
-10
lines changed

1 file changed

+6
-10
lines changed

understanding/20/error-identification.html

+6-10
Original file line numberDiff line numberDiff line change
@@ -16,12 +16,12 @@ <h2>Intent of Error Identification</h2>
1616
<p>The intent of this Success Criterion is to ensure that users are aware that an error
1717
has occurred and can determine what is wrong. The error message should be as specific
1818
as possible.
19-
In the case of an unsuccessful form submission, re-displaying the form and indicating
19+
In the case of an unsuccessful form submission, re-displaying the form and indicating
2020
the fields in error is insufficient for some users to perceive that an error has occurred.
2121
Screen reader users, for example, will not know there was an error until they encounter
2222
one of the indicators. They may abandon the form altogether before encountering the
23-
error indicator, thinking that the page simply is not functional. Per the definition in WCAG 2.0, an "input error" is information provided by the user
24-
that is not accepted. This includes:
23+
error indicator, thinking that the page simply is not functional. Per the definition in
24+
WCAG, an "input error" is information provided by the user that is not accepted. This includes:
2525
</p>
2626

2727
<ul>
@@ -72,19 +72,15 @@ <h2>Intent of Error Identification</h2>
7272
that user agents or assistive technologies can use to identify an error and provide
7373
error information to the user. For example, certain technologies can specify that
7474
the user's input must not fall outside a specific range, or that a form field is required.
75-
Currently, few technologies support this kind of programmatic information, but the
76-
Success Criterion does not require, nor prevent it.
77-
75+
This type of programmatic information is not required for this success criterion, but is covered
76+
by other criteria such as <a href="#name-role-value">4.1.2 Name, Role, Value</a>.
7877
</p>
7978

8079
<p>It is perfectly acceptable to indicate the error in other ways such as image, color
8180
etc, in addition to the text description.
82-
8381
</p>
8482

85-
<p>See also
86-
<a href="error-suggestion">3.3.1: Error Suggestion</a>.
87-
</p>
83+
<p>See also <a href="error-suggestion">3.3.3: Error Suggestion</a>.</p>
8884

8985

9086
</section>

0 commit comments

Comments
 (0)