WCAG Guidelines
Also Known As
WCAG
WCAG 2.2
accessibility guidelines
POUR
TL;DR
Web Content Accessibility Guidelines — the international standard defining how to make web content accessible to people with disabilities, organised into three conformance levels (A, AA, AAA).
Explanation
WCAG 2.2 (current) is organised under four principles — POUR: Perceivable, Operable, Understandable, Robust. Level A is minimum accessibility; AA is the legal requirement in most jurisdictions (ADA, EN 301 549, AODA); AAA is aspirational. Key AA requirements include 4.5:1 colour contrast, keyboard navigability, focus indicators, alt text for images, captions for video, and no keyboard traps. WCAG 3.0 is in development with a different conformance model.
Diagram
flowchart TD
WCAG[WCAG 2.1] --> POUR[4 Principles]
POUR --> P[Perceivable<br/>text alternatives<br/>captions colour contrast]
POUR --> O[Operable<br/>keyboard accessible<br/>no seizure triggers]
POUR --> U[Understandable<br/>readable predictable<br/>input assistance]
POUR --> R[Robust<br/>compatible with<br/>assistive technologies]
subgraph Levels
A[Level A - minimum]
AA[Level AA - standard target]
AAA[Level AAA - enhanced]
A --> AA --> AAA
end
style P fill:#1f6feb,color:#fff
style O fill:#238636,color:#fff
style U fill:#d29922,color:#fff
style R fill:#6e40c9,color:#fff
style AA fill:#238636,color:#fff
Common Misconception
✗ Accessibility is for a small minority of users — 15% of the world population has a disability; additionally, accessible design benefits all users (captions, keyboard navigation, high contrast).
Why It Matters
WCAG AA compliance is a legal requirement in many jurisdictions — lawsuits under ADA and similar legislation target inaccessible websites, and failure to comply exposes organisations to significant liability.
Common Mistakes
- Only testing with automated tools — axe and Lighthouse catch ~30% of accessibility issues; manual testing and screen reader testing are required.
- Colour contrast only — passing contrast ratios while failing keyboard navigation or missing alt text still fails WCAG.
- Not testing with actual assistive technology — NVDA (Windows) and VoiceOver (Mac/iOS) reveal issues automated tools miss.
- Overlaying widgets (AccessiBe) as a WCAG compliance solution — they do not provide true compliance and have been criticised by the disability community.
Code Examples
✗ Vulnerable
<!-- Multiple WCAG failures:
<div onclick="submitForm()">Submit</div> <!-- Not keyboard accessible, no role -->
<img src="logo.png"> <!-- Missing alt text -->
<input type="text" placeholder="Email"> <!-- No label element -->
<p style="color: #999">Fine print</p> <!-- Likely fails 4.5:1 contrast -->
✓ Fixed
<!-- WCAG AA compliant:
<button type="submit">Submit</button> <!-- Natively keyboard accessible -->
<img src="logo.png" alt="Company Logo"> <!-- Descriptive alt text -->
<label for="email">Email address</label>
<input type="email" id="email" name="email" autocomplete="email" required>
<p style="color: #595959">Fine print</p> <!-- 7:1 contrast ratio — AAA -->
References
Tags
🤝 Adopt this term
£79/year · your link shown here
Added
15 Mar 2026
Edited
22 Mar 2026
Views
28
🤖 AI Guestbook educational data only
|
|
Last 30 days
Agents 0
No pings yet today
No pings yesterday
Perplexity 10
Amazonbot 7
Google 3
Ahrefs 2
Also referenced
How they use it
crawler 20
crawler_json 2
Related categories
⚡
DEV INTEL
Tools & Severity
🟠 High
⚙ Fix effort: High
⚡ Quick Fix
Target WCAG 2.1 AA — it requires: text contrast 4.5:1, all functionality keyboard accessible, no content flashing >3Hz, and all non-decorative images having alt text
📦 Applies To
any
web
🔗 Prerequisites
🔍 Detection Hints
Colour contrast below 4.5:1; images without alt text; form inputs without labels; keyboard inaccessible interactive elements
Auto-detectable:
✓ Yes
axe
lighthouse
wave
color-contrast-analyser
⚠ Related Problems
🤖 AI Agent
Confidence: Medium
False Positives: Medium
✗ Manual fix
Fix: Medium
Context: File