Authentic conversations so far...

Measuring web accessibility is easy. Measuring it right isn't.

Bad ARIA doesn't make your site more accessible. It makes it more confusing.

Real accessibility work lives in the awkward conversations, the pushback and the decisions that create friction.

The goal isn't to have all the answers but to stay open enough to change.

In Issue 99 of Access Denied, Gary thinks a gut feeling is enough to test for accessibility.

Saying "I don't know" feels like failure, but in accessibility it might be the most honest thing you can say.

Most teams don't lack the time for accessibility, but rather a decision that makes it non-negotiable.

Nobody wants to be the person who blocks a Friday ship. That's who I am sometimes.

The worst part in working in web accessibility is being the last person in the room.

The best part in working in web accessibility is when nobody needs me.

Shipping small, consistent improvements beats waiting until you get it perfect.

In Issue 98 of Access Denied, Gary wants to prioritise a task force over fixing accessibility issues.

Most web accessibility problems are fixed at the wrong time, which is why they cost more.

There's a big difference between "not yet" and "never." And then there's the team that never had the accessibility conversation at all.

Accessibility fixes sit in a backlog because nobody's attached a number to them that anyone recognises.

Accessibility audits measure compliance, not experience.

Fixing accessibility issues one by one is slow, expensive and never quite done.

Accessibility keeps getting the leftover hours.

In Issue 97 of Access Denied, Gary changes the accessibility project name because it tests better.

Accessibility fails because nobody with budget approval wants it badly enough.

What do to and what not to do in accessibility statements

Don't strip out every technical word in your accessibility statement.

You can't claim your site is fully accessible on the accessibility statement.

How do you explain the known accessibility issues in an accessibility statement?

What do you do when someone reaches out on the email from the accessibility statement?

In Issue 96 of Access Denied, Gary blames someone else for the non-existent email address on the accessibility statement.

How much and how often is your website changing should tell you how often to update the accessibility statement.

How do you write an accessibility statement so that people actually read it

Is an accessibility statement required by law?

What is an accessibility statement and who is it for?