Real talk: The WCAG isn't premium content

1 minute read

You know what pisses me off?

The way some treat the WCAG like some fancy add-on package they can buy later. If the budget allows.

"Oh, we'll tackle accessibility in Phase 2." "Let's get the MVP out first, then worry about compliance."

I call BS on that!

WCAG isn't a wishlist of nice-to-have features. It's not an optional DLC you can purchase when you're feeling generous. Yes, it's technical standards, but frankly, it should be as fundamental to your development process as making sure your site actually loads.

You wouldn't dream of shipping a car without seatbelts, airbags or functioning brakes. "Sorry, we'll get the seat belt out in v2! You drive safe now!"

So why the hell do you think it's acceptable to launch websites that actively exclude people? Every time you ship without proper alt text, keyboard navigation or colour contrast, you're essentially building barriers and slapping "DISABLED PEOPLE KEEP OUT" signs on them.

WCAG compliance isn't premium content. It's the bare minimum of not being a complete dick to your users.

Sent on

Did you enjoy this bite-sized message?

I send out short emails like this every day to help you gain a fresh perspective on accessibility and understand it without the jargon, so you can build more robust products that everyone can use, including people with disabilities.

You can unsubscribe in one click and I will never share your email address.