Rule n° 78 - If any data entered in the form are rejected, the reason(s) why are indicated to the user.

Goal

• Help users understand what is expected and, by doing so, facilitate their progression to the next step.
• Prevent user frustration in the face of mistakes for which they don’t have an immediate solution.
• Improve the accessibility of content for people with disabilities.

Implementation

For each field containing rejected data, indicate the nature of the error and provide correction help

• Either at the start of the form, in a list of incorrect fields;
• Or in the context of each field, as much as possible using itslabel label.

Control

For each form checked:

• Check for the various possible errors in each form - no input in a field, non-compliance with a requested or predictable format (format of email address, date, etc.), case sensitivity, etc.
• If the input is rejected, check that the nature of the error is specified to help in its correction, by one of the means indicated in the implementation paragraph.

By Opquast - Read the license

Business application and benefits

The rules should be applied to your projects from the design phase through to post-implementation , and they should be understood by all professionals with web and customer experience (CX) responsibilities: from strategy to operations, marketers to project managers, and editorial to technical staff. The benefits of using this ruleset are numerous, including improving customer satisfaction, web performance, and e-commerce, and expanding your client base, while also decreasing your errors and costs.

The objective of these rules and the Opquast community mission is ‘making the web better’ for your customers and for everyone! Opquast rules cover the key major areas of risk that can negatively affect website users such as privacy, ecodesign, accessibility and security.

Opquast training has already allowed over 11,000 web professionals to have their skills certified. Train your teams or your students, contact us