Tuesday, 22 January 2008

Flash Accessibility Options


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.

Automatic Accessibility Transcoding for Flash Content

Source: Sato, D., Miyashita, H., Takagi, H. and Asakawa, C. (2007): Automatic Accessibility Transcoding for Flash Content. ACM SIGACCESS Conference on Assistive Technologies, pp. 35-42 Accessed via ACM Digital Library http://portal.acm.org on 22 January 2008.

  • "Flash andDHTML, is some of the most pervasive content because of itsvisual attractiveness to the sighted majority."
  • "Such visually rich content has been causing severe accessibility problems, especially
    for people with visual disabilities."
  • "For Flash content, the kinds of accessibility information necessary for screen readers is not usually provided in the existing content."
  • "Flash and Dynamic HTML (DHTML)are representatives of these rich content types, and they appeal tosighted people with their fascinating audio and visual presentations."
  • "Although Flash was only a format for simple vector-based animations in 1996, over the following decade, itwas enhanced to support high quality audio, scripts with user interactions, built-in GUI components, powerful image processing,and now streaming video support is the latest enhancement. Flashis no longer an animation format, but rather a platform forproviding interactive content, and the Flash player is installed inover 98% of the computers in the world as of March 2007"
  • "...content owners using Flash are under pressure to support accessibility."
  • Section 508 of the US Rehabilitation Act - Implemented in 2001 requested improved accessibility of governmental websites.
  • As a result an accessibility framework was designed and implemented into Flash Player and authoring tools. This is based on Windows accessibility, API and MSAA (Microsoft Active Assessibility), used by a wide range of assistive technologies with screen reading capabilities.
  • Therefore, if an author of Flash uses the updated authoring tools then screen readers can use Flash through MSAA.
  • "this architecture requires content creators to study methods to make content accessible and to apply those methods in their daily authoring tasks."
  • "...it has been very difficult to make the Flash content
    accessible compared to other formats such as HTML and PDF"

The following three aspects explain the difficulty in making Flash accessible:

  • "Flash content itself is used to create visually intuitive contentusing animations and movies. It is not static and the content is dynamically created and frequently changed in response to the users’ operations and the content’s own timeline. Accessibility enabling
    methodologies for such rich Internet applications are not mature."
  • "There is no tool to evaluate accessibility for existing Flash content. Currently the only method is to use ascreen reader, which imposes a heavy burden on developers."
  • Flash content developers are unfamiliar with accessibility problems. Based on our preliminary investigation [4], most of them do not even know that Flash has accessibility features."

  • "Due to these problems, not even the basic accessibilityenablement requirements have been met in existing Flash content,requirements such as alternative text, controlled reading order, orwidgets role information (e.g. for buttons)"
  • "Unaddressed, Flash accessibility will continue to decrease, and screen reader users
    will be left out of the richer Internet experiences forever. It is very important to develop new technologies to help both developers and screen reader users."

Possible Subject Ideas

There are a number of possible subjects I wish to pursue, as follows:

1. Flash accessibility
2. Adaptive interface design (web)
3. Creating the ulimate usable website using gaze recognition software.

The mind map below shows how these subjects could be applied.

First Post

My name is Richard Hamer and I am currently undertaking an MSc in Multimedia Computing at the University of Central Lancashire.This blog has been created for the purposes of logging the progress of my Masters Evaluation.