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

File upload #93

Open
davidhunter08 opened this issue May 28, 2019 · 4 comments
Open

File upload #93

davidhunter08 opened this issue May 28, 2019 · 4 comments
Labels
component Goes in the 'Components' section of the service manual staff-facing

Comments

@davidhunter08
Copy link
Contributor

What

Help users select and upload a file.

See the discussion from our friends at gov about this component.

@davidhunter08 davidhunter08 added the component Goes in the 'Components' section of the service manual label May 28, 2019
@cbernardojr
Copy link

This is the solution we're using for the Apps library project based on GDS:
https://design-system.service.gov.uk/components/file-upload/
Screen Shot 2019-05-28 at 11 17 07

@davidhunter08 davidhunter08 added the awaiting triage Needs triaging by team label Jul 2, 2019
@davidhunter08 davidhunter08 added help wanted Extra attention is needed and removed awaiting triage Needs triaging by team labels Aug 6, 2019
@devansXD
Copy link

devansXD commented Oct 7, 2019

Example on eRS - based on the GDS component. Has tested well.
Screenshot 2019-10-07 at 11 25 06

@BrieWhyatt
Copy link

We are proposing using the file upload mechanism with 3rd party online consultation suppliers. The following design (in line with above examples) will be tested soon and findings will be fed back.

get-advice-file-upload

@samanthasaw
Copy link

samanthasaw commented Dec 8, 2020

Findings from testing the NHS App file upload within an third party online consultation eczema triage journey:

What we tested:
Screenshot 2020-12-08 at 16 13 13

Key findings:

  • Photo upload design was seen as a welcome addition, best and most sensible part of the Eczema journey​
  • 1 user expected to input the description of the photo whilst they could see the photo ​
  • 1 user expected to be able to upload more than 1 photo ​
  • Some users tried to click the upload button before choosing a photo. However we think the fact that users were used to just clicking through the journey without inputting anything impacted this. We think that users didn't expect to have to upload anything or were reluctant for their private photos to come up.​ Also we tested this using an iframe, so users were not using a mobile device. This could also have impacted user behaviour.

Quotes:

  • "I would have asked the description with the actual picture just because you've got the photo in front of you. Not all of us have brilliant visual memory" ​
  • "[Photo upload] really good actually, [GP can] see [the] problem before appointment"​
  • "I would have probably said to let more than 1 photo in, I saw you're only allowed 1 photo" ​
  • "Describe what this photo is showing – that's a silly question"​
  • "That's good but I think it should also include that it's secure, if you're adding a photo it is quite a sensitive subject"

Next steps:

  • We have iterated the content of the native element to say
    [ Choose a photo ] No photo chosen
    Rather than
    [ Choose a file ] No file chosen
  • Rhiannon Smith is reviewing the content to give users confidence that the image will be sent securely
  • I'm exploring options for showing the image to the user when they are asked to describe it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component Goes in the 'Components' section of the service manual staff-facing
Development

No branches or pull requests

6 participants