Appropriate Feedback with Forms

This is a technique for testing:

WCAG 2.0:   Guideline 2.2 Enough Time: Provide users enough time to read and use content.  Understanding Guideline 2.2

2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A)

  • Turn off:The user is allowed to turn off the time limit before encountering it; or
  • Adjust:The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend:The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception:The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception:The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception:The time limit is longer than 20 hours. How to Meet 2.2.1 | Understanding 2.2.1

2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA) How to Meet 2.4.6 | Understanding 2.4.6
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) How to Meet 2.4.7 | Understanding 2.4.7
3.3.1 Error Identification: 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. (Level A) How to Meet 3.3.1 | Understanding 3.3.1
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) How to Meet 3.3.2 | Understanding 3.3.2
3.3.3 Error Suggestion: 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. (Level AA) How to Meet 3.3.3 | Understanding 3.3.3

Overview

Checking for labelling on forms has already been discussed but in this test we are checking to see what happens if someone does not complete the form or adds incorrect data such as text instead of numbers etc or does not have time to complete a form.  The latter tends to happen in timed tests or where there is a security issue.  The picture below shows helpful text based feedback when some fields were incomplete.


text version of form error

Method

Manual checks are almost the only way to see whether instructions or cues are provided appropriately when submitting a form or when errors have occurred.  The form elements are important as are the labels as mentioned in the labelling on forms web page.  Keyboard access is obviously essential at both the entry stage as well as at exit or submission.   When the error or submission message is returned, check that the focus for the keyboard access is immediately sent to the dialog box that appears or a text message is available at the start of a new page.  The content in both methods need to be understandable.  

audit form feedback


Use WebbIE or another text based browser or the Text-Only view in Webaim Wave toolbar to check whether labels are correct and linked to text input forms.  Use a screen reader to see that the controls and feedback makes sense.

Advice