Victorian Government Accessibility Toolkit - Version 3 - September 2009 - in pdf format (2898kb)
(This document requires the use of Adobe Acrobat Reader). Department of Business and Innovation, Information Victoria, September 2009 - Version 3.1.1 - March 2011 (minor edits). "The Victorian Government’s Accessibility Standard requires that: All websites must be Level AA compliant (W3C Web Content Accessibility Guidelines, Version 1.0); Where audience needs are specific, websites should become Level AAA as appropriate. This toolkit shows departments and agencies how to conform to this policy and the W3C Web Content Accessibility Guidelines, Version 1.0. The toolkit is designed for Victorian Government business managers and web site owners to enable them to effectively present the business case for accessibility and manage the processes involved..."
An accessible HTML version of the toolkit is currently under development.
Further information on Victorian Government Accessibility Toolkit - Version 3 - September 2009 - in pdf format (2898kb)
Last updated: 29 March 2011
-
Victorian Government Accessibility Toolkit - Version 3 - September 2009 - in word format (4990kb)
-
(This document requires the use of Microsoft Word Reader). Department of Business and Innovation, Information Victoria, September 2009 - Version 3.1.1 - March 2011 (minor edits). "The Victorian Government’s Accessibility Standard requires that: All websites must be Level AA compliant (W3C Web Content Accessibility Guidelines, Version 1.0); Where audience needs are specific, websites should become Level AAA as appropriate. This toolkit shows departments and agencies how to conform to this policy and the W3C Web Content Accessibility Guidelines, Version 1.0. The toolkit is designed for Victorian Government business managers and web site owners to enable them to effectively present the business case for accessibility and manage the processes involved..."
An accessible HTML version of the toolkit is currently under development.
- Audio and podcasts - Accessibility Toolkit - Version 3 - 2009
- There will be people who won't be able to access the audio file or podcast because: they are deaf; they are in a noisy environment; they cannot play sound. Audio files and podcasts cannot be made fully accessible, but they can be made accessible to some people with disabilities – for example people who are hearing impaired or deaf – by providing a transcript of the content in text or HTML.
- Audio describing videos - Accessibility Toolkit - Version 3 - 2009
- How to use Magpie 2.0 to create audio descriptions of all the visual content in online videos to make them more accessibility to people with disabilities.
- Blogging and Accessibility - Accessibility Toolkit - Version 3 - 2009
- Blogging is often just text or a combination of text, images and links. Therefore it is easy to make a blog accessible. However a blog has all the same potential accessibility issues as a web site does. Consequently blogs should always be tested against the W3C Web Content Accessibility Guidelines, Version 1.0, Level AA.
- Captioning downloadable videos - Accessibility Toolkit - Version 3 - 2009
- How to use Magpie 2.0 to create captions for online videos to make them more accessibility to people with disabilities.
- Captioning Vodcasts - Accessibility Toolkit - Version 3 - 2009
- Vodcasts cannot be made fully accessible, but they can be made accessible to some people with disabilities; for example people who are hearing impaired or deaf. A vodcast is made accessible by: providing a transcript of the video in text or HTML; and providing captions of all the audio content in the video.
- Captioning YouTube videos - Accessibility Toolkit - Version 3 - 2009
- How to use Magpie 2.0 to create captions for YouTube videos to make them more accessibility to people with disabilities.
- Creating sites accessible to people with cognitive disabilities - Accessibility Toolkit - Version 3 - 2009
- People with cognitive, language and learning disabilities comprise the largest group of those with disabilities accessing the web.
- Facebook and Accessibility - Accessibility Toolkit - Version 3 - 2009
- Facebook is a social networking site where users can keep in touch with their friends, post photos and videos and play games. Facebook uses a combination of technologies which make it inaccessible; however there is an HTML version of Facebook which can be used by screen reader users. However, Facebook is not accessible to other groups of people with disabilities
- Flash and Accessibility - Accessibility Toolkit - Version 3 - 2009
- Flash cannot be made fully accessible, but it can be made accessible to some people with disabilities; for example people using screen readers. A Flash file is made accessible by: Creating the Flash in a particular way; Inserting the Flash file in the site a particular way; and Providing a transcript of the Flash file in text or HTML.
- Frames and iFrames - Accessibility Toolkit - Version 3 - 2009
- According to the Web Content Accessibility Guidelines (WCAG), Version 1.0, frames are inaccessible and any information contained within a frame must be provided elsewhere (Checkpoint 1.1). Some assistive technologies do now interact with frames and iframes, however it is still important to provide equivalent, accessible content where they are used.
- Making a PDF accessible - Accessibility Toolkit - Version 3 - 2009
- This is a guide to creating accessible pdfs, however, PDFs cannot be made fully accessible, but they can be made accessible to some people with disabilities; for example people using screen readers. A PDF is made accessible by tagging certain elements within it, for example images. If a PDF is tagged properly then a person using a screen reader can often understand a PDF just as well as an HTML document. However PDF does not yet have all the features of HTML, and therefore an equivalent must always be provided.
- Making maps and Google maps accessible - Accessibility Toolkit - Version 3 - 2009
- Online maps are inaccessible to vision impaired people so a textual alternative (long description) must always be provided. It is also important to include accessibility features within the map so it is accessible to people with other disabilities e.g. by making the map non-reliant on JavaScript and keyboard accessible.
- Making Slideshare Accessible - Accessibility Toolkit - Version 3 - 2009
- Slideshare is a presentation sharing website where users can upload, view and share presentations. Presentations can be tagged and commented. It is also possible to embed presentations into a web site or download the presentation. Presentations can be shared publicly or privately. Slideshare uses a combination of technologies which make it inaccessible; however there is an accessible version of Slideshare that can be used instead. Slideshare can be made accessible by: Providing an alternative of the presentation in HTML, text or Word; and Providing a link to Easy Slideshare (accessible Slideshare).
- Mashups and Accessibility - Accessibility Toolkit - Version 3 - 2009
- It is difficult to categorically state that mashups are inaccessible; it really depends on the primary applications and how they have been put together. The best way to ensure that mashups do not exclude people with disabilities is to provide a transcript of the mashup in text or HTML.
- PDFs and Accessibility - Accessibility Toolkit - Version 3 - 2009
- Portable Document Format (PDFs) are inaccessible according to the W3C Web Content Accessibility Guidelines version 1.0. There are methods that can make the actual PDF available to certain people with disabilities (for example, creating tagged PDFs ), however even if these documents are created in an accessible way the information still will not conform to the W3C Web Content Accessibility Guidelines. The Australian Human Rights Commission has commented that Word documents are accessible: "When documents are only put on the Internet in PDF format, it usually results in inadequate or zero access for people with disability. "You can use HTML, Microsoft Word, or RTF formats", said the Commissioner. "It's particularly depressing to see documents created in word-processor formats, which provide very good access, being converted into PDF, which doesn't, then only being posted in PDF." " It is preferable, of course, to provide an HTML version.
- Twitter and Accessibility - Accessibility Toolkit - Version 3 - 2009
- It is important to provide a transcript of the Twitter content on your site, for people who cannot use the Twitter interface or do not have a Twitter account.
- Victorian Government Accessibility Toolkit - Version 2 June 2007
- Version 3 of the toolkit has been published in pdf and word formats. An accessible HTML version of the toolkit is currently being developed and will be published shortly. Until this occurs Version 2 of the toolkit is made available in HTML. This is Section 1 of the Victorian Government's Accessiblity Toolkit providing an overview of the contents of the toolkit.
- Videos and accessibility - Accessibility Toolkit - Version 3 - 2009
- Videos cannot be made fully accessible, but they can be made accessible to some people with disabilities; for example people using screen readers.