Manager checklist
The following checklist is intended to guide managers on the review of FORM
accessibility. It should be used during the review phase to ensure compliance of all FORM
s on the site.
Level A
Coding
- FRM_A1:
Is the
FORM
element only used forFORM
s (i.e. the entire page is not wrapped in aFORM
element)?- FRM_A2i:
Is the content of all
FORM
fields (e.g. dropdown selection lists) provided as text (i.e. ASCII characters are not used to represent text)?- FRM_A2ii:
Is the content of all
FORM
fieldLABEL
s provided as text (i.e. ASCII characters are not used to represent text)?- FRM_A3:
Do all
FORM
elements remain visible when images are disabled?- FRM_A4i:
Do all
FORM
image buttons have anALT
attribute?- FRM_A4ii:
Are all
FORM
image buttonALT
attributes correct?- FRM_A5:
Is the
FORM
buttonVALUE
correct (i.e. theVALUE
must not be empty)?- FRM_A6i:
Have all mandatory fields been marked appropriately?
- FRM_A6ii:
Has the definition of mandatory fields been provided?
- FRM_A6iii:
Is the definition of mandatory fields provided prior to the start of the
FORM
?- FRM_A7i:
Is a valid error message displayed on submission of an empty
FORM
(i.e. no data has been entered)?- FRM_A7ii:
Is a valid error message displayed on submission of an invalid
FORM
(i.e. incorrect data has been entered)?- FRM_A7iii:
Are error messages only available to the user after the
FORM
has been submitted (i.e. error messages are not available when style sheets are disabled prior toFORM
submission)?- FRM_A8:
Are error messages included within the relevant field
LABEL
element?- FRM_A9:
Are error messages descriptive?
Error Messages
Meaningful Sequence
- FRM_A10:
If layout tables have been used, does the
FORM
have a meaningful sequence (i.e. theFORM
content makes sense when reading left to right, top to bottom through the layout table cells)?- FRM_A11:
Is the visual and source order in the correct reading sequence in the
FORM
?- FRM_A12:
Is all important in
FORM
ation placed before the start of theFORM
?- FRM_A13:
Do
FORM
results display before the start of theFORM
?
Keyboard
- FRM_A14:
Can the entire
FORM
be successfully navigated top to bottom using the keyboard (i.e. theFORM
does not contain a keyboard trap)?- FRM_A15:
Are all features of the
FORM
keyboard accessible?- FRM_A16i:
Does the presentation of all
FORM
fields change appropriately on keyboard focus?- FRM_A16ii:
Does the presentation of all
FORM
buttons change appropriately on keyboard focus?
Field LABEL
s
- FRM_A17i:
Do all fields have a
LABEL
?- FRM_A17ii:
Are all field
LABEL
s visible (date fields excepted see also FRM_20i, ii)?- FRM_A17iii:
Are all field
LABEL
s coded withLABEL FOR
andID
?- FRM_A18i:
Are
FORM
fieldLABEL
elements correct (i.e. does the fieldLABEL
element contain the entire text of theLABEL
)?- FRM_A18ii:
Are all
FORM
LABEL
elements associated with aFORM
field (i.e. there are no orphanedLABEL
elements)?- FRM_A18iii:
Does each
FORM
field have a single, unique fieldLABEL
element associated with it?- FRM_A19:
Are sets of related fields grouped with the
FIELDSET
andLEGEND
elements?- FRM_A20i:
Are date fields (e.g. day, month, year) coded using the TITLE attribute?
- FRM_A20ii:
Are date fields grouped with the
FIELDSET
andLEGEND
elements?- FRM_A21i:
Are related radio buttons grouped with the
FIELDSET
andLEGEND
elements?- FRM_A21ii:
Are related checkboxes grouped with the
FIELDSET
andLEGEND
elements?- FRM_A22i:
Does the
FIELDSET
element have aLEGEND
?- FRM_A22ii:
Is the
LEGEND
element coded immediately after theFIELDSET
element?- FRM_A22iii:
Is the
FIELDSET
LEGEND
concise (i.e. less than 100 characters)?- FRM_A23i:
Do any JavaScript
FORM
features have an accessibleALT
ernative available when JavaScript is disabled?- FRM_A23ii:
Are any JavaScript
FORM
features that do not require anALT
ernative hidden when JavaScript is disabled?- FRM_A23iii:
Are placeholding characters in
FORM
fields removed when JavaScript is disabled?- FRM_A24:
Are users warned of any unusual behaviour before inputting content into a component?
- FRM_A25:
Are there no changes in context or content on focus (i.e. a change in context or content does not occur on focus or exit of a field)?
- FRM_A26:
Are there no changes in context on input (i.e. a change in context does not occur on input of a field)?
- FRM_A27:
Are changes in content on input only after the current focus?
- FRM_A28i:
Can the
FORM
be submitted when JavaScript is disabled?- FRM_A28ii:
Is any correct data retained when an incorrect
FORM
is submitted when JavaScript is disabled?- FRM_A29i:
Are errors identified with JavaScript disabled?
- FRM_A29ii:
Are errors identified appropriately with JavaScript disabled?
- FRM_A30:
Does
FORM
content remain unchanged when style sheets are disabled (i.e. extraneous content does not appear when style sheets are disabled)?- FRM_A31:
Does the visual order of the
FORM
match the order of the content when style sheets are disabled?
Fieldsets
JavaScript
Style Sheets
Level AA
Navigation
- FRM_AA1:
Has a search feature been provided?
Meaningful Sequence
- FRM_AA2:
Are all
FORM
submission pages styled consistently?
Keyboard
- FRM_AA3i:
Do all
FORM
fields have a highly visible keyboard focus indicator?- FRM_AA3ii:
Do all
FORM
buttons have a highly visible keyboard focus indicator?
Error Messages
- FRM_AA4:
Do financial transactions meet at least one of the following criteria? reversible (FRM_AA4i); checked (FRM_AA4ii) or confirmed (FRM_AA4iii).
- FRM_AA4i:
Are any financial transactions reversible (i.e.
FORM
submission can be reversed)?- FRM_AA4ii:
Are any financial transactions checked (i.e. data entered is checked for errors and the user is allowed to correct the errors)?
- FRM_AA4iii:
Are any financial transactions confirmed (i.e. a mechanism is available for reviewing, confirming, and correcting in
FORM
action before finalizing the submission)?- FRM_AA5:
Does the modification of user-controllable data meet at least one of the following criteria? reversible (FRM_AA5i); checked (FRM_AA5ii) or confirmed (FRM_AA5iii).
- FRM_AA5i:
Is the modification of user-controllable data reversible (i.e. can changes be reversed)?
- FRM_AA5ii:
Can the modification of user-controllable data be checked (i.e. data entered is checked for errors and the user is allowed to correct the errors)?
- FRM_AA5iii:
Can the modification of user-controllable data be confirmed (i.e. a mechanism is available for reviewing, confirming, and correcting in
FORM
ation before finalizing the submission)?- FRM_AA6:
Do legal transactions meet at least one of the following criteria? reversible (FRM_AA6i);checked (FRM_AA6ii) orconfirmed (FRM_AA6iii).
- FRM_AA6i:
Are any legal transactions reversible (i.e.
FORM
submission can be reversed)?- FRM_AA6ii:
Are any legal transactions checked (i.e. data entered is checked for errors and the user is allowed to correct the errors)?
- FRM_AA6iii:
Are any legal transactions confirmed (i.e. a mechanism is available for reviewing, confirming, and correcting in
FORM
ation before finalizing the submission)?- FRM_AA7:
Do error messages include suggestions?
- FRM_AA8:
Are field error correction suggestions only provided after the
FORM
is submitted (i.e. error messages are not available when style sheets are disabled prior toFORM
submission)?- FRM_AA9:
Are field error suggestions included in the field
LABEL
element?