Hackpads are smart collaborative documents. .

Ed Horsford

1 day ago
Unfiled. Edited by Ed Horsford 1 day ago
Ed H
  • Accessibility of progress indicators
Here's the markup that Passports uses to communicate the upload progress to users of assistive technology:
  • <div id="progress-container" class="progress-container" role="region" aria-live="assertive" tabindex="-1">
  •   <p id="progress" class="progress" role="progressbar" aria-valuenow="99" aria-valuemin="0" aria-valuemax="100">Uploading image</p>
  •   <div class="percentage"><p id="percentage">99%</p></div>
  • </div>
  • <div class="column-two-thirds hide">
  •   <header>
  •     <h1>Upload your photo</h1>    
  •   </header>
  • </div>
  • Representing loading with semantics
64 days ago
Unfiled. Edited by Ed Horsford 64 days ago
Uploading is a challenging interaction for many users, particularly on desktop devices. It's somewhat easier on mobile devices, but still presents challenges. Users lower on the digital literacy scale will struggle and may not be able to use a service if they need to upload as part of it.
Ed H File picker
The most basic upload mechanism is the file picker. This can be difficult to use on desktop devices, but works well on mobile devices. You should support using a file picker as a minimum before adding alternatives.
Drag and drop
Proficient  computer users may prefer to drag and drop from their file system onto the browser. 
Always use another upload method alongside drag and drop.
  • Drag and drop only works in modern browsers
  • Users with dexterity problems such as tremor may have difficulty dragging a file.
  • You may want to support drag and drop to support users who attempt to drag a file, and would otherwise lose their progress in the service.
28 days ago
Unfiled. Edited by Joe Lanman , Ed Horsford 28 days ago
  • Multiple levels of navigation
Ed H
  • Case management
  • Order of cases to work on / prioritise
  • SLAs
  • Access guidance
17 days ago
Unfiled. Edited by Ed Horsford 17 days ago
Ed H Passports
Register to Vote
28 days ago
Unfiled. Edited by Ed Horsford 28 days ago
Ed H DWP patterns
Lasting Power of Attorney
24 days ago
Unfiled. Edited by Ed Horsford , Sanjay Poyzer 24 days ago
  • Sign-out
Ed H Digital Marketplace
55 days ago
Unfiled. Edited by Ed Horsford 55 days ago
If GOV.UK Verify is not a good fit for your service, consider a passwordless account system. The best way to do this is to ask for the user's email address. When they need to sign in again, send a time-limited access code to that account. This approach means the user does not need to remember usernames and passwords.
Joe L
  • this makes email address a requirement. What do we do with people who don't have them? Or share an account. I would recommend they open one and provide links to Gmail, Outlook. I think the complexity of supporting alternative models is too great and could impact too much on the large majority.
Jason B
  • Some users want to be able to share their sign in with trusted parties to review their application. A time limited email doesn't work in this scenario. Ideally you'd set up user accounts with separate access for each of the individuals but for some services this might be overkill. Having username and password allows users to easily share access.
Ed H
  • I think this highlights a user need around providing a *way* for a second party to access an account - but doesn't necessarily preclude passwordless as a solution. Something to think about.

Contact Support

Please check out our How-to Guide and FAQ first to see if your question is already answered! :)

If you have a feature request, please add it to this pad. Thanks!

Log in / Sign up