Daily emails so far...

You don't need permission to work on accessibility because the majority of accessibility improvements are about how you build the stuff.

Get org-level support for accessibility without turning your practical wins into empty strategy documents.

In Issue 66 of Access Denied, Gary thinks having an accessibility strategy solves everything.

Accessibility is a system-level problem, but system-level solutions without unit-level action are useless.

Stop making accessibility harder than it needs to be. Use semantic HTML elements and get accessibility built in instead of fighting ARIA.

10 tips for a sustainable accessibility strategy, from focusing on people to automated tools, feedback loops and the impact of your choices.

Lab data tells you what's broken. Field data tells you if users can actually use your site.

Every decision in product development is an accessibility decision. We just don't always realise it.

Shift from "accessibility as compliance checkbox" to "accessibility as following natural user behaviour."

In Issue 65 of Access Denied, Gary thinks just adding any alt text to images solves accessibility.

Simple accessibility hacks rarely fix long-term use experience and process problems.

A code horror story with a giant pull request that fixes accessibility.

Weighing up outsourcing accessibility vs building in-house expertise? There are compelling reasons for each approach.

Say no to endless discussions and meetings about meetings, and instead reach clear outcomes and ship accessible products.

The people who never say "I don't know" are accessibility's biggest problem.

Screen readers aren't just for people with visual disabilities.

In Issue 64 of Access Denied, Gary thinks that copying Google will lead to success.

Accessibility shouldn't be an afterthought, but with legacy systems, that's often exactly what it becomes.

Stop copying big companies without understanding why their design works.

How can you prioritise accessibility debt to work first on what needs your immediate attention?

Wrapping up the series on BS meetings.

The user research you've been doing might have some pretty massive blind spots.

Casual feedback from trade shows and networking events can mislead your accessibility product decisions.

In Issue 63 of Access Denied, Gary thinks keyboard navigation isn't needed because his team use mice.

I'm done explaining accessibility basics to teams who aren't ready to listen.

Disregarding keyboard navigation because you haven't met people who rely on keyboards is just lazy.

How to convince your team to invest their time in fixing accessibility debt in your product.

If the end result of a meeting is another meeting, you should not have had the meeting.

Some people cannot be helped when they're not open minded about accessibility and people with disabilities.

Instead of changing what product owners want, help them get what they already want.