Authentic conversations so far...

Instead of stressing about A/B testing shades of blue, prioritse fixing accessibility.

Wrap up for the product owner's guide to accessibility debt and the past 20 emails.

How can you stop the loudest voices from drowning out accessibility experts in a meeting?

Drop the separate "accessibility ROI" argument and fold it into broader UX improvements where the business case is clearer.

Build accessibility checks into every sprint to stop the spread of inaccessible product features.

In Issue 51 of Access Denied, Gary thinks testimonials that keep interrupting users with screen readers adds to the customer satisfaction.

ARIA live regions have timing issues we can't control and are inconsistent across browsers and assistive technologies.

The whole "we'll get to accessibility later" mentality is nonsense.

Wrap up for building team accountability when considering accessibility debt.

If you need to have small talk in a meeting, keep it small and move on to the agenda.

The real heroes of web accessibility are those who build inclusively from day one, not those who create problems then profit from the fix.

Why keyboard accessibility matters and who relies on a keyboard, plus 5 practical tips to get it right.

In Issue 50 of Access Denied, Gary wants to add a keyboard-mode toggle to solve keyboard navigation.

The Web Almanac is an annual state of the web, including a fascinating chapter on web accessibility.

Pixel-perfect UIs don't guarantee accessible or even usable web products.

Just in time accessibility training is about fixing real issues in real time.

Rehashing the same topics in a meeting is a time waster.

Instead of memorising, focus on understanding the principles behind accessibility guidelines.

What is responsive design, mobile-first and what do they have to do with accessibility?

In Issue 49 of Access Denied, Gary disregards responsive design in accessibility.

Avoid aria-label because it does not work with automated in-browser translations.

Web apps and single page apps still rely on HTML and they still need to be accessible.

Without regular accessibility audits, your accessibility debt will skyrocket.

People who don't review the materials will derail a meeting with basic questions that have been answered already.

Accessible framework components don't guarantee an accessible product.

Introducing a new free email course on practical semantic HTML.

In Issue 48 of Access Denied, Gary thinks web frameworks can take care of accessibility out of the box.

It takes patience to work with developers, designers and product owners in web accessibility.

Developers use frameworks as an excuse not to bother with semantic HTML, but that introduces loads of accessibility issues into products.

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