search

w3c / matf

Guidance from the Mobile Accessibility Task Force (MATF)
https://w3c.github.io/matf/
Other
8 stars 3 forks source link

Success Criterion 3.3.1 - Error Identification - Level A #44

Closed JJdeGroot closed 2 weeks ago

JJdeGroot commented 4 months ago

WCAG2ICT guidance: https://www.w3.org/TR/wcag2ict-22/#error-identification

Share your thoughts for applying to mobile apps as a comment below.

julianmka commented 2 months ago

Based on previous task force conversation, this SC can be applied to native mobile apps and mobile web with minimal or no deviation from WCAG2ICT.

Proposal

In MATF's first draft of guidance, this SC's section will read as:

This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.1.

Please indicate your agreement with a thumbs up emoji 👍, or if you disagree, use the thumbs down emoji 👎 and elaborate in comments.

jamieherrera commented 2 months ago

The Intent documentation does mention an error message could be in a dialog rather than on the same page as the error itself. I wonder if we should add a note that dialogs are common for native iOS and Android communication? My company had a conversation about whether dialogs were acceptable; people were getting snagged on the phrase "in text".

julianmka commented 2 months ago

I think that would be a good note to add, @jamieherrera, with the caveat that there does need to be some kind of inline indication of the error as well.

The pattern I usually recommend for screens with multiple validated inputs is to throw an alert dialogue with a more general message about the error(s) and then use an inline message to give details for each input with an error.

JJdeGroot commented 2 weeks ago

Closing this issue because the draft language has been accepted.