Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Back link #95

Closed
eliothill opened this issue Dec 18, 2017 · 8 comments
Closed

Back link #95

eliothill opened this issue Dec 18, 2017 · 8 comments

Comments

@eliothill
Copy link
Contributor

Have experienced multiple research participants not notice/understand the 'back button' in the context of the form, when needing to correct an error on a previous page.

Users are less inclined to use the browser back button in case it takes them away from the form (assume from previous experience of single page applications).

Suggest making text more descriptive, increase space and make use of icons consistent.

@eliothill eliothill created this issue from a note in Design system backlog (Proposed (anyone can add)) Dec 18, 2017
@eliothill
Copy link
Contributor Author

eliothill commented Dec 18, 2017

Suggested update
suggested-update

Examples of guidance navigation
arrow-on-other-nav

Example of chevron icon on miller column nav – guidance page
arrow-on-miller-column-nav

Example of details/summary used in progressive disclosure (the reverse of what is currently the back link icon)
details-progressive-disclosure

Current back link icon
current-back

Example taking out for usability testing
example-1-taken-for-usability-test

@jimkosem-hod
Copy link

Have actually seen it used in testing a couple of times. Can't give you exact figures though.

@owenm6
Copy link
Contributor

owenm6 commented Dec 19, 2017

Feedback from Megan: fear from some users that the back button would undo work. Users weren't sure where the back button would take them.

@jimkosem-hod
Copy link

Fair point. It could go both ways really. I think in terms of anything you need to submit it might be best avoided, but if it was anything that is more informational or navigational, then I would think its fine.

@owenm6 owenm6 moved this from Proposed (anyone can add) to Backlog in Design system backlog Dec 19, 2017
owenm6 pushed a commit that referenced this issue Jan 9, 2018
@owenm6
Copy link
Contributor

owenm6 commented Jan 9, 2018

@owenm6 owenm6 moved this from Backlog to Experimental in Design system backlog Jan 9, 2018
@owenm6 owenm6 changed the title Improving back button Back link Jan 24, 2018
@eliothill eliothill mentioned this issue Apr 5, 2018
ctdesign pushed a commit that referenced this issue May 4, 2020
@karypun
Copy link
Contributor

karypun commented Jul 1, 2020

Closing this issue as it currently exists in the design system: https://design.homeoffice.gov.uk/components/back Raise a new issue if needed

@karypun karypun closed this as completed Jul 1, 2020
@isobelseacombe
Copy link

Been doing lots of thinking about this in PPPT lately. Have come up with rules for using back links in lateral task flows and breadcrumbs for app navigation. Sharing work with colleagues in BICS then will share here

@chris-barrett-ddts
Copy link

Been doing lots of thinking about this in PPPT lately. Have come up with rules for using back links in lateral task flows and breadcrumbs for app navigation. Sharing work with colleagues in BICS then will share here

We're having similar thoughts on WRLS at the moment and just wondering how this was implemented on your service and what the outcomes were? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

6 participants