- Tell users in advance whether or not a field is required.
- Prevent mistakes before they are made.
- Improve the accessibility of content for people with disabilities.
Indicate that the entry is mandatory in the label associated with the field. If this indication is made with a symbol (an asterisk for example), an explanation of this symbol should come before the form.
For each form:
- Check that the label associated with each field indicates that it is mandatory, if necessary by checking, with a code inspector, that the information is indeed present in the
labelelement, in an
aria-labelattribute, or else that it is linked to the field via an
- Check that the fields with labels not specifying that they are mandatory are actually optional, by validating the form without completing these fields. If an error message indicates that they must be completed or if the form cannot be validated in this way, the best practice is not valid.
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.