Checklist "Transaction"

Note: To collect evidence related to this checklist use the Excel file: Evidence collection from the Checklist “Transaction” (xlsx, 86KB)

Requirements to be met:

1.1 The sequence of tabulation between fields follows the filling sequence

The order of tabulation between the fields must correspond to the normal sequence of filling of the form.

1.2 Forms with more than 2 screen heights should be distributed over several pages

Forms should not be presented excessively long. Forms that occupy more than 2 screen heights should be distributed over as many screens as necessary to comply with this rule. Long forms can also have several delayed interaction moments, requesting the user the absolutely necessary information at each stage, as opposed to requesting all the necessary information at an early interaction moment.

1.3 Forms with more than one page have the sequence of steps illustrated

The forms distributed over several pages should indicate at the top of the page the sequence of steps necessary to complete them, together with the designation of each step. The user must be able to select the previous steps to return to the respective screens and, if necessary, correct information.

2.1 The size of the fields should reflect the predictable size of the data

The size of the fields should reflect the predictable size for data entry. For example, a telephone field should be as wide as necessary to contain all digits. No more, no less.

2.2 Progressive disclosure is used instead of inactive fields

Instead of showing inactive fields, the form should hide the fields dependent on the key field whenever it has not been activated. When you activate the key field, you see the fields that depend on the condition defined in it.

2.3 The captions of the fields are brief and clear

The captions associated with the fields should be clear and as brief as possible, without resorting to major explanations. If such explanations are necessary, they should be presented in a parallel text block.

2.4 Mandatory fields must be clearly indicated as such

Identification should not be based solely on colour. The visual identification signage should be noticeable. An alternative equivalent compatible with the assistive technologies used by users with special needs should be made available.

3.1 In long actions, the system should indicate what is happening

The system should indicate what it is processing or what time it expects when the user triggers actions that lead to this behaviour.

3.2 The success of the transaction/sending of information must be confirmed

The success of a transaction must be clearly communicated to the user through a confirmation message.

4.1 It must be possible to correct information already entered at any time

All information already entered by the user in a session can be corrected at any time before the transaction is finalized.

4.2 Destructive actions should never be permanent; it should always be possible to undo the operation

The user must be able to recover from any action he/she has taken during the session.

4.3 Error messages are clearly identified next to the source fields

Error messages must be clearly presented in connection with the fields to which they relate. This does not detract from the need to present them in a summary list. This last technique is particularly useful on long pages.

4.4 Error messages should show the concrete steps to solve them

Error messages should be clear and succinct, not unnecessarily exposing the user to internal system mechanisms, and clearly explaining the steps needed for the user to solve the problem.