Table 2.

Semantic tags.

Tag	Description
Consistency and standards	All system providers throughout the design must adhere to a unified protocol by maintaining consistency in terminology, sequence of actions, and data localization.
Visibility of the system status	Users should be notified of ongoing processes via suitable alerts and feedback mechanisms.
Match between system and world	Users’ perceptions of the system should align with their mental models of how the system is expected to function.
Minimalist design	Any unnecessary information should be eliminated because it acts as a distraction and impedes efficiency.
Minimize memory load	Users should not be required to memorize extensive information to perform routine tasks.
Informative feedback	Users must receive informative feedback regarding their activities.
Flexibility and efficiency	The system should provide resiliency so that users can customize settings and expedite their tasks.
Good error messages	Messages should provide sufficient information for users to comprehend the nature of errors, learn from mistakes, and take corrective action.
Prevent errors	The design should deter errors by preventing incorrect actions.
Clear closure	Users must be explicitly informed when a task has been completed.
Reversible actions	Users should be allowed to recover from errors made by them.
Use user’s language	The system language must be comprehensible to the targeted users.
Users in control	Users should not feel in control of the system without encountering unforeseen circumstances.
Help and documentation	The system should offer various forms of help, such as contextual assistance, mission-focused guidance, and alphabetically organized (lexicographically arranged) help topics for easier navigation.