A Web Compliance Engineering Framework to Support the Development of Accessible Rich Internet Applications
Carlos A Velasco, Dimitar Denev, Dirk Stegemann, Yehya Mohamad · 2008 · Proceedings of the 2008 International Cross-Disciplinary Conference on Web Accessibility (W4A 2008) · doi:10.1145/1368044.1368054
Summary
This paper from Fraunhofer Institute introduces Web Compliance Engineering as a new discipline within Web Engineering, and presents a software framework (imergo) designed to support accessibility compliance for Rich Internet Applications. The authors argue that existing evaluation and repair tools had significant limitations: poor crawling of large or dynamic sites, lack of project management capabilities, inability to validate against published grammars for mobile devices, limited localization for different policy environments, no support for dynamically generated DOM elements, and no integration with reporting languages like EARL. Their framework addresses these gaps by treating compliance as an ongoing quality process rather than a one-time evaluation. The system uses Semantic Web technologies to define an ontology describing compliance environments at three layers of abstraction — syntactic, semantic, and implementation-specific — enabling reuse of test cases across different policy environments and standards. The architecture follows a Service Oriented approach with seven main components: Business Manager, Resource Supplier (with crawler, parser, and extractors), Analyzer, Reporting Manager, Presentation layer, Persistence Manager, and Configuration Manager. The framework supports rule sets for WCAG 1.0, WCAG 2.0 (then in Working Draft), and mobileOK Basic Tests 1.0, using the Unified Web Evaluation Methodology (UWEM) to address testability issues in WCAG 1.0.
Key findings
The paper identifies a critical shift in Web 2.0 where the traditional separation between content authors and end users was dissolving, as users increasingly became content providers through wikis, blogs, and social platforms. This meant compliance tools needed to serve not just developers but also end users creating content within RIAs — for example, guiding a user to properly describe uploaded images. The framework was designed to support five distinct use cases: enterprise content management systems (authoring-time feedback), RIA end users (accessible content guidance), RIA developers (ARIA role and state integration), web site commissioners (auditing and quality monitoring), and usability experts conducting manual testing. A key architectural decision was using ontologies to semantically describe compliance environments, allowing the same framework to adapt to different national policy requirements — important for multinational organizations facing non-uniform accessibility legislation worldwide. The system had moved beyond research prototype and was being tested in real production environments and large-scale web portals.
Relevance
This paper captures an important moment in the evolution of accessibility tooling, when the field was transitioning from simple page-level checkers to integrated compliance platforms that could handle the complexity of dynamic web applications. The concept of Web Compliance Engineering — treating accessibility not as a one-off audit but as a continuous quality assurance process embedded in development workflows — remains highly relevant today. The multi-stakeholder approach (developers, content authors, auditors, end users) anticipated how modern accessibility platforms like Deque, Level Access, and Siteimprove would evolve. The paper also highlights a persistent challenge: the gap between accessibility policy adoption by governments and actual implementation by the industry, which the authors attributed partly to the limitations of existing tools. For organizations managing accessibility across multiple jurisdictions with varying requirements, the ontology-based approach to mapping different policy environments remains an instructive model.
Tags: web compliance engineering · rich internet applications · accessibility testing · semantic web · EARL · software engineering · quality assurance · automated testing
Standards referenced: WCAG 1.0 · WCAG 2.0 · WAI-ARIA · EARL · UWEM