Daily emails so far...

Accessibility isn't something you install from a code repository.

The Web Almanac found that strong accessibility laws improve scores, but enforcement and commitment matter more.

In Issue 83 of Access Denied, Gary vibe codes an inaccessible app.

The Web Almanac highlights the benefits and the dangers of artificial intelligence in web accessibility.

The promises made by overlay vendors are largely bullshit.

The Web Almanac 2025 highlights increase usage of ARIA roles and attributes across the board.

Half of web images still lack proper alt text in 2025 and the filename as description problem still won't die.

Proper error handling makes or breaks form accessibility.

The Web Almanac 2025 shows small improvements for form accessibility.

In Issue 82 of Access Denied, Gary thinks Lighthouse scores are enough for accessibility.

98% of websites include page titles, but 2% still don't bother with this basic HTML element.

Only 24% of websites have skip links, but maybe that's not the real problem.

Proper heading structure matters for accessibility and SEO, yet 41% of sites still get it wrong.

Two-thirds of websites now remove focus indicators, making them unusable for keyboard users.

Why contrast ratios matter, what 4.5:1 means and how to fix issues.

Accessible writing means using language your audience understands, without unnecessary complexity or jargon.

In Issue 81 of Access Denied, Gary thinks common patterns are good even when they're bad.

The Web Alamanc shows a 1% improvement in accessibility scores, but is that meaningful?

The 2025 Web Almanac's Accessibility chapter is live.

Most accessibility decisions don't need snap judgments, but time, team input and strategic thinking.

Automated accessibility testing tools aren't meant to replace expertise.

Accessibility is a values problem, not a resource problem.

Bad ideas don't become good simply because they're the only ideas on the table.

In Issue 80 of Access Denied, Gary prioritised accessibility for Q2 of the year.

When it comes to accessibility and making your website or product accessible, what are you trying to avoid?

While snow shoveling rules vary, accessibility responsibility always falls on you.

The cutting edge is painful. HTML, accessibility and listening to users aren't.

Even good intentions in the planning phase lead to inaccessible products.

Relationships, health, freedom and web accessibility all require you to pay the full cost up front.

When it comes to accessibility in product development, paying debt later costs way more than building it in from the start.