3 ms·
> At which point do you announce the mistake to a screen reader? There is a standard for this: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/
by IshKebab 2y ago
> At which point do you announce the mistake to a screen reader?
There is a standard for this: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-invalid https://developer.mozilla.org/en-US/docs/Web/Accessibility/A...
But I would suggest just having the validation in addition to the current behaviour.
> Where do you shift focus?
You don't?
> There's so much research that shows the opposite.
There's research that shows that a "tomorrow" button is bad??
- petepete 2y ago> There's research that shows that a "tomorrow" button is bad?? That client side validation isn't always accessible. More info here: https://design-system.service.gov.uk/patterns/validation/ https://design-system.service.gov.uk/patterns/validation/
- IshKebab 2y agoThat page doesn't say that at all. In fact they even mention a character count component that gives instant feedback.
- petepete 2y agoIt does. > When to tell the user about validation errors > Do not validate when the user moves away from a field. Wait until they try to move to the next part of the service - usually by clicking the ‘continue’ or ‘submit’ button at the bottom of the page. Yeah the character count is a bit of a special case because reaching the limit without going over would be very inconvenient.