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
Comments
Have actually seen it used in testing a couple of times. Can't give you exact figures though. |
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. |
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. |
Added the component - https://home-office-digital-patterns.herokuapp.com/components/back |
Closing this issue as it currently exists in the design system: https://design.homeoffice.gov.uk/components/back Raise a new issue if needed |
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 |
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.
The text was updated successfully, but these errors were encountered: