Affordable Web Accessibility: A Case for Cheaper ARIA
Yury Puzis, Yevgen Borodin, Andrii Soviak, Valentyn Melnyk, I. V. Ramakrishnan · 2015 · Proceedings of the 12th International Web for All Conference (W4A) · doi:10.1145/2745555.2746657
Summary
This paper argues that the primary barrier to web accessibility is not technical limitations but the high cost of implementing WAI-ARIA, the W3C accessibility specification for rich internet applications. The authors systematically analyze why ARIA implementation is expensive by walking through a detailed example: making a simple login dialog accessible requires at least 10 distinct implementation steps spanning HTML, ARIA markup, JavaScript, server-side code, and CSS — involving technical writers, web developers, web designers, and accessibility specialists across the website's entire lifecycle. The paper identifies four key cost drivers: accessibility logic crosses programming language boundaries (HTML, ARIA, JavaScript, CSS), programming paradigm boundaries (declarative vs. imperative), role boundaries (multiple specialist teams), and organizational boundaries (webpage developers, browser vendors, and screen reader developers all with different priorities). The authors argue that these complexities explain why only the most popular, well-resourced websites achieve reasonable accessibility, and why screen reader support for ARIA remains incomplete years after the specification was finalized. They contend the web's accessibility could be greatly improved through an "affordable" version of ARIA.
Key findings
The paper identifies specific technical complexities that inflate ARIA implementation costs. For speech feedback, web developers cannot explicitly define what a screen reader should say — they can only assign labels through numerous competing methods (aria-label, aria-labelledby, aria-describedby, HTML label tags, placeholder attributes, alt text, etc.), leaving neither party certain of the actual user experience. For content visibility, there are numerous CSS and HTML methods to hide content visually (display:none, opacity, z-index, viewport positioning, etc.) but the aria-hidden attribute is used inconsistently, so screen readers must guess what should be perceivable. For dynamic content, ARIA live regions are inadequate for modern web applications that are essentially "live" at the scale of the entire page. For navigation, virtual cursor control is split between three parties (user-agent, webpage, browser), with browser focus manipulation serving as an imperfect hack. The authors propose two remedies: (1) move the ARIA Role Model into HTML itself to eliminate the HTML/ARIA duopoly, and (2) extend ARIA to let developers explicitly define user-agent behavior (speech patterns, cursor movement) conditional on element roles and states, removing the need for JavaScript in accessibility logic.
Relevance
This paper provides an unusually frank economic analysis of why web accessibility adoption remains low despite decades of standards development. For accessibility practitioners advocating within organizations, understanding the cost argument is essential — accessibility is often rejected not because developers are unaware of ARIA but because implementation is genuinely expensive relative to perceived return. The detailed breakdown of a simple login dialog's accessibility requirements is a powerful illustration for training purposes. While the specific proposals (merging ARIA roles into HTML) have not been fully realized, the underlying cost analysis remains valid. The paper's suggestion to extend ARIA's utility to situationally impaired users (e.g., people temporarily unable to look at screens) to create economies of scale foreshadows current arguments about the curb-cut effect and universal design benefiting all users. Modern frameworks like React and Angular have partially addressed the cost problem through built-in accessibility patterns, but the fundamental complexity of the ARIA specification and its cross-boundary implementation requirements persist.
Tags: WAI-ARIA · web accessibility · screen readers · web development · accessibility economics · web standards · accessibility cost
Standards referenced: WAI-ARIA · WCAG 2.0