This is a DRAFT resource that supports Working Drafts of WCAG 3. Content in this resource is not mature and should not be considered authoritative. It may be changed, replaced or removed at any time.
🔙 WCAG 3.0 (Silver) Guidelines
Method: Instructions for completing tasks
Platform
- All desktop and mobile platforms
Technology
- Websites and applications, such as HTML, ARIA, and Javascript
- Native apps and applications, such as iOS, Android, MacOS, Windows, and Linux
- Documents, such as HTML, PDF, and word processing (for example, Word)
Summary
- Instructions help users enter and submit data.
- Instructions that include illustrative examples help users understand and follow data entry requirements when inputting data.
How it solves user need
- People need instructions for inputs that have data requirements.
- People benefit from instructions that are clear and easy to follow.
- People benefit from instructions that include examples that illustrate formatting requirements.
Outcome
This method supports the outcome Input instructions provided..
Detailed description
- Instructions: Provide instructions for any inputs that have data entry requirements, for example, password or format requirements.
- Clear words: Use clear words to explain data entry requirements.
- Examples: Include illustrative examples when appropriate for explaining data entry requirements, for example, Date (MM/YYYY).
Dependencies
To be determined.
The following examples illustrate some basic ways to provide instructions for inputs that have data entry requirements.
Providing simple instructions within labels
Simple instructions can be provided within an input label, for example, including “required” in the label of an input that must be completed:
Name (required):
Providing an example
In some cases, the best instruction is an example of data in the correct format, for example, including “joe@example.com” in the label to show the required email format:
Email (joe@example.com):
Providing detailed instructions
Some inputs require more detailed instructions that are clearly marked and defined, for example, providing detailed password requirements with a section heading and list of requirements:
Password Requirements
- At least 8 characters
- Uppercase and lowercase letters
- At least one number
- At least one special character
Atomic Tests
- Test Units: Each input.
- Unit Score: For each test unit, complete each of the following tests and sum the test credits to get the unit score.
Test that instructions are present
Test Procedure
- Identify inputs that only accept data in a given format.
- Check that the page or view provides details about the required format.
Expected Results
#2 is true.
Critical Error if #2 is false.
Test for clear words
Test Procedure
- Identify instructions.
- Check that the instructions use clear words.
Expected Results
#2 is true.
Test that illustrative examples are present
Test Procedure
- Identify instructions that would benefit from an illustrative example.
- Check that the instructions include an example of data in the required format.
Expected Results
#2 is true.
Exception: Password inputs due to other considerations, for example, security risk
Scoring
- Still to be developed. We will include this in a future working draft.
Holistic Tests
- Still to be developed. We will include this in a future working draft.
W3C Resources
- Easy Checks: Required fields and other instructions sections in Forms, labels, and errors
- WAI Tutorials: Overall Instructions and Inline Instructions in Form Instructions
Non-W3C Resources
- Still to be developed. We will include this in a future working draft.