Skip to content
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.

Test for WCAG success criterion 3.3.3: Error suggestion #244

Open
hannolans opened this issue Jun 25, 2014 · 0 comments
Open

Test for WCAG success criterion 3.3.3: Error suggestion #244

hannolans opened this issue Jun 25, 2014 · 0 comments

Comments

@hannolans
Copy link
Contributor

http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-suggestions.html

Applicability

FORM
Containing

  • Required fields
  • Field that requires specific data formats
  • Field with limited set of values

Not applicable

FORM

  • without required fields, fields that requires specific data formats and fields with limited set of values
    i.e. search form
  • when error suggestion jeoparize security

Techniques

Required fields

G83: Providing text descriptions to identify required fields that were not completed
ARIA2: Identifying a required field with the aria-required property

Field that requires specific data formats

ARIA18: Using aria-alertdialog to Identify Errors (ARIA)
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 (Scripting)
SCR32: Providing client-side validation and adding error text via the DOM (Scripting)

Field with limited set of values

ARIA18: Using aria-alertdialog to Identify Errors (ARIA)
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 (Scripting)
SCR32: Providing client-side validation and adding error text via the DOM (Scripting)

QUAIL

For each form we need to do a submit and check the results.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants