Open jukesie opened 5 years ago
Looking at form validation for the prototype, there is this issue asking about its inclusion in the Kit: https://github.com/alphagov/govuk-prototype-kit/issues/509 There is a comment that 'we need to show error messages for alpha assessment'. There is also a link to http://www.craigabbott.co.uk/validation-for-prototypes which questions what we are actualy testing, and that forcing specific errors is more useful from a UX perspective.
Multi-disciplinary team with design, development and content expertise building prototypes using the govuk prototype kit using and building upon established govuk design patterns with content being reviewed and brought in line with govuk standards.
Prototype 01 Release 1 - mostly lift and shift existing relevant content from existing service into govuk design patterns.
Added basic validation for missing fields in the forms, with error summary and messages as per GDS guidelines
Updated the initial breadcrumbs to remove them from the linear journeys re GDS breadcrumbs
Test using tabbed interface for Authorised Users. These fit the GDS description as they are people who use a service regularly, with specific requirements regarding the search results retreived.
Their need to perform tasks quickly may be greater than their need for simplicity of first-time use.
Trialling step-by-step pattern for lodgement of property data. Not sure this is a good fit for our purposes: Have almost 20 sections, with a target sudience of expert users.
To pass your alpha, beta, and live assessments you usually need to:
explain how your team has included designers, content designers and frontend developers
explain how the service has used the styles, components and patterns in the GOV.UK Design System or the GOV.UK frontend toolkit and elements