Daily emails so far...

Forget the "put yourself in their shoes" exercises in accessibility.

Certification is cool and all, but it's hollow without genuine care for people.

In Issue 70 of Access Denied, Gary gave Sarah a random email where to send accessibility tickets.

Being the bridge between support requests and implementation teams means getting caught in the middle.

Teams are constantly "researching" accessibility instead of just fixing the obvious shit that's broken.

Create guidelines, document decisions and build a knowledge base is essential for accessibility.

The gap between good testing and good products is culture.

Specialisation builds expertise, but isolation kills collaboration.

When product teams create silos, accessibility falls through the cracks.

In Issue 69 of Access Denied, Gary gives a presentation on accessibility, but knows nothing about it.

Instead of convincing people accessibility matters, build it first and make them work to remove it.

Stop thinking accessibility is just about blind people and screenreaders.

You don't need everyone to be an accessibility expert. You need everyone to know their part.

Automated tests catch the obvious stuff. Here are 5 things they can catch that actually matter to people.

Accessibility is like starting a fire. It works better when you don't overwhelm everyone with massive changes.

Accessibility specialists often end up as "complexity managers," whose job is to make sense of unnecessarily complicated systems.

In issue 68 of Access Denied, Gary values accessibility but can't find time to prioritise it.

It doesn't matter why you make your site accessible as long as it gets done.

Companies mandate yearly training, everyone gets a certificate, but nothing changes. True for security, GDPR or accessibility.

Who's actually responsible for accessibility in the team?

Automated tests catch the obvious stuff. Here are 5 things they miss that actually break products for people.

Ignoring accessibility means building on a shaky foundation.

What is the best case and the worst case scenario when you don't fix your accessibility problems?

In Issue 67 of Access Denied, Gary thinks early adopters of a product is a representative sample.

Make things simpler to understand and problems can become easier to fix.

We made dropdowns unnecessarily complex.

Accessibility starts with people.

Do you absolutely need more than what automated testing gives you?

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.