Phase banner

[govuk-design-system]

Use this issue to discuss this component in the GOV.UK Design System.

[timpaul]

There's some evidence here from the GOV.UK Notify team that the beta banner can cause confusion and even put some people off using their service: alphagov/notifications-admin#1838

[36degrees]

Worth noting that they weren't using the beta banner, just the beta tag – as per the product page example.

A traditional beta banner might have been fine. It possibly is evidence that that the tag by itself isn't working, though.

[jbuller]

It would be useful to have clarity on whether the phase banner (and breadcrumb)s should be inside the main element or not. (I'd say outside)
The Start page pattern on the Design System has it above

However for example https://www.gov.uk/service-manual/helping-people-to-use-your-service/making-your-service-accessible-an-introduction has it inside the main element,
This means the Skip to content link only cuts out about half the points of keyboard focus it would otherwise.

[dashouse]

@jbuller @stevenaproctor Hi, you'll find this implemented in many different ways across GOV.UK sites as they were all made at different times. If you're using the GOV.UK Design System / GOV.UK Frontend then this page on the design system clarifies the structure of the page we intend people to use https://design-system.service.gov.uk/styles/layout/#page-wrappers

[jbuller]

Thanks for the pointer.
I'd say it should be clearer on the phase banner page, or link to where it is clarified.
I didn't even find the page you highlighted when I was searching.
Actually, only the 'Customised page template' section of next page has the phase banner html in the larger context, above main element https://design-system.service.gov.uk/styles/page-template/

[suryanaga]

So to request a few changes to this:

1. We should clearly state the Alpha phase banner should only be used for prototypes, not working services. Possibly a link to the service manual's page about the alpha phase would be useful here.
2. In the beta banner, we should recommend linking to both the legacy service and the support channels that are available for users struggling to use the service. (I think @soniaturcotte did something like this recently for a GOV.UK Publisher beta.) Possibly it would be good to design a few options for people to pick from, depending on the setup of their beta.

[dashouse]

Thanks @sanjaypoyzer, as this is a direct request for an update to the guidance I've moved this into an issue on the Design System itself so it can be triaged in our next session.

#869

[drewno-design]

@jbuller @stevenaproctor Frontend then this page on the design system clarifies the structure of the page we intend people to use https://design-system.service.gov.uk/styles/layout/#page-wrappers

I am not sure how to interpret the placement of phase banner. Should it be directly underneath header but before main element?

My main concern is that if the phase banner is in the main element, then it is read by screen reader at the beginning of the main content.

[jbuller]

I agree it's still not clear. The phrase "so that they sit directly underneath the header." suggests outside of the <header> element and then it says to put it in the same div wrapper as the <main> element.
So that means its not supposed to be in any landmark area?

But yes your reasoning is correct, don't put the phase banner inside the main element to avoid clutter.for assistive technology users on every page.

[terrysimpson99]

I propose a rethink of the phase banner. It doesn't satisfy a user need for the services that I'm involved with and doesn't appear to add a business benefit either. I've never understood what it's for and the guidance page doesn't say.

I asked on slack and there were two suggestions:
(1) somebody suggested it would help a user if there is more than one version of the service (such as www.moneyclaim.gov.uk
and https://www.gov.uk/make-money-claim) or one service available in two phases.

(2) somebody suggested it helps if a service is undergoing rapid change.

Scenario 1 makes sense. I can see why scenario 2 exists but for most services and most users it's a moot point. As long as the user can get from the start to the end of the journey there's no benefit in the banner.

The phase banner contains a feedback link. Here are my thoughts on that: (a) if it's important then there would be a feedback link for live services; (b) on our service in the last month, we got ~11700 instances of feedback, only 26 of those via the feedback link in the phase banner, the rest were from the post-submit feedback; (c) Of the 26 instances of the feedback some of them were requests for assistance and so the feedback link is drawing users away from our 'Get help with this page' link on the same page; (d) having a feedback link in a feedback page is too weird for me but that's what we do.

In summary, I'm raising two separate issues: the first relates to the phase banner; the second relates to in-page feedback. These two issues can be considered separately. What do others think?