search

w3c / wcag

Web Content Accessibility Guidelines
https://w3c.github.io/wcag/guidelines/22/
Other
1.14k stars 256 forks source link

"in text" vs "as text" 3.3.1 Error Identification #4068

Open jamieherrera opened 2 months ago

jamieherrera commented 2 months ago

Can 3.3.1 update the phrase "in text" to "as text"?

This phrasing is also probably used elsewhere. I looked for an open or closed ticket related to this but did not find this specific issue, thank you for humoring me:

3.3.1 SC reads, "If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text."

Intent for the Understanding document highlights "text" from "The error must be indicated in text." to define what "text" is, unrelated to its location.

In #1810 also about 3.3.1, @patrickhlauke mentions,

it's also the proximity here that counts. even if the error message was just "this field must not be empty", the fact that it's near it "indicates" that it refers to that. as in you don't necessarily need to make the error message make complete sense in utter isolation. still evaluating it in the context of where it is - "the item that is in error is identified (by having that error appear right after it)"

I agree that proximity to an error could contribute to the "which item is in error" part of Error Identification without necessarily needing explicit content to define a location. However, it should be more clear that "in text" does not require proximity.... or even that the error message be on the same page. I see that in 2.2 the Note was added that an alert or dialog can be used. In English, "in text" vs "as text" carry different meanings.

patrickhlauke commented 2 months ago

In English, "in text" vs "as text" carry different meanings.

and these different meanings are?

detlevhfischer commented 1 month ago

in text / as text:

To me, "in text" implies that the error identification bit might be contained somewhere in a larger chunk of text rather than presented as a stand-alone element (and this is actually the case in the situation where a list of errors is generated and displayed before the form). But it may even be a warning sign icon embeddded in a text string not focusing on the error (admittedly an edge case unlikely to happen) because it does not say the error is identified "as text".

The term "as text" makes it a bit clearer that there has to be real text identifying the error. The difference is minor, but I agree with @jamieherrera that "as text" would be the better choice.