search

Energy-Saving-Trust / Design-System

A library of reusable components, patterns, and examples that embrace modern product design practices. Additionally, a collection of in-house standards, guidelines, and principles for creating inclusive, user-friendly, and effective products and services.
https://design-system-test-preview.pages.dev
1 stars 0 forks source link

DS Feedback - Stephanie - (not actionable yet) #91

Open elisa-est opened 4 days ago

elisa-est commented 4 days ago

Noting this here for now, then we will separate these out into separate issues.

  1. Browser support – do we / should we specify anywhere what browsers we support?
  2. Session management – do we have a standard session length? Could be important where the user is inputting a lot of data or might pop off halfway through to count their energy saving lightbulbs
  3. Validation behaviour – do we validate field by field, or less frequently (maybe based on clicking a CTA, or session length)
  4. Validation errors – could we be a bit more specific about how validation errors should be presented? E.g. we should avoid that irritating thing where you get a generic “there is an error message” when you click Submit, but no information about which input you got wrong.
  5. Special characters – another massive PITA for me. Do we have any restrictions around special characters (if not, we probably should) and if so, how do we inform the user. This really should be one for developers to address.
  6. Address entry – my preference would always be to nudge the user towards the address finder, rather than entering addresses manually.
  7. Date picker – if we have to have one, that’s probably the best one. Worth considering whether we’d ever need to validate two related dates e.g. one has to be before or after the other, or must be within a date range – if so the validation (and validation errors) need to be quite specific
  8. Location – are we ever bothered about the user’s location, and if so, how do we determine it?
  9. Uniqueness – another one for the development team, but we should have a standard way of determining uniqueness for – at least – a user / contact, and a property.
  10. Wizards – would a wizard component be useful for some of those long forms?
elisa-est commented 4 days ago

@EST-Karol and @lynsiepatient fyi these are the points Stephanie brought up when she reviewed the Design System.