If you’ve ever heard someone mention “making a website accessible” and thought, “That’s a developer thing, right?”—you’re not alone.
Accessibility often gets shoved into the tech bucket: coding problems, screen reader fixes, lawsuits, overlays. But at the heart of it is something much simpler (and much more human): Can people actually use your website?
That’s where WCAG comes in.
Let’s break it down—plain language only. No coding background required. (Just because I spent 3 years doing development work a decade ago doesn’t mean I remember it all, so let’s keep it…shall we say…accessible).
First, What Is WCAG?
WCAG stands for the Web Content Accessibility Guidelines.
It’s a global standard that explains how to make websites and digital content accessible to people with disabilities. These guidelines are written and maintained by the W3C—the same group that helps define the web itself.
There have been a few versions over the years:
- WCAG 2.0 (2008)
- WCAG 2.1 (2018) – most widely used today
- WCAG 2.2 (2023) – recently finalized
- WCAG 3.0 is in development and will eventually be the next major shift
Don’t let the version numbers scare you. WCAG is built on four core principles:
The world wide web should be Perceivable, Operable, Understandable, and Robust.
(That’s the POUR framework—more on that another day.)
For now, here’s the key takeaway:
WCAG tells you how to build websites that work for real people in real life.
Okay, But I’m Not a Developer. Why Should I Care?
Let’s get real. Most websites aren’t built by teams of accessibility experts. They’re made by:
- Small business owners using WordPress, Wix or Squarespace
- Designers building from templates
- Marketers managing content in a CMS
- Freelancers juggling design, dev, and copywriting
And here’s the thing: you can break WCAG without ever touching a line of code.
Here are a few examples:
- Uploading an image without alt text? WCAG violation.
- Choosing low-contrast colors that make text hard to read? WCAG violation.
- Using vague link text like “click here”? WCAG violation.
- Forgetting to label a form field? WCAG violation.
None of that requires code to fix. But all of it impacts your users—and could leave you vulnerable to legal risk.
WCAG Isn’t Just About Disability—It’s About Usability
Yes, WCAG is focused on making content accessible to people with disabilities. But here’s the secret every great UX designer knows:
When you design for accessibility, you improve the experience for everyone.
- Clearer text benefits people reading on mobile or while multitasking
- Descriptive links help people skim faster
- Logical structure helps Google index your site
- Keyboard navigation helps super tech-savvy users and people with limited mobility
- Captions help people in loud environments—or watching silently at work
Accessibility isn’t a “nice to have.” It’s smart design.
So… How Do I Know If My Site Meets WCAG?
You don’t need to memorize the guidelines. You just need to start checking for patterns.
Here’s a quick, non-technical checklist based on WCAG principles:
- Can users see your content clearly? (Color contrast, text size, alt text)
- Can they navigate your site without a mouse? (Keyboard access, skip links)
- Can they understand what to do? (Clear instructions, descriptive buttons)
- Does your site work reliably on different devices and with assistive tech?
If the answer is “no” to any of those, there’s room for improvement—and real benefit waiting on the other side.
The Legal Angle (Yes, You Should Know This Part)
In the U.S., WCAG is widely used as the benchmark for ADA compliance. That means:
- If your website isn’t accessible, it could be considered discriminatory
- You can be sued—even if you didn’t know better
- There’s no official checklist in the law, but courts almost always point to WCAG
Industries most at risk: healthcare, legal, education, finance, retail, and any business that sells or serves online.
But again: compliance is the floor, not the goal.
Good user experience and accessibility are what help your business thrive.
Bottom Line: WCAG Is Everyone’s Job
You don’t need to be a developer to care about accessibility.
- If you write content, design pages, upload images, or publish blog posts—you impact accessibility.
- If you work with clients who want their websites to convert—you should understand how accessibility helps.
- If you run a business—you should care that people can actually use what you’re putting into the world.
WCAG is a tool, not a burden. It’s a guide to making better websites—for everyone.
Want a Plain Language WCAG Checklist?
This is exactly what my book Practical UX is all about. It walks you through how to spot accessibility and usability issues with a simple, repeatable process—no coding background required.
Grab your copy of Practical UX and start making your website (or your clients’) more accessible, effective, and human-friendly today. www.practicaluxbook.com
Leave a Reply