Cookie banner #12
Cookie banner #12
Comments
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
Also: (how) is this different from the cookies link in the footer? |
I'm going to add this to my service. One question: should it say 'GOV.UK uses...' or 'Service name uses...' - I reckon the latter. It's the service setting the cookies, and the service's cookie policy you'll get to when you visit the link. |
Just to note that a version of this was added to |
@MalcolmVonMoJ Thanks for sharing. Just a comment on the mandatory cookies - I didn't understand the logic of accept mandatory cookies as a thing, but like what you have done. Hope your UR will explore the user journey between GOV.UK and Legal Aid and how users perceive the two banners. |
Mandatory cookies: my terminology for "strictly necessary cookies".
Our service uses some cookies that fall into this category, so if we offered a choice to reject all cookies, this would either be misleading or essentially stop them from using the service. We'd therefore need to rephrase it to something akin to "only accept strictly necessary cookies" or "reject all optional cookies". Various different ways of phrasing it but they are all a bit wordy. Anyway, user research continues... The journey from GOV.UK to the service is part of the research. |
Hi again. Also interested in your reasoning
Again, that would be great to explore in UR as there's been a lot of supposition around the need for a consistent pattern. (But may be there a consistently differentiated pattern??) |
@peter-jordan, I just realised I didn't answer you - or at least not here. Apologies. If I recall correctly, testing shewed that users could become exasperated when they had just accepted cookies on the GOV.UK page - perhaps the one with the Start button - but then are asked again when they enter the service. It was thought that a distinct pattern (from the main GOV.UK) would help them understand that the question was different, that we are asking for this service only and not the whole of GOV.UK. |
Quick response, as I'm not working this pm. I'd like a next week if poss. Monday? |
I am working from Tuesday next week. If you want to talk about our decisions, I should be able to find some time. Ordinarily, it would be wise to include our interaction designer as well, but unfortunately today is his last day for a fortnight. I'll see if I can get his thoughts on this and will post them here. |
Hey Malcolm. Any chance of a chat Tue pm or Wed am? I'm trying to pull together an idea of what different depts have been doing. |
@peter-jordan, yes, I should think so. How can I contact you? I have a few slots this afternoon, most of tomorrow before midday is free too. |
On ukgovernmentdigital.slack.com Slack @peterbjordan_gds ?? I'm free 15:00-17:30 today or 09:30-11:00 Wed |
For reference, this is what the “Find postgraduate teacher training” service did: |
Cheers @fofr |
@fofr Really useful and interesting to read that. I've also not seen a design history site like that before, great concept. (Reminds me of something in "The Design of Design" by Fred Brooks of keeping a diary of design decisions during a project, both for the project itself, and for others to learn from.) |
Cookie Banner UpdateThe GOV.UK team and the Design System are working together on testing and releasing an experimental iteration of the cookie banner. Objectives of the Cookie Banner
Actions
|
In July 2020 the GOV.UK programme in GDS conducted user research into the impact of displaying multiple cookie banners on GOV.UK within a single user session. They ran 5 60 minute, remote user research sessions. The participants varied in their levels of interest in online privacy. These are the banners they tested: The research found that:
|
For services where users have to be signed in via an account, I wonder whether it’s worth collecting analytics cookie consent via the sign up flow? Something like this (although perhaps the wording would change): The advantages would be that it avoids users having to repeatedly answer the same question on every new device or browser, and that the question would never conflict with other buttons or forms in the same page. There would also be more space to go into more detail about what kind of analytics are collected, how the data is anonymised, shared, etc, which might make the consent more "informed"? |
GOV.UK Design System working group review: Cookie banner componentRepresentatives from the GOV.UK Design System working group reviewed this contribution in December 2020. Based on a majority vote, the group decided that:
They also made the following recommendations. Guidance
Design
Code
Next stepsBased on this feedback, the GOV.UK Design System team have agreed to:
|
Release of cookie bannerThe cookie banner component has been published in the Design System. The cookie banner component allows users to accept or reject cookies which aren’t essential to making your service work. Problems to solveWe looked to:
What we decided and what has changedWe decided to:
How we went about building itWe:
AcknowledgementsThank you to everyone that contributed to this component, including Gavin Wye at GOV.UK and Frankie Roberto at the Department for Education, for their research, design and development How you can help our ongoing user researchShare your research or feedback by commenting on this issue or propose a change – read more about how to propose changes in GitHub |
Really great work on this – we will soon be AB testing a variety of cookie banner options on Teaching Vacancies at DfE and will make sure to feed back our findings as well. One thing I'm not sure I understand is why there is a version for "only essential cookies" at all – my understanding is that that negates the need for a cookie banner, and is something IMHO every service should strive for anyway because they're one of the worst things to ever happen the internet (but that's a personal opinion). See e.g. Github's move to eliminate non-essential cookies. Perhaps a wider piece of guidance for services around cookies and avoiding them may be helpful, as well as alternatives to serving the business need of gathering data and improving their service – but that's obviously a bit beyond the remit of the Design System! |
Could be. Users might still expect to see something telling them what the deal is with cookies, given that they frequently will on other sites. (I'm not familiar with any research on this, so I'm just speculating.) |
Accessibility of the GOV.UK Design System cookie bannerWe have a card to consider publishing some of these findings in the Design System guidance. What the GOV.UK Design System team did to improve the accessibility of the cookie banner
What we tested for
Issues we found in the first round of testing
Fixes we made before a second round of testingTo try and fix the above, we did the following:
Findings from the second round of testing
Feedback from the GDS accessibility clinic
Outcomes from the accessibility testing and related fixes
|
What
Help users manage their personal data by telling them when you store cookies on their device.
The text was updated successfully, but these errors were encountered: