How to make a great government website

Post by petepete » Tue, Jun 04, 2024, 11:03 PM UTC

IshKebab wrote: post #63

petepete wrote: post #23

Earlier quoted context omitted.

> It would be much better if a tiny bit of JavaScript told you as soon as you put the date in, and if it had a "tomorrow" button, which would also require some JavaScript. There's so much research that shows the opposite. You might prefer that but government websites need to work for everyone, and showing validation messages automatically confuses less technically able people, and it's really hard to make it fully ac…

> 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/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??

Post by IshKebab » Wed, Jun 05, 2024, 6:50 AM UTC

petepete wrote: post #71

IshKebab wrote: post #63

Earlier quoted context omitted.

> 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/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??

> 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/