Automatic accessibility transcoding for flash content
Daisuke Sato, Hisashi Miyashita, Hironobu Takagi, Chieko Asakawa · 2007 · Proceedings of the 9th International ACM SIGACCESS Conference on Computers and Accessibility (Assets '07) · doi:10.1145/1296843.1296852
Summary
This 2007 paper from IBM's Tokyo Research Laboratory tackles a problem that was acute during the height of the Flash era: the near-total inaccessibility of Flash content to screen reader users. Although Flash had an accessibility framework built on Microsoft Active Accessibility (MSAA), it placed the burden of adding alternative text, widget roles, and reading order entirely on content authors — who, the authors' prior investigation showed, were largely unaware the framework even existed. The result was that most buttons, links, and interactive widgets in Flash movies had no alternative text, no exposed role, or failed to appear in the accessibility tree at all. Rather than wait for authors to remediate their content, the authors built a client-side transcoding proxy that intercepts Flash content between the web server and the Flash player. A lightweight content-loader component (written in ActionScript) injects a repair script that inspects the Flash player's internal object model and rewrites accessibility properties on the fly. The paper focuses on three concrete repair problems: buttons that are silently dropped from MSAA (blank up-frames, _visible=false, HTML-in-text objects); unnecessary buttons exposed by slider widgets and decorative indicators; and the widespread absence of alternative text. Heuristics cover button detection (area and aspect-ratio thresholds), text-to-button association (area overlap ratios), and fallback extraction of ActionScript instance names as labels. The system was evaluated on 28 English and 9 Japanese pages containing over 500 Flash buttons.
Key findings
Across the 23 English pages surveyed, 61% of 428 Flash buttons had no alternative text before repair, and a further 20 buttons were completely invisible to MSAA. After automatic transcoding, 55% of the 282 target buttons (155 buttons) received correct alternative text — 73% of these drawn from nearby text objects already present in the Flash content, and 27% from ActionScript instance names that developers had chosen for their own convenience. All 20 previously invisible buttons were successfully exposed, and 16 of 26 unnecessary buttons (slider handles, volume indicators) were correctly suppressed. Overall, button accessibility on English pages rose from 33% to 69%. A striking secondary finding: Flash's built-in auto-label function was surprisingly ineffective, leaving substantial usable text information untapped — suggesting the same algorithms could be folded directly into the Flash player with significant gains. Japanese pages fared far worse (7% to 16% accessible) because ideographic-character fonts are commonly rendered as images rather than text, eliminating the text sources the repair algorithm relies on.
Relevance
Flash is long dead, but the techniques in this paper remain relevant to anyone building remediation overlays, accessibility-repair browser extensions, or automated alt-text tooling. The core insight — that authoring frameworks which place the entire accessibility burden on developers will systematically fail, and that useful labelling information is often hiding in plain sight within the content itself — applies directly to today's SPAs, canvas-based applications, and component libraries that produce inaccessible output by default. The instance-name heuristic anticipates modern work using DOM identifiers and ARIA inference, and the client-side transcoding architecture foreshadows today's accessibility overlays, with all the same caveats about reliability and false positives. The paper is also a useful cautionary tale: a 55% automatic-repair rate sounds impressive until you realise 45% of buttons still fail, and 'broken by error' cases introduced new inaccessibility. Overlays are not a substitute for accessible authoring, a lesson the field has had to relearn repeatedly.
Tags: flash · transcoding · automatic repair · screen readers · alternative text · visual impairment · assistive technology · web accessibility · MSAA
Standards referenced: Section 508 · WCAG 2.0 · MSAA