4 ms·

Component under discussion: https://design-system.service.gov.uk/components/date-input/ https://design-system.service.gov.uk/components/date-input/ It is bad.

by Eduard 5y ago

Component under discussion: https://design-system.service.gov.uk/components/date-input/ https://design-system.service.gov.uk/components/date-input/ It is bad. Day month year are separate inputs. No auto-jump to next input. Even if this was done for accessibility reasons, it is not accessible for many on the a11y spectrum. Also, the component is half baked. How come one can input wrong input and there is no immediate error feedback? How come the error example still shows a validation error despite entering correct data?

pimlottc 5y ago
> It is bad. Day month year are separate inputs. No auto-jump to next input. Even if this was done for accessibility reasons, it is not accessible for many on the a11y spectrum. Auto-advancing is a non-standard behavior for input fields, it could easily be confusing for users who aren't expecting it. Behavior in auto-advancing fields can also be awkward when going back to edit values, or pasting. I also wouldn't be surprised if it was more difficult for a11y users with screen readers. Keep it simple. > Also, the component is half baked. How come one can input wrong input and there is no immediate error feedback? This is covered elsewhere under "Patterns / Validation" [0], they recommend delaying validation until the user attempts to move on to the next section or submit the form. > How come the error example still shows a validation error despite entering correct data? I'm not sure what you mean, both examples have clear explanations in the error message; the first example [1] indicates that the date must be in the past and the second [2] is missing the year. 0: https://design-system.service.gov.uk/patterns/validation/#when-to-tell-the-user-about-validation-errors https://design-system.service.gov.uk/patterns/validation/#wh... 1: https://design-system.service.gov.uk/components/date-input/error/index.html https://design-system.service.gov.uk/components/date-input/e... 2: https://design-system.service.gov.uk/components/date-input/error-single/index.html https://design-system.service.gov.uk/components/date-input/e...

by Eduard 5y ago

pimlottc 5y ago

> It is bad. Day month year are separate inputs. No auto-jump to next input. Even if this was done for accessibility reasons, it is not accessible for many on the a11y spectrum. Auto-advancing is a non-standard behavior for input fields, it could easily be confusing for users who aren't expecting it. Behavior in auto-advancing fields can also be awkward when going back to edit values, or pasting. I also wouldn't be surprised if it was more difficult for a11y users with screen readers. Keep it simple. > Also, the component is half baked. How come one can input wrong input and there is no immediate error feedback? This is covered elsewhere under "Patterns / Validation" [0], they recommend delaying validation until the user attempts to move on to the next section or submit the form. > How come the error example still shows a validation error despite entering correct data? I'm not sure what you mean, both examples have clear explanations in the error message; the first example [1] indicates that the date must be in the past and the second [2] is missing the year. 0: https://design-system.service.gov.uk/patterns/validation/#when-to-tell-the-user-about-validation-errors https://design-system.service.gov.uk/patterns/validation/#wh... 1: https://design-system.service.gov.uk/components/date-input/error/index.html https://design-system.service.gov.uk/components/date-input/e... 2: https://design-system.service.gov.uk/components/date-input/error-single/index.html https://design-system.service.gov.uk/components/date-input/e...