Rule n° 71 - The user is warned whenever a field is case-sensitive.

Goal

• Prevent the risk of mistakes and, as a result, prevent the user from having to fill out the same field several times.
• Prevent confusion in users who think they correctly completed the field, but see it marked as an error.
• Improve the accessibility of content for people with disabilities.

Implementation

If the expected entry is case sensitive, specify in the label associated with the field that it must be done in upper or lower case, as appropriate.

Control

For each form

• Identify the fields whose input is case sensitive by entering the requested text in upper case then in lower case and check whether, in one of the two cases, the input is rejected.
• If the input is rejected because of its case, check that the label associated with each field, using the label element or in the aria-label attribute, informs the user of the case sensitivity.

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