You ship the entire product.

When roles collapse, so does judgement. Maybe you're a founder. Maybe you're a team of one, or AI has turned you into someone who takes ideas all the way to production. There's no accessibility team to review your work... so YOU need accessibility judgement in your toolbox, alongside everything else.

A couple of pieces to start with

• Pair programming with AI

  You finish faster but maybe understand less. Here's the instruction set I'm experimenting with.

• Design & development: the yin & yang of web accessibility

  A flawed design coded perfectly is just as bad as a brilliant design coded poorly.

• How to be a keyboard accessibility super hero

  Keyboard access is the fastest, cheapest accessibility test you can run — and the foundation almost everything else builds on.

What I write about for building

• Accessibility when you're the whole team
• What to get right first
• Making AI build accessibly
• Shipping fast without shipping barriers

I'd love to hear more about what you're looking to learn next. What's one thing you're looking for that would change things in your work tomorrow? Reach out with your stories and messages — I'm always happy to learn what would be most useful to you.