A framework for filtering web accessibility guidelines
Rehema Baguma, Roger G. Stone, Jude T. Lugega, Th. P. van der Weide · 2009 · Proceedings of the 2009 International Cross-Disciplinary Conference on Web Accessibility (W4A) · doi:10.1145/1535654.1535663
Summary
This paper presents a framework for organizing and filtering web accessibility guidelines such as WCAG according to four contexts of use, addressing the widely acknowledged problem that WCAG guidelines are difficult for their target audience to navigate and apply. The framework proposes four filtering dimensions: web page component (content, navigation, and user interface), type of disability (visual, hearing, physical, cognitive), level of use (understanding guidelines vs. applying techniques), and document structure (preliminary content, per-guideline view, and peripheral references). These dimensions can be combined — for example, a developer could filter to see only techniques for making navigation accessible to blind users. The framework was implemented as a prototype using CSS and JavaScript to dynamically show and hide portions of the WCAG 1.0 guidelines document based on user selections, presenting a navigation frame with the four context dimensions alongside the full guidelines content. The approach is inspired by the recognition that different stakeholders need different views: IT managers need compliance overviews, developers need technical implementation guidance, and procurement officers need requirements checklists.
Key findings
The prototype was tested with 20 web developers and 10 IT managers using scenario-based tasks. For developers, tasks completed using the filtered framework guidelines were accomplished with less difficulty than those using raw WCAG 1.0. When given a choice in Task 4, 18 out of 20 developers preferred the framework guidelines, citing easier navigation and the ability to control the amount of information displayed. Developers noted the framework was easy to navigate and that grouping guidelines by content, navigation, and disability type made it easier to find relevant advice quickly. In contrast, raw WCAG 1.0 was described as difficult to navigate with no control over information volume. For IT managers, Task 1 (using the framework) was completed with less difficulty than Task 2 (using raw guidelines), with none failing to complete using the framework compared to raw guidelines. The evaluation confirmed two key usability aspects identified by Colwell and Petrie: the organization allows discovery of required advice, and the interface for accessing the guidelines is usable. The CSS and JavaScript filtering approach proved more efficient than database-driven designs used by some other accessibility guideline tools.
Relevance
This paper addresses a persistent challenge in accessibility practice: WCAG guidelines, while comprehensive, remain difficult for many practitioners to navigate and apply effectively. The "one view for all" presentation of WCAG does not serve the varied needs of its diverse audience — developers, managers, testers, and procurement specialists all need different entry points and levels of detail. The four-dimensional filtering framework offers a practical model that could be applied to current WCAG versions and other accessibility standards. The finding that 90% of developers preferred filtered guidelines over raw WCAG reinforces the need for better accessibility guidance tools. Modern accessibility resources like the W3C's "How to Meet WCAG" quick reference with its filtering options reflect this same insight. For organizations training staff on accessibility, this research supports the practice of creating role-specific views of accessibility requirements rather than presenting the full specification to all stakeholders. The work also highlights the value of presenting guidelines organized by disability type, which WCAG 2.0 intentionally moved away from in favor of technology-neutral principles — a design choice that may improve generality but can make it harder for practitioners to understand which users are affected by specific requirements.
Tags: accessibility guidelines · WCAG usability · context of use · guideline filtering · developer tools · accessibility education
Standards referenced: WCAG 1.0 · WCAG 2.0