There will be people who won’t be able to access the Flash file because:
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:
Checkpoint 1.1 requires that a text equivalent is provided for every non-text element (e.g. via "alt", "longdesc", or in element content). This includes: applets and programmatic objects, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
Checkpoint 6.2 requires that equivalents for dynamic content are updated when the dynamic content changes.
The Flash file needs to be created in a particular way, in order to make it accessible. Accessibility needs to be considered both when creating the Flash file and when inserting the file into the web site.
Use FlashMX to develop the Flash file and ensure that:
When creating the Flash file ensure:
The Flash file needs to be inserted in the site in a particular way, in order to make it accessible. Accessibility needs to be considered in how the user will access the Flash file. Website Flash content should :
Further when inserting Flash content into your website:
It is important to provide a transcript of the Flash file. Where the user cannot access the Flash file, it is vital a transcript is provided (in HTML, text or Word) so that they are not missing out on the content within the Flash file.
Languages Online (by the Department of Education and Early Childhood Development) contains a variety of language activities, including an Indonesian language activity .
In the example above, selecting one of the children will play an audio file is played pronouncing a phrase. The aim of the exercise is to test whether a student has learnt the Indonesian phrase for "Good morning" and other words, and reinforcing the pronunciation of the word.
A suitable, accessible alternative needs to be the equivalent of the activity, thus it needs to test whether the student knows the Indonesian phrase for "Good morning" and other words and provide the pronunciation. In this instance the accessible alternative might be similar to the example below:
Fill the gaps with one of the following phrases:
Selamat pagi (pronounced sell-amat pag-e with a hard g)
Selamat siang (sell-amat see-ang with a hard g)
Sampai jumpa (pronounced sump-ay joomp-a)
Selamat malam (pronounced sell-amat mull-um)
Selamat sore (pronounced sell-amat sore-ee)
It’s before 11am. Jill says ___________
It’s between 11am and 3pm. Jerry says ___________
It’s between 3pm and 6pm. Jackie says ___________
It’s after 6pm. Jack says _____________
John says ______________Answers
It’s before 11am. Jill says selamat pagi (good morning)
It’s between 11am and 3pm. Jerry says selamat siang (good [middle of the] day)
It’s between 3pm and 6pm. Jackie says selamat sore (good [late] afternoon)
It’s after 6pm. Jack says selamat malam (good evening / night)
John says sampai jumpa (see you later)
Source: Accessibility Toolkit Version 3, September 2009. Section 5 - Flash and Accessibility.
Last updated: 24 October 2010(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.
(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.
Enter your email address to subscribe or unsubscribe from the eGov What's New mailing list.
Please enter email address of the person you wish to send this page to.