A Web Design Framework for Improved Accessibility for People with Disabilities (WDFAD)
Rehema Baguma, Jude T. Lubega · 2008 · Proceedings of the 2008 International Cross-Disciplinary Conference on Web Accessibility (W4A) · doi:10.1145/1368044.1368077
Summary
This paper from Makerere University in Uganda proposes WDFAD (Web Design Framework for Improved Accessibility for People with Disabilities), a developer-oriented framework that repackages web accessibility requirements according to the three components of web applications: content, navigation, and user interface. The authors argue that existing accessibility guidelines like WCAG, while comprehensive, are difficult for developers to integrate into their workflows because they are not organized around how developers actually think about and build web applications. Drawing on the Non-Functional Requirements (NFR) Framework from software engineering, WDFAD represents accessibility as a system of primary goals (content accessibility, navigation accessibility, user interface accessibility) decomposed into actionable sub-goals. The framework identifies 16 accessibility requirements derived from WCAG and research literature, classifies each according to which web application components it affects, and provides justifications for why each requirement matters for blind users specifically. A key analytical contribution is mapping these requirements into overlapping sets using a Venn diagram, revealing which requirements are "global" (affecting all three components) versus "local" (affecting only one or two), and identifying critical sub-goals whose failure would compromise accessibility across multiple components simultaneously.
Key findings
The framework reveals that user interface accessibility is the "super primary goal" — it has the most sub-goals (13 of 16) and the most unique requirements not shared with other components. Navigation follows with 11 sub-goals, while content has the fewest at 8. Four requirements are critical because they cut across all three components: text-only version, text alternatives for visual elements, meaningful content structure in source code, and design for device independence. Failing to meet any of these four affects the accessibility of content, navigation, and user interface simultaneously. On a pairwise basis, navigation and user interface share the most requirements, making them the most closely linked components. The analysis also reveals that there are more shared (global) sub-goals than individual (local) ones across the three primary goals, meaning that many accessibility improvements yield benefits across multiple application components simultaneously. This finding suggests that developers can achieve significant accessibility gains by prioritizing the shared requirements first. The authors note that the shift from static HTML to interactive Web 2.0 applications has made user interface accessibility increasingly important, which is reflected in WCAG 2.0 incorporating more interactivity-focused guidelines.
Relevance
WDFAD addresses a persistent gap in accessibility practice: the disconnect between how accessibility standards organize requirements and how developers actually build applications. While WCAG organizes by principles (POUR) and guidelines, developers think in terms of content, navigation, and UI components — the practical building blocks of their work. The framework's insight that most accessibility requirements are global rather than local has a practical implication that remains relevant: addressing shared requirements first provides the highest return on investment. Coming from Makerere University in Kampala, Uganda, this paper also represents an important Global South perspective on web accessibility, where limited developer training and resources make developer-friendly frameworks particularly valuable. Although the paper focuses primarily on blind users and does not cover the full range of disabilities, its component-based approach to organizing accessibility requirements anticipates modern patterns like design system accessibility and component-level accessibility testing that have become standard practice.
Tags: web accessibility · accessibility framework · blind users · screen readers · web design · developer tools · non-functional requirements · Uganda · Global South accessibility
Standards referenced: WCAG 1.0 · WCAG 2.0 · Section 508