Skip to content

Review: 3.3.3 Error Suggestion (AA) #84

@qbalsdon

Description

@qbalsdon

Task: Edit MCAG section 3.3.3 considering the mobile research questions (to be completed)


If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

Sufficient Techniques for Success Criterion 3.3.3

Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Situation A: If a mandatory field contains no information:

G83: Providing text descriptions to identify required fields that were not completed
ARIA2: Identifying a required field with the aria-required property
[PDF5: Indicating required form controls in PDF forms ](https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF5.html)

Situation B: If information for a field is required to be in a specific data format:

ARIA18: Using aria-alertdialog to Identify Errors
G85: Providing a text description when user input falls outside the required format or values
G177: Providing suggested correction text
SCR18: Providing client-side validation and alert
SCR32: Providing client-side validation and adding error text via the DOM
[PDF22: Indicating when user input falls outside the required format or values in PDF forms ](https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF22.html)

Situation C: Information provided by the user is required to be one of a limited set of values:

ARIA18: Using aria-alertdialog to Identify Errors
G84: Providing a text description when the user provides information that is not in the list of allowed values
G177: Providing suggested correction text
SCR18: Providing client-side validation and alert
SCR32: Providing client-side validation and adding error text via the DOM
[PDF22: Indicating when user input falls outside the required format or values in PDF forms ](https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF22.html)

Advisory Techniques for Success Criterion 3.3.3

G139: Creating a mechanism that allows users to jump to errors
G199: Providing success feedback when data is submitted successfully

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions