Module 4: Checkpoint summary
All of the requirements and their conformance levels for this module are presented here. This summary can be used as a quick checklist for evaluating web pages.
Checkpoint 1 - Form controls
| Conformance: Mandatory |
Form controls must have explicitly associated labels.
Checkpoint 2 - Logical source order
| Conformance: Mandatory |
Form fields must use a logical source order to control tabbing.
Checkpoint 3 - User input validation
| Conformance: Mandatory |
Validation of user input must occur server-side.
Checkpoint 4 - Process completion
| Conformance: Mandatory |
Process completion must not rely on client-side scripting or embedded objects.
Checkpoint 5 - Usability testing
| Conformance: Mandatory |
Each new process must undergo usability testing ( http://www.qld.gov.au/web/cue/definitions#usabilitytesting ).
Checkpoint 6 - Opt-in
| Conformance: Mandatory |
Opt-in must be used over opt-out.
Checkpoint 7 - Primary actions
| Conformance: Mandatory |
Provide only one primary action per form.
Checkpoint 8 - Secondary actions
| Conformance: Desirable |
Clearly distinguish the primary action from secondary actions.
Checkpoint 9 - Terminology
| Conformance: Desirable |
Standardise terminology across action buttons and links within an application.
Checkpoint 10 - Mandatory fields
| Conformance: Mandatory |
Clearly label all mandatory fields with the required field indicator.
Checkpoint 11 - Field indicators
| Conformance: Desirable |
Required field indicators should be aligned in their own column.
Checkpoint 12 - Field notices
| Conformance: Mandatory |
Display a required field notice before any form fields.
Checkpoint 13 - Label placement
| Conformance: Mandatory |
Place form control labels and required field indicators consistently.
Checkpoint 14 - Personal information
| Conformance: Mandatory |
Remove optional form fields that collect personal information.
Checkpoint 15 - Optional form fields
| Conformance: Mandatory |
Reduce the number of optional form fields.
Checkpoint 16 - Content blocks
| Conformance: Mandatory |
Separate content blocks.
Checkpoint 17 - Placement of content blocks
| Conformance: Mandatory |
Placement of content blocks must be consistent throughout an application.
Checkpoint 18 - Content block titles
| Conformance: Desirable |
Content block titles should use consistent terminology.
Checkpoint 19 - Grouping information types
| Conformance: Mandatory |
Information types must be grouped together in a form.
Checkpoint 20 - Read-only data
| Conformance: Mandatory |
Form controls must not be used to display read-only data.
Checkpoint 21 - Progressive disclosure
| Conformance: Desirable |
Progressive disclosure should be used when appropriate.
Checkpoint 22 - Input error messages
| Conformance: Mandatory |
Input error messages must be clearly defined.
Checkpoint 23 - Form input
| Conformance: Mandatory |
Retain form input on error.
Checkpoint 24 - Incorrect form fields
| Conformance: Mandatory |
Highlight all incorrect form fields.
Checkpoint 25 - Standardise error messages
| Conformance: Mandatory |
Standardise error message placement and colour.
Checkpoint 26 - Placement of error messages
| Conformance: Desirable |
Input error messages should appear near the relevant form control.
Checkpoint 27 - Radio buttons
| Conformance: Mandatory |
Radio buttons must represent 'or' options.
Checkpoint 28 - Check boxes
| Conformance: Mandatory |
Check boxes must represent 'and' options.
Checkpoint 29 - Positioning of labels
| Conformance: Mandatory |
Labels must be positioned to the right of radio buttons and check boxes.
Checkpoint 30 - Radio button and check box options
| Conformance: Desirable |
Radio button and check box options should be presented vertically.
Checkpoint 31 - Horizontal presentations
| Conformance: Mandatory |
Horizontal presentations must avoid close proximity.
Checkpoint 32 - Radio button options
| Conformance: Desirable |
A maximum of six radio button options should be used per question.