Or zoom in and out in maps. It's odder to have the zoom in button disappear than having a consistent interface. Worth keeping in mind that these use cases are nearly all very rare on the services we make.
I think it depends on the context. We normally use 'Back' would to take the user to the 'page they were previously on' - ie not a specific page. Though there may be contexts where it could be closer to how 'back' is used on iOS - ie up one level.
In this case the user has started on 'Business overview', gone through a process to amend business details and at the end of this clicks to return to 'Business overview'. So in their mind they are very much returning to 'Business overview' rather than continuing to it.
If this green button is on a screen that confirms the amended business details, 'Continue' would be my preference. If it shows amendments that have not yet been confirmed, it would be 'Submit'. 'Back to business overview' doesn't seem a CTA; if the user would logically expect to return to business overview after confirming amendments, 'Continue' makes more sense. However, this is just one example and the query I received was more in general about use of capitals when referring to screen titles.
hm, good question on capitals, I'm not sure to be honest - We normally use sentence case throughout. So "Continue to business overview" or just "Business overview" - but this might be a question for a content person like Stephen Gill
I think it's sentence case. You either understand what we mean by 'Back to business overview' label or you don't - I don't think capping up 'Business' helps. If people don't understand what you mean, the answer is probably to change the label.
Not sure where to put this, but the use of 'should' tested really badly when I was at Universal Credit; it was experienced as patronising and we subsequently avoided using it. GOV.UK uses it though (eg 'You should upgrade your browser' instead of 'Upgrade your browser' or 'We advise you to upgrade your browser'). Any thoughts or experiences?
I mentioned this to the content team here and they're already avoid use of the word 'should' where they can - this must have just escaped their beady eye. I'll raise the same issue on the browsers page as well
Millie Guest I designed the original tables on /performance. The links weren't always seen, that's true. They should probably be underlined too. Not all users found them, but those that did understood what was happening. Tables should be usable without sorting too. Another option might be to have an explicit "Sort by: X, Y, Z" option that users can pick from. For the sorting itself, don't just reverse the current order - keep entries that are unsortable at the end. Eg several rows might not have a numeric value. Rather than treating these as sortable, sort your numeric entries and keep non-sortable ones alphabetical at the end. Also think about initial sort order. Whether greatest>least or least>greatest makes more sense. Will depend on the data.
We are struggling with complex data entry tables that include totals both in the rows and columns. Typically these tables have 8 columns, with very little space to explain what, for example, OM2b stands for. Displaying a key above the table means a long list of definitions (the tables are displayed dynamically, based on the user's previous answers). Any examples or tips?
Pietro Desiato Yes, it's arguably a little odd. Basically, the GOV.UK start page template places the 'Before you start' heading on the page automatically, in that position. The GOV.UK core product team were looking at improving the start page templates, but I'm not sure where they're up to with that.
Caroline Jarrett sorry it was a while ago and I'm not totally sure what the changes were? It still seems like 'other ways' is part of this section, which was my original issue. Actually, it seems like this content has gone out of sync with the image? (3) is the button in the image...
If the service is not hosted on GOV.UK then then tell the user why it's hosted elsewhere.
what would be an example of explaining 'why'? Is it a user need to know?
'Remember me' type functionality isn't about storing passwords - as you say they should never be stored (only hashed and salted versions). I think 'remember me' typically does two things: stores the username / email for easily filling, keeps the user logged in longer. It would be worth a conversation with your SIRO / other security professional. Typically you'll have a session time limit, and we shouldn't offer the user the option to keep it alive. For storing the username / email, I guess it depends on if this is sensitive and if you think it's helpful to your users - ie the user need.
Thanks Ed. This is for one of the Environment Agency's services, which is only used by internal users who typically take several days or even weeks to complete the process of submitting a project funding proposal. I accept that this is different from public services.