title: How should error messages should be handled for screen readers?
body: <p>I am working on some accessibility testing. On the site, they have a registration form and use form validation techniques. Error text is shown under the form fields where the data inserted within the form field is invalid. Currently the error text appears on the fly and not on the form submission. As you tab through the form, errors appear.</p>
  
  <p>By design, the form submit button is not visible until the form field data is valid. So doing an error check on form submission is not currently possible.</p>
  
  <p>What is considered "best practice" in this situation? I feel they need to change the way this form is designed to meet WCAG.</p>
  
  <p>There seems little point in using aria-describedby on the field and associated with the error message as the by the time the error appears, the user has moved to a new field. Should they be looking to show the submit button and then in turn allow the errors to be announced when the form submission fails? Or is there another issue with error text changing on the screen with no changes alerting the screen reader?</p>