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.
Form controls must have explicitly associated labels.
Form fields must use a logical source order to control tabbing.
Validation of user input must occur server-side.
Process completion must not rely on client-side scripting or embedded objects.
Each new process must undergo usability testing ( http://www.qld.gov.au/web/cue/definitions#usabilitytesting ).
Opt-in must be used over opt-out.
Provide only one primary action per form.
Clearly distinguish the primary action from secondary actions.
Standardise terminology across action buttons and links within an application.
Clearly label all mandatory fields with the required field indicator.
Required field indicators should be aligned in their own column.
Display a required field notice before any form fields.
Place form control labels and required field indicators consistently.
Remove optional form fields that collect personal information.
Reduce the number of optional form fields.
Separate content blocks.
Placement of content blocks must be consistent throughout an application.
Content block titles should use consistent terminology.
Information types must be grouped together in a form.
Form controls must not be used to display read-only data.
Progressive disclosure should be used when appropriate.
Input error messages must be clearly defined.
Retain form input on error.
Highlight all incorrect form fields.
Standardise error message placement and colour.
Input error messages should appear near the relevant form control.
Radio buttons must represent ‘or’ options.
Check boxes must represent ‘and’ options.
Labels must be positioned to the right of radio buttons and check boxes.
Radio button and check box options should be presented vertically.
(when horizontal presentations are used)
Horizontal presentations must avoid close proximity.
A maximum of six radio button options should be used per question.