...to be a team working on this particular thing. What’s important to your team, and what sort of behaviours do you welcome? How are you going to deal with complex...
...GOV.UK Verify better for users. We welcome the input of experts, like the authors of this paper and, if that’s you, we’d encourage you to get in touch with us....
...new frontend, which is being built in the open, in the form of pages available in Welsh (adborth/feedback welcome) improved the workflow for our rapid technical support response team procured...
...organisations working together for greater security and privacy, is also new. You don’t need to wait for codes in the post, or post things yourself, or go in person to...
...in this blog post. We welcome comments and suggestions for improvements and would love to hear how GOV.UK Verify has worked for you. Our objective is to not just make...
...and keyboard while the rest of the mob act as ‘navigators’ by suggesting what source code needs to be produced. Not everybody will be part of the mob at all...
...pages (e.g. clicks made on links) and extra tagging code called custom variables which enabled us to segment the data. We also added an extra step into the process: when...
...Commissioner’s Code of Practice for Privacy Impact Assessments provides an excellent proposed methodology for a PIA, which was used as a starting point for the review of GOV.UK Verify. Conducting...
...skipping through sections that the screen reading software identifies using the header tags in the code. However, we realised that some of the pages in GOV.UK Verify don’t use headers...
...covering security, Agile methodologies, open source code and more. The process was resource-intensive but it helped to focus the team on the requirements of the live assessment and proved a...
