Accessibility and WCAG Basics
Overview
Accessibility means a page works for people using a keyboard, screen reader, or reduced vision, not only a mouse and unimpaired sight. WCAG AA is the specific, testable standard this curriculum targets: semantic HTML, alt text, keyboard operability, visible focus states, and sufficient color contrast.
Why It Matters
Accessibility problems are easy to miss because they are usually invisible to whoever built the page: a sighted person using a mouse will never notice a missing focus outline or a missing alt attribute. That is exactly why it needs a deliberate check rather than an assumption that the page is fine because it looks fine.
Core Principles
- Semantic HTML is the foundation. Real buttons, real headings, and real landmarks give assistive technology the structure it needs, before any ARIA attribute is added.
- Every interactive element needs a visible focus state. Keyboard users rely on it to know where they are on the page.
- Contrast and alt text are testable, not subjective. A contrast ratio either meets 4.5:1 or it does not; an image either has a meaningful alt attribute or it does not.
Interactive Demo
alt="" (missing)
Ceramic mug, hand glazed, holds 12oz.
Click "Check next issue" to find the first accessibility problem on this sample card.
Common Mistakes
- Removing the default focus outline for aesthetic reasons without replacing it with an equally visible alternative.
- Leaving an image's alt attribute empty or filling it with the file name instead of a description of its content or purpose.
- Treating accessibility as a final audit step instead of checking it alongside color and typography decisions as they are made.
Related Concepts
- Color and Contrast: contrast ratio is one of the checks in this demo.
- Typography: line length and line height also affect readability for low-vision users.
- Forms and Inputs: accessible forms depend on the same keyboard and labeling principles.
Used In Templates
Demonstrated directly in the Documentation Site, Blog and Article Site, Personal Resume and CV Site, Internal Dashboard and Admin Panel, and FAQ and Help Center Page templates; see docs/PRD.md section 13.2.
Summary
Accessibility is a set of specific, checkable requirements, not a vague goal: semantic elements, visible focus states, meaningful alt text, and sufficient contrast. Because these problems are invisible to whoever is not affected by them, they need a deliberate check, not an assumption.