Authentic conversations so far...

Including accessibility into the definition of done will create accountability and all but eliminate issues in the future.

Too many people in a meeting kill any productive discussions. Here are three ways to deal with them.

Meeting the web content accessibility guidelines doesn't guarantee your product is usable or inclusive.

Empathy is essential if you want to create an accessible and inclusive product.

In Issue 47 of Access Denied, Gary thinks accessibility issues introduced with AI can be fixed with just a better prompt.

Accessibility work can be mentally exhausting when others don't listen.

Legacy code is just an excuse to not make a product accessible.

Building team accountability for tackling web accessibility debt requires setting measurable goals.

BS meetings that start and end late disrupt everyone's day, but especially impact those with accessibility needs.

Why do we complain about web accessibility and how can we provide solutions to bring change.

Prioritise accessibility into your process to have fewer urgent issues afterwards by dealing with the important bits up front.

In Issue 46 of Access Denied, Gary thinks adding "make it accessible" to the AI prompt is enough.

After all these years, I'm still learning about web accessibility and that feels pretty damn special.

AI won't fix your inaccessible product and it's not worth trying.

The first step to build team accountability is to assign clear roles so that every accessibility requirement has an owner.

The lack of an agenda or a vague agenda is the firs sign of a BS meeting.

Making invisible consequences visible can transform product design and how you make choices in accessibility.

Help developers ship accessible websites by giving them reliable tools, match those to their skills and help them prioritise effectively.

In Issue 45 of Access Denied, Gary thinks semantic HTML is outdated and useless if you want to make art.

Accessibility work is not without its challenges, but there is magic in creating solutions that genuinely improve lives.

If all your markup is comprised of divs, you should stop calling yourself a web developer.

Why is team accountability important for chipping away at accessibility debt and four ways to build it into your process.

What are the most common issues with meetings about web accessibility?

Instead of perfect accessibility, aim for continuous improvement. Perfect accessibility doesn't exist.

An accessibility sprint can and will deliver short-term improvements, but without ongoing attention, new issues will creep in.

In Issue 44 of Access Denied, Gary thinks using placeholders for form labels is a great user experience.

Instead of debating accessibility with so-called experts and other stubborn stakeholders, try to work with them to get things done.

WCAG isn't a choose-your-own-adventure book. Read it and stop pretending it’s "ambiguous" because you don't like the rules.

Wrap up for making smart trade-offs when considering accessibility debt.

Soul-crushing inefficiency as a web product team pretends to care about accessibility while accomplishing absolutely nothing.