Accessibility at Early Stages: Insights from the Designer Perspective
Adriana Martín, Alejandra Cechich, Gustavo Rossi · 2011 · Proceedings of the International Cross-Disciplinary Conference on Web Accessibility (W4A) · doi:10.1145/1969289.1969302
Summary
This paper addresses a fundamental imbalance in web accessibility practice: while many tools exist to help developers evaluate accessibility after implementation, very few support designers in building accessibility into web applications from the start. The authors propose a method for modelling accessibility requirements at early design stages using aspect-oriented software development (AOSD) principles combined with WCAG guidelines. Their approach treats accessibility as a "crosscutting concern" — a quality requirement that spans multiple components of a system rather than being confined to one module. The method works through a four-stage process integrated into the Object-Oriented Hypermedia Design Method (OOHDM), a mature web engineering methodology. First, designers identify accessibility requirements using User Interaction Diagrams (UIDs) with "integration points" that mark where accessible interaction is essential. Second, these requirements are organised using Softgoal Interdependency Graphs (SIGs) that map WCAG checkpoints to two branches: user technology support (assistive technology compatibility) and user layout support (interface presentation). Third, a supporting tool discovers crosscutting accessibility concerns and applies them to abstract interface models. Finally, concrete accessible HTML is generated through aspect "weaving" that injects accessibility properties into the user interface code.
Key findings
The authors demonstrate through a university student login page case study that accessibility requirements naturally exhibit crosscutting behaviour — the same requirement (such as associating labels with form inputs) must be applied repeatedly across multiple interface elements, creating "scattering" and "tangling" problems that aspect-oriented design is well suited to solve. Their supporting tool uses the Observer design pattern implemented through AspectJ to automatically inject accessibility properties (labels, keyboard shortcuts via accesskey, tab ordering via tabindex) into HTML output when interface models are saved. The approach produces five "association tables" that map abstract interface widgets to concrete HTML elements and their corresponding WCAG checkpoints, enabling reuse across projects. The authors also report that migrating from WCAG 1.0 to WCAG 2.0 required only straightforward redefinitions to their association tables, suggesting the approach is resilient to standards evolution. They candidly acknowledge trade-offs: model-driven approaches add bureaucracy, time, and learning effort, and the approach requires prior knowledge of WCAG terminology.
Relevance
This paper makes a compelling case for "shift-left" accessibility — addressing it during design rather than retrofitting after development. The authors identify a knowledge gap that persists today: developers lack accessibility expertise while accessibility specialists lack programming skills, and most organisations only consider accessibility at the end of the development cycle when remediation is costly. For organisations building web applications, the key takeaway is that accessibility requirements can and should be treated as reusable architectural concerns modelled early in design, not as an afterthought requiring expensive rework. While the specific AOSD tooling may be academic, the underlying principle — that accessibility patterns recur across projects and can be systematically captured and reapplied — is directly applicable to modern component-based development and design systems.
Tags: accessible design · software engineering · aspect-oriented design · web engineering · model-driven development · user interface design · WCAG compliance · shift-left accessibility
Standards referenced: WCAG 1.0 · WCAG 2.0