Web Accessibility and the problem of exclusively relying on development tools to achieve it.

Abstract

Web accessibility remains poorly implemented despite decades of established guidelines, with studies showing that the vast majority of websites fail to meet basic accessibility standards. This research examines the gap between accessibility requirements and implementation practice by investigating what needs developers have on their tools when complying with the Web Content Accessibility Guidelines (WCAG). Through interviews with content management system developers, users, and individuals with accessibility needs, combined with prototype testing of alternative interface designs, this study reveals that accessibility implementation suffers from a fundamental invisibility problem. Unlike visual design elements that provide immediate feedback, accessibility features operate in a realm largely invisible to content creators, leading to implementations that appear correct but fail real users. Through the formulation of a prototype that tests alternative ways of implementing alt text in a content management system, guidelines emerged that aid users both identify and solve accessibility issues. These guidelines answer the research question by helping developers of content management systems address issues of cognitive load, as well as issues of evaluation and execution to significantly improve implementation accuracy among their users. These are meant to be applied in a meta sense relative to the WCAG, guiding tool designers how to aid their users in adhering to the WCAG by addressing the needs the WCAG puts on its adherers. The study concludes by highlighting limitations of using automated tools when assessing the accessibility of the web, leading to false positives and skewed targets in the development stage. The inclusion of actual users with accessibility needs in throughout the design process being crucial, stressing the complimentary role evaluation tools have as opposed to a sufficient standalone method.