WCAG 2.1 Level AA Explained in Plain English

1. Perceivable - Can People See/Hear Your Content?

Information must be presented in ways users can perceive. If someone can't see images, they need text descriptions. If they can't hear videos, they need captions.

2. Operable - Can People Use Your Website?

All features must work for everyone. People who can't use a mouse must be able to navigate with a keyboard. Nobody should feel rushed or encounter seizure-triggering content.

3. Understandable - Is Your Content Clear?

Your website should be predictable and help users avoid mistakes. Forms should clearly explain what's needed, and error messages should be helpful.

4. Robust - Does It Work with Assistive Technology?

Your website must work with screen readers and other tools people with disabilities use. This means using proper HTML and following web standards.

Rule: Every image needs a text description

Why: Blind users can't see images, so screen readers read the description

Example: Instead of just showing your city logo, add alt="City of Springfield logo"

Exception: Decorative images can be marked as decorative

Rule: Text must stand out from the background (4.5:1 contrast ratio)

Why: People with low vision need strong contrast to read

Example: Black text on white = good. Light gray on white = bad

Also: Don't use color alone to convey information (like red = required)

Rule: Everything must work without a mouse

Why: Some people can't use a mouse due to motor disabilities

Test: Unplug your mouse. Can you still use your website with just Tab and Enter?

Common issue: Dropdown menus that only work on hover

Rule: Use headings in order (H1, then H2, then H3)

Why: Screen readers use headings like a table of contents

Example: Don't jump from H1 to H3, skipping H2

Think: Headings are for structure, not just making text big

Rule: Every form field needs a label

Why: Screen readers need to announce what each field is for

Example: Don't just have a box - label it "Email Address"

Also: Clearly mark required fields and provide helpful error messages

Rule: Videos need captions, audio needs transcripts

Why: Deaf users can't hear audio content

Note: Auto-generated captions are okay if they're accurate

Also: Provide audio descriptions for important visual information

Rule: Link text must describe where it goes

Why: Screen readers can list all links on a page

Bad: "Click here" or "Read more"

Good: "Download 2024 Budget Report" or "Apply for Building Permit"

Rule: Give users enough time or let them extend time

Why: Some users need more time to read or complete tasks

Example: If your form times out after 15 minutes, warn users and let them extend

Myth: "We need to make a separate accessible version"

Truth: No! Make your main website accessible. Separate versions often become outdated and are considered discriminatory.

Myth: "Accessible websites are ugly and boring"

Truth: Accessibility doesn't limit design. You can have beautiful, modern websites that are also accessible. Major brands prove this every day.

Myth: "We'll fix it after launch"

Truth: Building accessibility from the start is 10x cheaper than retrofitting. Plus, you're legally liable from day one.