Chapter: quality
Rule: acceptedInvalid
Spec: Invalid input accepted
A required field was blank, or a field held typed junk it should not accept (email without @, a non-date in type=date, pattern / min / max / length). Save still sent that value or left the page, and the field never showed an error.
Example: Name is required and empty, or email is asdf. After Save there is no aria-invalid, no visible {id}-error, and no HTML5 constraint error — and either a write carried that value or the form is gone. Empty required and typed junk are the same class. Not this: XSS/SQLi stored as ordinary text in a notes/name field with no crash and no injection; Save that stays put with no write and no error (silent Save, WCAG 3.3.1); the page crashing on that junk (Q-03); the server bouncing a write the UI allowed (Q-01).
This id is stable. Reports link here so T/V/Q classes do not shuffle when a soak ranks differently.