Search

The DAS is not mandating one login for users or a single front door for government digital services, but careful consideration into the creation of new access points and investigation into the benefits of the consolidation of multiple access points. Australian Government digital services are currently dispersed across multiple agency websites, portals and apps. This means that people need to understand how government works to find the support and services they need, leaving them to navigate a fragmented and decentralised digital government landscape. The myGov User Audit called for a consolidation of digital services across government to stop this situation from worsening. A coordinated approach moving government agencies towards a more centralised digital landscape is needed to support people in navigating government services.  The DAS is part of a suite of standards and guidance that sits within the Digital Experience Policy (DXP). The DXP supports a whole-of-government (WofG) focus on improving the experience for people and businesses interacting digitally with government information and services. The DXP includes a suite of standards and guidance that supports agencies to deliver more cohesive and consistent digital experiences, including (but not limited to) the Digital Service Standard, the Digital Inclusion Standard, and the Digital Performance Standard. Digital Access Standard Page 2 The DAS is an extension of Criterion 4 ‘Connect services’ and Criterion 6 ‘Don’t re-invent the wheel’ of the DSS to support a common experience for users. The DAS sets criteria that agencies must meet to determine where their new digital service fits into the whole-ofgovernment digital service landscape. The criteria will help agencies assess whether a new access point is required or if they can reuse existing platforms and capabilities. This policy will ensure agencies design and deliver digital services in consideration of broader government landscape, including the Data and Digital Government Strategy (DDGS) the Digital Service Standard (DSS) and The Digital and ICT Reuse Policy. The DAS supports the DDGS and DSS by promoting consistency across digital services and ensuring services: • are accessible • are secure • are transparent, and • meet the needs of people and business

• Listen to and understand diverse user needs: Consider diverse user needs from the outset. This will make sure services cater to the greatest range of users possible. Consider the different identities, characteristics and perspectives of users to make sure the digital service is welcoming and inclusive for all.
• Conduct usability testing with diverse user groups: Do usability testing with individuals from diverse backgrounds, including those with different abilities, ages and cultural contexts. Adopt inclusive prototyping techniques to simulate the experiences of users with different abilities and identify potential challenges. Recognise that various aspects of a person’s identity, such as race, gender and age, all work together to shape their digital experience.

Co-design with users

Involve users throughout the Service Design and Delivery Process to make sure their perspectives, needs and feedback are incorporated into the final service. Encourage shared ownership by co-designing accompanying artifacts, such as tutorials and guides, using language that is meaningful to all.

Consider cohort-specific digital inclusion requirements (outlined below)

Tailor the digital service to meet the specific needs of user groups and promote inclusion to make sure support is provided at the appropriate level. Consider how to apply the following cohort specific requirements when designing and delivering digital services.

People with disability

• Use person-first language: Use respectful language in the design and delivery of your digital service. Say ‘people with a disability’, not ‘disabled person’.
• Support independence: Support users to complete their service by providing clear explanations and instructions up front. Advise the user on the documentation they will require at the start of the transaction, so they do not have to get all the way through to understand the requirements.
• Avoid story repetition: Where appropriate, seek consent to share data about user accessibility needs with other channels and services. This avoids them needing to repeat their personal information.

Blind or low vision

• Consider alternative login approaches: Support your users to access alternative login approaches, such as voice identification, instead of the more traditional password entry methods.
• Tag and code headlines: Make the information architecture assimple as possible so information is easy to read and navigate by screen-readers. Tag and code headline types appropriately to support those with vision impairment.
• Make it audible: Offer information in audio formats to support easy access to information. Consider if you can provide audio instructions for how to complete the service to support users to complete their interactions digitally end-to-end.

Deaf or hard of hearing

• Use interpretation technologies: Where available, consider how you can take advantage of best practice and leading technologies for Auslan interpretation (i.e. picture-in-picture solutions).

First Nations Australians

• Respect family structures: Be aware of and respect family structures and the dynamic and complex nature of Aboriginal kinship relations. Collaborate and co-design with Elders and other First Nations Australians throughout the Service design and delivery process.
• Recognise that some information may not exist: Understand that some documents do not exist, due to historical factors, remoteness or lack of available services. Where no legislative barriers exist, consider what alternative documents can be used to support the completion of a service.
• Use visual communication tools: Use visual communication to supplement wordy paragraphs and visual cues. Visual communication should be meaningful from a First Nations perspective.
• Respect privacy: Only request information that is legislatively required and avoid unnecessary additions. Acknowledge that trust may be lacking and be transparent about what the information will be used for and who can access it.
• Use culturally safe language: Consider how chatbots and staffed chat functions can use culturally appropriate language: for example, ‘Are you living with extended mob?’

Persons impacted by family and domestic violence

• Provide visibility of who has access: Consider providing users with a clear and easily accessible list of who can access the service and who will be notified of any changes for example, a change of address. Give users the choice of when and how they receive government communications and make it easy to change, in the event they need to do it quickly.
• Make it easy to remove multiple users: Support survivor-victims to remove multiple users from accessing a shared government service or account. Consider privacy enhancing ways for users to do, so it does not unnecessarily trigger or notify other users.
• Support ‘quick exit’: Consider the use of ‘quick exit’ buttons within your digital service to help re-direct users to other digital pages if they are in an unsafe environment.
• Clearly communicate tasks and actions: Use simple steps and actions to clearly communicate what is required and limit the impacts on survivor-victims. Consider the use of checklists and easy-to-follow formats to avoid decision fatigue and to support the survivor-victims to complete the service.

Neurodiversity

• Keep interfaces and interaction patterns predictable: Be clear on the expectations and next steps by letting users know exactly what will be required of them ahead of time. Consider using consistent designs and patterns to support a seamless transition within the service.
• Make users feel welcome and accepted: Cater to different learning styles and preferences by offering supplementary options to text, such as audio and visual formats and through pictures or images. Allow users to customise their interface by changing colour schemes and making other types of personalisation.
• Simplify the language and service: Simplify language to make it easy to understand and follow without being condescending or minimising the user. Break up tasks into manageable sections and allow forms to be saved so users can return to them later.
• Communicate status: Support users to track the status of their digital services and interactions by communicating status information. Proactively remind users to finish tasks using alerts and notifications if paused part-way through.

Culturally and linguistically diverse communities

• Use visual communication tools: Provide visual ways of communicating as a supplement to wordy paragraphs and visual cues that can be easily interpreted. Create repeatable steps and actions to support users to complete tasks. Consider the use of video conference and other software to help users understand the context through body language.
• Offer in-language options: Identify the most common languages used across your service and offer in language options on the front page of websites so it can be easily changed. Consider how you can offer your guidance materials and tools in other languages to support the user to complete the service.

People with low digital ability

• Clearly communicate tasks and actions: Use simple steps and actions to clearly communicate what is required. Consider using checklists and easy to follow formats to avoid decision fatigue and to support the user to complete the service.
• Support users to move between service channels: Where appropriate, consider how you can support your users to move through your service channels using easy to gather information. For example you may offer downloadable content that they can print out and take into a shopfront to complete the service.
• Apply search engine optimisation: Consider how you can effectively apply search engine optimisation to support users to find information and services easily.