Build consistent and responsive design

• Follow the whole-of-government content management model.
• Use the digital design styles and assets in the design system, starting with a mobile first and responsive design.
• Comply with WCAG 2.1 AA for accessibility.
• Write using plain language. Aim for a reading age below grade 9 unless there is a clear need for technical language.

Using responsive design, following common design patterns and style guidance for digital content, and making sure the service is accessible means it will be simpler, clearer and faster for all users. It will also be available on the platforms and devices that users choose.

Consistent design that is responsive to different devices helps you to save time and money by re-using something that already exists that follows better practice and is based on data and user research. This means you can concentrate on the unique things your service needs to do.

Responsive design ensures that users can interact with your service regardless of their device size or type, and browser or device processing power. The service should follow mobile-first design principles, consider users on slow internet connections or with limited download data, work well for both mouse and touch devices, and use front-end technology that works well regardless of device processing power.

Writing and designing content so it is consistent, plain and in the language of your users helps people gain trust and confidence in using different services. By providing information they can easily understand they may be less likely to use alternative sources that could be misleading.

During Alpha stage you need to consider the design methods and patterns you could apply in your service, and how you can communicate simply and clearly with your users.

You should:

• understand how you will use responsive design for platform independence
• understand how you will use existing design patterns to make the service consistent:
  • Consistent User Experience (CUE) standard for sites outside the qld.gov.au (for example department/agency sites, campaign sites)
  • Single Website Experience (SWE) template for information and services appearing on Queensland Government website (www.qld.gov.au).
  • Queensland Government Design System (beta) can also be used when available (over time, this will replace the CUE).
• create simpler and more clear information by understanding the language of your users, using plain language by default, and applying contemporary online writing methods
• follow accessibility better practice and are planning how your public prototype will meet WCAG 2.1 level AA (Opens in new window)
• ensure appropriate design, content design and front-end developer support is provided to the team.

As you develop through Beta stage and progress to Launch stage,you should be applying these principles and design methods and will be expected to show them in your service.

• Website standards, guidelines and templates
• Publish on Queensland Government websites
  • About the Queensland Government website
  • Franchise model statement of commitment
  • Decide which website to publish your content on
  • Request a new website (log in to For government)
• Consistent User Experience (CUE) standard
• Single Website Experience (SWE)
• Queensland Government Web writing and style guide
• Corporate branding and identity
• Principles for the design, development and deployment of mobile apps

• Asset Mapping for Experience Consistency (external)
• Australian Government Style Manual (Opens in new window) (external)
• 18F Content Guide (Opens in new window) (external)
• 18F Blog Looking at the different ways to test content (Opens in new window) (external)
• UK Government Digital Service Style guide (Opens in new window) (external)