This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
[3155] Fix error styling and standardise behaviour across the service #222
Merged
dankmitchell
merged 7 commits into
master
from
3155-fix-error-message-inconsistency-design-review
Mar 25, 2020
Merged
[3155] Fix error styling and standardise behaviour across the service #222
dankmitchell
merged 7 commits into
master
from
3155-fix-error-message-inconsistency-design-review
Mar 25, 2020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Auto pull request trigger is configured on this repository for PR validation. To review the app deployed by this PR, please replace |
f77e421
to
1048534
Compare
1048534
to
86d493a
Compare
Home/location page did not follow the styling convention we use throughout the service and recommended by GOV.UK Design System.
Reorders the hint/error message so that it matches govuk-frontend guidelines of label, hint, error.
I discovered there where elements on the page had the same id. THis causes a couple of issues - Elements on a page should have unique ID - Field labels did not work because label did not know which element to focus on (Accessibility issue) What was causing this is that we output a bunch of hidden fields that represent params which we track throughout the users journey. We should have excluded any form fields that were being used on the page.
fixes an accessibility issue with location/provider text fields not having labels. Screenreaders would not be able to provide the context of the input to the user. The labels were present but they were not using the correct input id for their `for` attribute. (No visual difference but users should be able to click on the labels)
The error summary link should set focus on the first radio/checkbox in a list or the invalid text field.
The user does not get the opportunity to select which type of studies they are interested in as part of the initial search. We include all types of study by default. The user can change the filter to narrow their search. We have a validation that ensures at least one checkbox is ticked. However, if the user decides to untick each option and submits the page, we provide them with an error message stating they should pick at least one option but both checkboxes are ticked by default so it maybe confusing to the user as they did not tick each option and both checkboxes are already ticked. They maybe confused as to how to correct this error as it seems to have corrected itself.
error summary links should set focus on the first radio/checkbox
86d493a
to
04409e2
Compare
dankmitchell
approved these changes
Mar 25, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
During migration from c# to Rails, a lot of different developers worked on various pages and were mostly trying to replicate what was done in c#. Unfortunately, this introduced some inconsistency in styling, error messages and interaction when the user clicked on the error summary link.
Changes proposed in this pull request
Home/Location page
Study type filter page
Qualification filter page
Screenshots
Before - Home/Location page (3 error states)
After - Home/Location page (3 error states)
Before - Study type filter page
After - Study type filter page
Outstanding issues not addressed in this PR
Home/Location page
Subject page
Generally, the subject page is complicated because we are using an accordion to group what would have been a large list of checkboxes into different groups.
Checklist