Technical Questions About WCAG and Accessibility
The technical implementation of accessibility regularly raises questions: what exactly are the WCAG? How is testing done? And are automated tools sufficient? The following questions address the technical aspects of accessible web development.
- What are the WCAG and which version applies? The Web Content Accessibility Guidelines (WCAG) are the international standard for accessible web content, published by the World Wide Web Consortium (W3C). The current version is WCAG 2.2, published in October 2023. EN 301 549 references WCAG 2.1 AA as the minimum standard; we recommend WCAG 2.2 AA as the current state of the art.
- What does WCAG 2.2 AA conformance mean? WCAG defines 78 success criteria at three levels: A (basic), AA (recommended) and AAA (optimal). Conformance level AA encompasses all A and AA criteria, meaning 56 of 78 criteria. AA is the internationally recognized standard and is referenced by EN 301 549 as the minimum requirement.
- Are automated accessibility tools sufficient? No. Automated tools like axe-core and Lighthouse detect only 30 to 50 percent of all accessibility issues (Source: WebAIM 2024). Complex barriers like inconsistent screen reader output, incomprehensible error messages or poor keyboard accessibility require manual expert evaluation and testing with assistive technologies.
- What is the difference between ARIA and semantic HTML? Semantic HTML (headings, landmarks, lists, forms) conveys meaning directly through native HTML elements. ARIA (Accessible Rich Internet Applications) supplements missing semantics for interactive widgets like tabs, modals and dropdown menus. The first rule of ARIA: do not use ARIA if a native HTML element can do the job (Source: W3C WAI).
- Does accessibility work with JavaScript frameworks? Yes. React, Vue, Angular and Svelte are fully compatible with accessible development. Challenges lie in client-side routing, dynamic content and focus management. With the right patterns and libraries these challenges are solvable. More on our accessible web development page.
- What are accessibility overlays and why don't they work? Accessibility overlays are JavaScript widgets intended to retroactively adapt a website. Leading accessibility experts and disability associations explicitly warn against these tools: they do not solve the structural problems in the source code and can even worsen the experience for people with disabilities. The BFSG requires structural accessibility in the source code (Source: W3C WAI, Overlay Fact Sheet).