Enabling an Accessible Web 2.0
Becky Gibson · 2007 · Proceedings of the 2007 International Cross-Disciplinary Conference on Web Accessibility (W4A 2007) · doi:10.1145/1243441.1243442
Summary
This keynote paper from IBM's Becky Gibson examines the accessibility challenges created by the emergence of Web 2.0 and the technologies being developed to address them. Written at a pivotal moment in web history, the paper describes how the shift from static HTML pages to dynamic, interactive web applications built with JavaScript, Ajax, and DHTML was creating significant barriers for people with disabilities. While the basic web had become reasonably accessible through WCAG 1.0 and assistive technology support for standard HTML elements, Web 2.0 introduced complex interface components like tree controls, tabbed interfaces, floating dialogs, and rich text editors built from generic div and span elements that conveyed no semantic information to assistive technologies. The paper presents the then-emerging Accessible Rich Internet Applications (ARIA) specification as the primary solution, explaining how ARIA roles, states, and properties could add semantic metadata to these custom components so screen readers and other assistive technologies could interpret them. Gibson also surveys the accessibility API landscape across operating systems, including Microsoft Active Accessibility (MSAA), IAccessible2 (an IBM-developed extension donated to the Linux Foundation), Mac Accessibility API, and Linux Accessibility Toolkit (ATK), noting that MSAA was insufficient for Web 2.0's advanced features.
Key findings
The paper identifies three key technical solutions for accessible Web 2.0: ARIA semantics for role and state information, the tabindex attribute for keyboard focus management (allowing any element to receive focus, not just links and form controls), and live regions for communicating dynamic page updates to assistive technologies. Gibson documents the practical implementation of ARIA in the Dojo toolkit, which was among the first JavaScript frameworks to integrate ARIA support into its widget library. She also describes several testing tools emerging at the time: IBM's Rule-based Accessibility Validation Environment (RAVEN), an Eclipse-based tool using aspect-oriented programming for automated accessibility testing, and the University of Illinois's Functional Web Accessibility Evaluator (FAE), which evaluated coding techniques rather than simply checking for tag attributes. A critical insight is that accessibility needed to be built into the toolkits and frameworks developers were using, achieving "accessibility by default" rather than requiring each developer to implement accessibility individually.
Relevance
This paper is a valuable historical document capturing the moment when web accessibility practice had to fundamentally evolve beyond static HTML. Gibson's vision of "accessibility by default" through toolkit integration proved prescient — modern frameworks like React, Angular, and Vue all incorporate accessibility features, and ARIA has become a cornerstone of web accessibility practice. The paper's discussion of IAccessible2 and accessibility API evolution provides important context for understanding how browser-to-assistive-technology communication works today. For practitioners, it serves as a reminder that each wave of web technology innovation (Web 2.0 then, single-page applications and web components now) requires renewed attention to accessibility. The challenges Gibson identified — dynamic content updates, custom widget semantics, keyboard navigation — remain relevant nearly two decades later.
Tags: ARIA · Web 2.0 · JavaScript · DHTML · accessibility APIs · keyboard navigation · screen readers · toolkits · dynamic content
Standards referenced: WAI-ARIA · WCAG 1.0 · Section 508 · MSAA · IAccessible2