diff --git a/app/views/design-system/patterns/charts.html b/app/views/design-system/patterns/charts.html index f078583c..5830fc20 100644 --- a/app/views/design-system/patterns/charts.html +++ b/app/views/design-system/patterns/charts.html @@ -33,6 +33,10 @@ Select a school +
{{description}}
+ +You can create a questionnaire as part of a service or campaign website to help users understand:
+ +You cannot use this pattern to:
+ +Whilst there’s no limit on the number of questions or answers you can create, it is recommended to use no more than 10 questions. Anything more complex may meet user needs better if designed as a service.
+ +With this pattern you can:
+ +The user is asked a question and based on their answer they are then:
+ +The user is asked a question and based on their answer they are then:
+ +It uses the existing question components from the GOV.UK design system.
+ +Here's an example of how this pattern works. Links on the results pages are broken to avoid any impact to the live service.
+ +There is full guidance on ‘Get to an answer’ for how to do this.
+ +By default, all questionnaires use DfE styling.
+ +Do not change the visual style unless there’s a clear user or business need. You may cause accessibility issues by customising styles.
+ +If you need to customise the visual style, for example to match campaign branding, you can change colours and add a decorative image (generic images which do not give any additional information to the content). Any change must still meet accessibility standards which includes testing colour contrast against WCAG levels.
+ +To use ‘Get to an answer’ you must:
+ +To create a questionnaire, sign in to ‘Get to an answer’.
+ +For more detail on how to set up your questionnaire read the guidance in the ‘Support’ section.
+ +Before a questionnaire can be made live you will need to complete all the steps in the ‘Prepare to publish questionnaire’ section.
+ +The technical documentation for ‘Get to an answer’ provides further information on how the component works.
+ +If you would like to develop additional functionality to meet your service’s requirements, we encourage teams to build on this pattern. For example, you might need more complex question logic.
+ +If you would like to propose a change, you can:
+ +