Updated Web Guide released

Peter Alexander - AGIMO
The Department of Finance Archive

The content on this page and other Finance archive pages is provided to assist research and may contain references to activities or policies that have no current application. See the full archive disclaimer.


I’m pleased to announce the release of a revamped and updated Web Guide. The purpose of the Web Guide is to help agencies manage their online presence and understand their relevant legal and policy obligations in this space. The site replaces the previous Web Publishing Guide, which was launched in May 2007. 

The Web Guide contains the latest up-to-date advice in areas such as accessibility, Government 2.0, copyright, freedom of information and many more. We’ve also tried out some new things with the site, like our new page listing various PDF readers, including free and open source options. This is meant to be something agencies can link to from their own sites where appropriate rather than pointing their users to a single PDF reader application. In updating the Web Guide we have tried to consult as widely as possible on the redevelopment. We worked closely with a range of agencies to form the site’s new content. We reached out to our mailing lists and other relevant contacts to run focus groups about the site’s future. We also tried to consult with you, the public, wherever we could – before its content was rolled into the blog you’re reading now, my team ran a Web Guide blog. We used that blog – and later, the  AGIMO Blog – to discuss the progress of the site, including our design choices, the results of the focus groups and to release some the new content (particularly our Government 2.0 Primer) as soon as it was ready. In a lot of ways, launching the updated Web Guide is only a first step. We’re already at work developing more content to add to the site – for example, we know that agencies are interested in new guidelines about how to apply the mandatory Australian Government branding to mobile applications. From here, we will work to develop new guidance while also keeping the existing content current. I’d appreciate any comments on the updated Guide or suggestions for new content you may have to help us along the way.


Comments on this blog are now closed. Please let us know if you would like to discuss this post or have any general comments.

Comments (10)


This is a great idea. I would like my students to be involved in some of the usability testing if this is possible. I run a website design training course and the usability testing would really help them out. Let me know if this possible.
Kind regards

Great work Peter. It's great the guide has its own domain.

I think the new Web Guide will prove really useful. It's handy to have something authoritative like this that people can point to, particularly for smaller agencies. It will help people gain the trust they need from internal stakeholders to try new and creative things, especially around Gov2.0 and online consultation initiatives etc.

Well done team; concise, plain english, easy to scan through and very useful.

Congratulations on your revised guide. It makes interesting reading.

It's a shame that RSS was not a mandatory topic as it can still be a pain to cover new information on many Government websites.

One question is there a period of grace when these guidelines come into force or are they all current as of now?

HI guys. Just wondering where or when I may find the slides from the recent PDF Accessibility seminars held in Canberra.
(and you may want to have a look at this form as my comment was lost after not filling in the captcha:)

Hi Sebastian - the PDF slides should be available soon, you can find more information on our post about the training sessions.

Apologies for any difficulties with the CAPTCHA -- what you describe is a known issue, and something we'll look to resolve in the future.

Are there any guidelines on use of CAPTCHA on WCAG compliant sites?Our project believes our website will be a target for flooding attacks, and would like to make it more difficult for an attacker to write a script to overload our system.  

Thanks for the question Jason. WCAG 2.0 Success Criteria 1.1.1 allows CAPTCHAs as long as "text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities". However, it is well documented that many people still have difficulty with CAPTCHAs regardless of ability. There have been several comprehensive write-ups of alternative CAPTCHAs and their issues, e.g. “In Search of the perfect CAPTCHA”, but no fully accessible alternatives exist. Please contact AGIMO directly for further information.


I can't access the webguide in Safari or IE. Is the site down?

Many thanks,

Last updated: 27 February 2017