-
Notifications
You must be signed in to change notification settings - Fork 0
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
Buttons #12
Comments
Full width buttonsTeam Frontier have been exploring making buttons full width on the NHS App for smaller screens (640px and below). Next stepsContinue to test to see if:
|
Accessibility notes3.2 Touch Target Size and SpacingThe high resolution of mobile devices means that many interactive elements can be shown together on a small screen. But these elements must be big enough and have enough distance from each other so that users can safely target them by touch. Best practices for touch target size include the following:
3.5 Placing buttons where they are easy to accessMobile sites and applications should position interactive elements where they can be easily reached when the device is held in different positions. When designing mobile web content and applications many developers attempt to optimize use with one hand. This can benefit people with disabilities who may only have one hand available, however, developers should also consider that an easy-to-use button placement for some users might cause difficulties for others (e.g. left- vs. right-handed use, assumptions about thumb range of motion). Therefore, flexible use should always be the goal. Some (but not all) mobile operating systems provide work-around features that let the user temporarily shift the display downwards or sideways to facilitate one-handed operation. |
Button sizingCurrent sizing of the NHS design system button. From screen size width 641pxHeight = 60px
Width
Until screen size width 640pxHeight = 48px
Width
|
Secondary or low priority CTAI would add this here regarding the use of secondary buttons because I think it will become particularly relevant to the app in context where there is a promo but a primary button isn't appropriate. The current secondary had less design effort compared to the primary and it has weaknesses around versatility across different context, plus when paired with the primary, it is relies on colour alone to make the distinction of hierarchy between them. |
Sticky CTA's For the past few months, our team has been experimenting with Sticky CTA's, i.e. buttons which remain in a fixed position within the app viewport as the user scrolls up/down a screen. We have been exploring types of screens they may work well, as well as situations in which they would not be suitable.
/ Potential drawbacks of fixed CTA's would include:
/ Potential step-around / Conclusion / Useful links: |
what do we think about outline buttons? we've had feedback from users that the standard secondary button looks like it is deactivated. a outline format might be a way to avoid that impression while providing a button that isn't as emphatically THE MAIN THING as the big green button. |
An outline button was recently tested on a load more pattern for booking a gp appointment. [insert findings here] |
follow up about the image above: should the bottom edge of the button be thicker, so that it is more like the standard filled button, which simulates a 3D effect with the darker bottom edge? |
yeah, I think it does - that will also make it sit well next to a primary button (if used together in a button group) |
@davidhunter08 i would think option 1 makes the most sense for colour (because it is the most direct), but option 3 makes the most sense for size (so the bottom edge is the same height as the bottom edge on the primary button). not sure how you do that! also, bit of a curveball: are we willing to consider proposing increasing the size of the bottom edge and/or corner radius for all buttons? the rationale here is
some tests... |
@davidhunter08 Have a look at the way I implemented it on Start for life here The design spec on Figma here The actual working code on the 'sign up for newsletter' section https://www.nhs.uk/start-for-life/ DetailIn terms of the box shadow, I had to remove this because it was overlapping behind the transparent background, what I did instead was to use a 4px border bottom to create that shadow look. I also reduced the border opacity of the default state to allow for the animation transition when a user hovers or clicks it so it gives that instance feedback that it's an interaction element. In addition, I added a tinted blue for the background when hovering or selected, as well as change the font weight to be default when selected
Reference |
Research findings for secondary buttonsFor the Proxy application service, we trialled use of a secondary button on a screen where users could choose from two different actions:
Moderated usability research with 10 participants showed that the secondary button was not easily identified as the option to select to continue with a new application. This was mainly attributed to the grey colour. I'm checking for further findings on this and will update further if more comes to light. |
Research findings for buttons Source - NHS Wayfinder usability testing, May-July 2024. We tested new components in the NHS design system as part of our design system uplift work. 1. Full span buttons Finding: Patients found full span buttons clear and straightforward. They were recognised immediately as buttons and patients were able to move easily through the screens. 2. Button/link assembly component Finding: Patients recognised two distinct but related actions they could take and had no difficulty in finding both or either option. |
This is to match the designs in the prototype, using a newer button style that's currently being tested but not yet part of the NHS frontend. See nhsuk/nhsapp-frontend#12 for more details.
This is to match the designs in the prototype, using a newer button style that's currently being tested but not yet part of the NHS frontend. See nhsuk/nhsapp-frontend#12 for more details.
This is to match the designs in the prototype, using a newer button style that's currently being tested but not yet part of the NHS frontend. See nhsuk/nhsapp-frontend#12 for more details.
This is to match the designs in the prototype, using a newer button style that's currently being tested but not yet part of the NHS frontend. See nhsuk/nhsapp-frontend#12 for more details.
This is to match the designs in the prototype, using a newer button style that's currently being tested but not yet part of the NHS frontend. See nhsuk/nhsapp-frontend#12 for more details.
Secondary buttonDesign hypotheses
DesignDesktopMobileCoded examplesView coded examples (u: app / p: redesign) Next steps
|
@davidhunter08 This looks really good and something I've wanted to resolve in the service manual design system, any idea on when this will be tested? I'd be keen to get it straight into nhsuk-frontend rather than only the app, if that's possible. |
Hey @anandamaryon1, we're currently planning the user research for this, it's looking like it'll be in-person in Leeds on the 13th and 14th November. |
What
Use this issue to discuss buttons used on the NHS App.
Related
NHS App design system Figma file
NHS design system guidance
NHS design system discussion
GOV.UK Design System guidance
GOV.UK Design System discussion
The text was updated successfully, but these errors were encountered: