...for this project to be coded in the open, with all code published on github.com in open repositories. Where this is not possible there should be a convincing explanation as...
...the research was conducted may not in all instances be the end users of the product. It is recommended that the needs of these admin and helper end-users are assessed...
...code to allow general open source release. This is something that could be reviewed in the future. A login is required for the service. The service is targeted exclusively at...
...form into two distinct registration and information-gathering steps to eliminate the confusion of a confirmation screen part way through the journey, and introducing logical branching so that users are only...
...complete the digital service independently. The AD support also includes digital inclusion approaches through scripting and signposting. Needs assessment is in place within the phone support, for the issuing of...
...development team to release but there is some downtime necessary (albeit measurable in minutes). These abilities are expected to remain in place for public beta with the service looking to...
...brought in for alpha assessment is limited in scope and there are some areas which the team will need to focus on in private beta development and which will need...
The service will use this report to inform continued development in the interim until they plan to move to private beta development in autumn 2016 when a further assessment will...
...of formal and informal intermediaries a range of attitudes towards the process and the institutions involved (caution, wariness, fear, etc.) time pressures to apply The data gathered during this fieldwork...
...line is in place with support, and the team have provided a questionnaire for feedback to ensure that they get the type of information in line with inclusion scales required...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.