Functional Web Accessibility Techniques and Tools from the University of Illinois
Jon Gunderson, Hadi Bargi Rangin, Nicholas Hoyt · 2006 · Proceedings of the 8th International ACM SIGACCESS Conference on Computers and Accessibility (Assets '06) · doi:10.1145/1168987.1169049
Summary
This paper presents two complementary tools developed at the University of Illinois at Urbana-Champaign for helping web developers create functionally accessible websites: the CITES/DRES Functional Web Accessibility Best Practices and associated evaluation tools. The authors argue that Section 508 and WCAG 1.0 provide principles for accessible design but lack specific markup implementation requirements, leaving developers unsure how to actually implement accessibility. The CITES/DRES Best Practices fill this gap by providing concrete markup requirements for common HTML elements and web page design, organised into five categories: Navigation and Orientation (using structural HTML to title pages, assign headings, define navigation bars, and label form controls), Text Equivalents (providing text representations of audio, video, and graphic content, particularly ALT attributes on images), Scripting and Automation (addressing device independence and accessibility in dynamic web applications built with scripting and XML technologies), Styling (using CSS to separate styling from structure, enabling users to restyle content for their perceptual needs), and Standards (using HTML, XHTML, CSS, DOM, and other W3C standards to ensure interoperability across assistive technologies).
Key findings
The Functional Accessibility Evaluation (FAE) Tool analyses web pages against the CITES/DRES best practices and produces summary and detailed reports on accessible markup usage. Unlike many evaluation tools that simply generate lists of manual checks, FAE uses rules to test each functional accessibility feature and links results to best practice documentation. However, the authors note FAE cannot determine whether a resource is accessible or not — it estimates functional accessibility and flags areas needing attention. The Mozilla/Firefox Accessibility Extension provides an in-browser tool that makes hidden accessibility information visible: it reveals information on headers, labels, and other structural elements that the graphical rendering typically does not disclose. Features include the ability to disable CSS styling, in-line tag styling, and table-based layout; apply user style sheets; toggle high contrast options; test for text equivalents on non-text content; and provide keyboard navigation commands. For dynamic web applications, the extension is being extended to support DHTML accessibility features being developed by the W3C. Both tools are free and open source, lowering the barrier to accessibility testing.
Relevance
This paper captures an important moment in the evolution of web accessibility tooling — the recognition that guidelines alone are insufficient without specific implementation techniques and verification tools. The five-category organisation of best practices (navigation, text equivalents, scripting, styling, standards) remains a useful framework for thinking about web accessibility even though the specific tools have evolved. The emphasis on functional accessibility — evaluating whether markup actually supports assistive technology interaction rather than just checking for the presence of attributes — was ahead of its time and anticipated the approach now common in modern tools like axe and Lighthouse. For practitioners, the paper reinforces that accessibility evaluation requires both automated analysis and manual review, and that making invisible accessibility structures visible to developers is key to adoption.
Tags: web accessibility · automated testing · accessibility evaluation · WCAG · Section 508 · browser extension · best practices · dynamic HTML
Standards referenced: Section 508 · WCAG 1.0 · UAAG · W3C DOM · W3C DHTML Accessibility Roadmap