Your judgement is more important than ever.

Getting straight to the point here: I've been helping teams design and build software for 25+ years. The engineers that always rose to the top were the ones that had skills and judgement that others were missing. How do you decide what's worth building and how it gets built? Adding accessibility expertise & judgement can help you stand out.

A couple of pieces to start with

• 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.

• Three types of relationships and what they mean for accessibility

  Explicit, implicit, and content-based: the three kinds of relationships on a page, and why all three have to work together to create a fully accessible experience.

What I write about for engineering work

• Semantics, focus, and state
• Why accessible components still make inaccessible pages
• Testing beyond the automated checker
• Working with designers on accessibility
• Reviewing AI-generated code for accessibility
• Building judgement AI can't replace

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.