I think it's very good because it would finally solve this old problem. I only wonder if it is technically possible, because the HTML specification specifies something else and in my opinion the HTML specification and this specification would contradict each other.

Update:

Chromium browsers have implemented this change and now the invalid state is not announced until a user has entered an invalid value to a field.

Safari on macOS also does not announce the invalid state with an untouched field. Safari doesn't announce a field as invalid when it has an incorrect entry - there is a browser form message that appears that indicates the incorrect entry, but the field itself does not expose an aria-invalid=true.

Firefox announces an untouched required field as invalid.

thanks @cookiecrook. i pulled in your suggestion and also broke the paragraph into two parts.

this pr should pull in the work steve started in #395

edit: no, that should be its own PR still.

per the approving review and the fact the chrome bug has been marked as fixed, i'm merging this PR.