- Reduce the risk of input errors.
- Reduce the risks associated with sending incorrect or unusable data.
- Prevent the user from giving up, for lack of information about the expected input.
- Improve the accessibility of content for people with disabilities.
Indicate what is the expected input format using the label associated with the field. For example:
<label for="mail">Email Address (of the type email@example.com)
For each form:
- Submit various possible errors in each form, for non-compliance with a requested or predictable format (format of email address, date, etc.), in order to detect the fields for which a specific input format is required.
- Check, using a code inspector, that the label associated with each relevant field indicates the expected format in the label element or by using an ARIA attribute.
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.