Ajax Live Regions: ReefChat Using the Fire Vox Screen Reader as a Case Example
Peter Thiessen, Charles Chen · 2007 · Proceedings of the 2007 International Cross-Disciplinary Conference on Web Accessibility (W4A) · doi:10.1145/1243441.1243448
Summary
This paper presents ReefChat, an accessible Ajax chat application, and Fire Vox, an open-source screen reader extension for Firefox, as a proof-of-concept for WAI-ARIA live regions — one of the earliest practical demonstrations of this then-nascent specification. The authors frame the core problem: traditional assistive technologies treat web pages as linearisable content, but Ajax applications break this assumption by inserting new content in arbitrary locations with complex interactions. While AT can detect DOM mutation events, it cannot understand what those events mean in context because Ajax applications use custom widgets built from divs, spans, and CSS rather than standard HTML elements with known behaviors. ARIA live regions solve this by allowing developers to mark page regions that can be dynamically updated, specifying how assistive technology should announce changes. ReefChat demonstrates this with chat messages placed inside a live region marked with aria:role="log", aaa:live="polite", relevant="additions", and atomic="false" — meaning new messages are spoken individually and in sequence as they arrive, without interrupting the user. The user list uses similar markup with relevant="additions removals" to announce both arrivals and departures.
Key findings
The paper documents a significant gap in ARIA support at the time: Fire Vox was the only screen reader supporting live region markup, while JAWS and Window-Eyes supported ARIA widget roles but not live regions — highlighting how the ARIA specification was being adopted piecemeal across different AT products. ReefChat introduced an innovative per-user message filtering feature: left and right arrow keys allow users to cycle through messages from specific users, addressing the practical problem of busy chat rooms where messages from many users become overwhelming — a usability challenge unique to serial audio access. The heading-based navigation in Fire Vox (Ctrl+Shift+H) provided shortcuts to the four main UI sections (Messages, Compose Message, User Listing, Options), demonstrating how proper heading structure enables efficient non-visual navigation even in application-like web interfaces. The authors proposed a "chatMessage" ARIA role (inheriting from the Group role) that did not yet exist in the specification, illustrating how practical implementation drove ARIA's evolution. The chat was designed with plans to convert it into a Dojo toolkit widget, anticipating the importance of accessibility in Ajax toolkits.
Relevance
This paper represents a pivotal moment in web accessibility history: one of the first working demonstrations that ARIA live regions could make real-time web applications accessible to screen reader users. The chat application use case was ideal for demonstrating live regions because it has an inherently asynchronous, continuously updating interface where the user's focus (the input field) is separate from where new content appears (the message log) — the exact scenario that traditional screen readers could not handle. The per-user message filtering feature demonstrates thoughtful accessible UX design that goes beyond basic ARIA compliance to address real usability challenges specific to non-visual interaction. For modern developers, the paper illustrates core live region concepts (polite vs. assertive priority, additions vs. removals tracking, atomic vs. non-atomic updates) that remain the foundation of accessible dynamic content today. The fragmented ARIA support across screen readers documented here — with different AT products implementing different parts of the specification — is a pattern that persists and that developers must still account for.
Tags: ARIA · live regions · web accessibility · AJAX · Web 2.0 · screen readers · dynamic content · keyboard accessibility · instant messaging · open source
Standards referenced: WAI-ARIA