A form can refuse an empty field while accepting an inaccurate answer. Required-field checking and checking the truth of the information are different tasks.
The MDN required reference describes the attribute’s role in form validation for supported controls. The browser can enforce a presence condition without knowing whether a typed name or statement corresponds to reality.
Consider an invented registration form requiring a job title. Typing a fictional title may satisfy the basic field condition. Whether the application should verify it depends on the service and its legitimate needs, not on the presence of an asterisk.
For designers, label required fields plainly and ask only for information the process needs. Explain an accepted format where relevant. A user should not have to submit repeatedly to discover a hidden rule.
For server-side implementation, validate the received data according to the application’s requirements; browser behaviour is not the sole enforcement boundary. Keep presence, format and any substantive verification distinct in both code and error messages.
For users, a green check beside a field usually reports an interface condition, not an independent endorsement of its contents. Read the confirmation in the context of what the form can actually check.
Image: an editorial illustration, not a documentary photograph.