Authentic conversations so far...

Teams that invest in slowly building accessibility skills end up in a better place than those who try to fix everything at once.

In Issue 56 of Access Denied, Gary thinks being first is everything, even without an accessibility strategy.

Speed doesn't matter if you don't know where you're going.

Stop assuming young users don't need web accessibility.

Include accessibility into your existing acceptance criteria to build things right from the start without it feeling like extra work.

BS meetings where you try to educate everyone about everything in accessibility fail miserably.

Accessibility issues aren't side effects. They are what happens when we ignore knowingly problems.

Small compromises can exclude millions of users without anyone planning to.

In Issue 55 of Access Denied, Gary thinks no progress on accessibility means the team is maintaining a consistent standard.

Our job is to write a story that resonates with others and helps them make better choices for accessibility.

Accessibility isn't about technical complexity or resource allocation. It's who you're willing to exclude.

Set specific and measurable goals for accessibility and tie them to existing metrics you already track.

BS meetings that monitor activity aren't the same as making progress. Turn check-ins into actual work sessions.

Treating accessibility as an afterthought costs you customers.

Building accessibility into your web product from day one saves money, time and creates better experiences for all users.

In Issue 54 of Access Denied, Gary thinks it's enough to run an accessibility plugin right before launch.

When web accessibility fails, every small frustration compounds into something much bigger.

Stop blaming accessibility for being a speed bump in your agile process.

Most product teams can make meaningful progress on accessibility debt in 6-12 months.

BS meetings always have the one manager who's all theory and zero accessibility practice.

The only way to learn accessibility is to do the work and build it in your development process.

The 5 hidden rules product owners use to avoid making their products accessible, and what they're really costing you.

In Issue 53 of Access Denied, Gary thinks that AI writes semantic code.

Writing semantic HTML is something you do automatically without really thinking about it.

If you're constantly putting accessibility in the backlog, you'll end up with mountain of technical debt.

Common questions that came up for the series on accessibility debt.

Keep people engaged during meetings to guarantee the best outcomes.

Three quick process changes to tack on accessibility checks to your existing product development workflow.

With the European Accessibility Act in effect, small businesses can think of it as a burden or as an opportunity to build something better.

In Issue 52 of Access Denied, Gary approves the budget for the EAA fines instead of fixing accessibility issues.