The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.

The design should speak the users' language. Use words, phrases, and concepts familiar to the user, rather than internal jargon.

Users often perform actions by mistake. They need a clearly marked "emergency exit" to leave the unwanted action without having to go through an extended process.

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.

Good error messages are important, but the best designs carefully prevent problems from occurring in the first place. Either eliminate error-prone conditions, or check for them and present users with a confirmation option before they commit to the action.

Minimize the user's memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another.

Shortcuts — hidden from novice users — may speed up the interaction for the expert user so that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

Interfaces should not contain information that is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility.

Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.

It’s best if the system doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks.

By adhering to Web Accessibility Standards, such as WCAG 2.1, designers can create inclusive experiences that benefit everyone.