Cookie banner

[JamesR-CA]

Cookie banner

Please provide a summary / description of the component, including its purpose and where it is/might be used.

Cookie banner to be used on other web based products and services. At the moment there is a 'passive' cookie banner - which I assume works that cookies will be dropped and there is no-way to opt out.

It would be good to know:
• what our DPO guidance is around the use of cookies for: non-logged in and logged in users
• how this works with partner organisations using products and services such as the inward referrals project (currently in QA)
• what our DPO guidance is around the use of cookie management by users depending on the above
• the ability to effectively manage cookie customisation depending on product or service
• is there a need for cross-domain tracking or cross-domain log-ins

Please provide as much detail as you can. If you have any documents or evidence you want to submit, you can attach them to this issue.

I only link to the GDS as a reference to see how far/close our approach would be - and the level of work needed to design, test, develop this type of component.

The design system working group is here to support you through the contribution process - to help them, please consider the following:

• does your component need to be used by other products or services?
• yes, this could be used by the Referrals products that are being developed. Could be developed to offer a consistent cookie experience across platforms
• does something similar already exist in the design system
• no
• is there a product team that would perform the research, design, development and QA work associate with building this component?
• a use case can be the Referrals team product as well as potentially the Public Site (?) - again I think the approach will depend on above points
• do you have any user stories / scenarios that describe the component?
• no - has work been done on this previously?

Existing components

If your proposed feature exists in a product already, and you would like it to be included in the design system, please consider the following and ensure you have completed as much of the following as you can.

Code

• provide a link to your component working in a dev or prod environment
• provide links to the code for this component

Usability

• have you tested the component with the intended user group? Please include any links to research documentation in your proposal

Accessibility

• have you ensured your component meets WCAG 2.X AA guidelines? Include test protocols from external audits or notes from internal tests
• have you tested your component with a screen reader?
• have you tested your component by using only the keyboard to interact with it?

Quality

• provide links to any appropriate automated tests you have written
  • unit tests
  • behavioural tests
  • visual regression tests