MIPAW: Modele of a Progressive Implementation of Web Accessibility
Jean-Pierre Villain, Olivier Nourry · 2012 · Proceedings of the International Cross-Disciplinary Conference on Web Accessibility (W4A) · doi:10.1145/2207016.2207045
Summary
This paper presents MIPAW (Modele of a Progressive Implementation of Web Accessibility), a framework for reorganizing WCAG criteria into a user-centric, phased implementation model. The authors, who lead the AccessiWeb reference list — the most widely implemented WCAG-based methodology in France — argue that while WCAG 2.0 is technically mature, its organizational structure creates significant barriers to practical adoption in web projects. The A conformance level alone accounts for roughly 75% of the total accessibility workload, making it appear as an "impassable wall" to project teams. Furthermore, WCAG's technical focus disconnects accessibility from user experience concerns, reducing it to a checklist of technical constraints rather than a design priority. MIPAW addresses this by restructuring WCAG criteria around the concept of "access to information" — the idea that certain criteria are fundamentally about whether users can access content at all, while others improve the quality of that access. The model was developed through the AccessiWeb GTA (Workgroup on Accessibility) with support from 16 leading French digital accessibility companies. An expert survey asked both technical experts and expert users to classify each AccessiWeb criterion by its impact on access to information, producing a statistical basis for the restructuring.
Key findings
The expert survey revealed that "access to information" is a highly structuring concept within WCAG: 45 criteria (across all three levels) were rated by over 85% of experts as impacting access to information, while 29 criteria had zero impact on information access. Critically, user impact was found to be uncorrelated with access to information — a criterion with no information access impact could still have strong or weak user impact. This insight led to MIPAW's four-phase implementation model: (1) Secure access to information — ensure presence of essential technical devices and alternative content (e.g., alt attributes on images, video transcripts); (2) Guarantee access to information — ensure relevance and quality of those devices and alternatives; (3) Improve user impact — address criteria with strong impact on user experience (e.g., color contrast, HTML parsing); (4) Improve user experience — handle criteria with weaker but still meaningful impact (e.g., decorative images, images of text). The model preserves WCAG's A/AA/AAA level structure entirely, overlaying it with a user-needs-driven progression rather than replacing it.
Relevance
MIPAW offers a pragmatic answer to a question many organizations face: where do we start with WCAG compliance, and how do we prioritize when resources are limited? The standard WCAG conformance levels (A, AA, AAA) are not designed as implementation phases — they group criteria by severity, not by logical order of implementation. MIPAW's reframing around "access to information" gives project managers a more intuitive progression: first ensure content is reachable at all, then ensure it's meaningful, then improve the broader experience. This approach aligns accessibility work with quality assurance practices that web teams already understand, potentially reducing the perception of accessibility as an isolated technical burden. The model's main limitation is that it remained in incubation at publication, with collaborative workgroups still forming. The paper presents the theoretical framework and survey validation but no case studies of the model applied to real projects. Still, the underlying insight — that WCAG needs a user-centric implementation layer on top of its technical structure — remains a relevant challenge for the accessibility field.
Tags: WCAG implementation · progressive enhancement · accessibility strategy · quality assurance · accessibility evaluation · organizational accessibility
Standards referenced: WCAG 2.0