Combining SADIe and AxsJAX to Improve the Accessibility of Web Content
Darren Lunn, Simon Harper, Sean Bechhofer · 2009 · Proceedings of the 2009 International Cross-Disciplinary Conference on Web Accessibility (W4A) · doi:10.1145/1535654.1535672
Summary
This paper from the University of Manchester presents a prototype system that combines two accessibility approaches — SADIe and Google's AxsJAX framework — to improve web content access for visually impaired screen reader users. SADIe (Semantic Annotation for Document Interfaces and Environments) uses semantic annotations added to a website's Cascading Style Sheet (CSS) to describe the roles that page elements play (e.g., navigation menu, main content, summary). The key insight is that visual rendering in CSS closely corresponds to the designer's intended role for each element — sighted users can infer a list of links is a menu from how it looks, so annotating the CSS captures this semantic information. Previously, SADIe used these annotations to restructure pages by reordering the DOM for sequential screen reader output. In this new prototype, the same CSS annotations instead generate Content Navigation Rules (CNR) for Google's AxsJAX framework, which dynamically injects WAI-ARIA statements into web pages. This allows screen reader users to navigate static web content using simple keyboard shortcuts ('n' for next content chunk, 'p' for previous, 'm' for menu, 's' for summary) in an application-like manner rather than reading linearly through the page. The system operates as a proxy between the browser and server, with annotations stored in a shared repository.
Key findings
The prototype demonstrated technical feasibility using CNN as an example, where three CSS elements (cnnNavigation, cnnHeaderRightCol, cnnHeaderLeftCol) were annotated to identify the menu, summary, and main content respectively. A single CSS annotation propagated across all pages sharing that stylesheet, providing high scalability with minimal annotation overhead. The paper references a significant finding from prior research by Petrie et al. that evaluated 100 websites with 51 disabled users: of 585 observed problems, 45% were not violations of any WCAG 1.0 checkpoint — motivating the need for approaches beyond guidelines compliance. The SADIe-AxsJAX combination addressed this by enabling users to skip directly to relevant content with single key presses rather than navigating through banners, advertisements, and other peripheral elements. The approach also demonstrated SADIe's flexibility, as the same annotations could drive different transcoding outputs (DOM restructuring or ARIA injection). A key practical advantage was that web designers could enhance accessibility by simply annotating CSS roles without needing to understand AxsJAX or ARIA technologies directly.
Relevance
This paper represents an important moment in the evolution of web accessibility techniques — the transition from static page restructuring to dynamic ARIA-based interaction. The core ideas remain highly relevant: that CSS carries implicit semantic information about page structure, that screen reader users benefit from application-style keyboard navigation over linear reading, and that accessibility tools should lower the barrier for web designers rather than requiring deep technical expertise. The finding that 45% of accessibility problems fell outside WCAG checkpoints remains a cautionary reference point for practitioners who rely solely on automated compliance testing. While the specific technologies (AxsJAX, the SADIe proxy model) have been superseded by native ARIA support in modern browsers and screen readers, the paper's vision of consistent keyboard-driven content navigation anticipated patterns now common in screen reader usage. The proxy-based transcoding approach also foreshadowed later browser extension strategies for accessibility remediation.
Tags: screen readers · web accessibility · transcoding · ARIA · CSS · assistive technology · visual impairment · Web 2.0 · keyboard navigation
Standards referenced: WAI-ARIA · WCAG 1.0 · WCAG 2.0 · XHTML