Tuesday, 22 January 2008

Key Points

1. Flash is well known to produce visually appealing and attractive software.

2. Perceived as having huge accessibility problems

3. Not usually good for the visually impaired (e.g. screen reading software, lack of alternative text for buttons, hypertext links, widget roles)

4. Since Flash was first created in 1996, its interactive features (GUI, video streaming, audio etc.) have increased considerably, reflected in it's high usage throuhout the world.

5. Huge pressure for content owners to make Flash accessible (screenreading companies)

6. As a result of Section 508 of the US Rehabilitation Act, which required more accessibility of governmental websites, Flash improved its authoring software and player to make it more accessible. Using MSAA (Microsoft Active Accessibility) Flash can now be read by screen readers. However, this is largely dependent on the Flash author making use of this feature when publishing.

7. Still very difficult to make Flash accessible compared to HTML. This is due to the following reasons:
a. As it is a rich internet application and not static (animations, content changing due to interactivity etc.) accessibility methods in this field are still in their infancy.
b. Accessibility testing software and evaluation tools are currently not available. In fact using a screen reader is the only mechanism available at present
c. Flash content developers are unfamiliar with accessibility issues.
As a result of this Flash does not meet the current accessibility requirements.

8. If developers continue to ignore accessibility issues in Flash then accessibility will decrease.

No comments: