AccessiWeb Methodology
summary
AccessiWeb reduces WCAG 2 into concrete, testable rules so auditors answer one question one answer per criterion; it produces printable criteria and a label identification used in certification. It targets specific browser + assistive‑technology pairings (legacy IE combinations mentioned) and recommends cautious adoption of HTML5 features only when tested with referenced AT. France-wide monitoring finds only 3% of public sites publish WCAG conformance, and the methodology exists to increase consistent, auditable compliance.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:36MeAc: monitoring web accessibility in Europe
- 9:10What are the problems?
- 10:50Accessi Web : a collaborative answer to these problems
- 11:59Ensuring an operational understanding of WCAG 2
- 14:42Providing a methodology used in a certification process
- 17:04Weakness and Strength
- 20:40A question of compromise
related talks
32mAccessibility Conformance Testing (ACT)
33mWeb accessibility in practice, more than just WCAG
50mAccessibility by Everyone (and for Everyone)
40mAccessible Websites - A Prolegomenon
22mAccessibility in Practice
01h 03mAccessibility: Making your websites more inclusive
15mAccess-what? why and how. A11Y for all
45mAccessibility: Why You Should Learn About WCAG