LAB
Everything here is a research direction or an in-progress idea, not a shipped product. Accessibility, AI-assisted engineering and developer experience are the current areas of focus.
A research direction for developer tooling that surfaces accessibility issues earlier in the IDE, before code reaches review: missing alt text, unlabeled fields, unclear accessible names, keyboard-interaction gaps, non-semantic elements and common ARIA misuse.
AccessLens is a concept, not a released product. It grew directly out of the "shift accessibility left" thinking explored in my writing.
Working notes on using Cursor, Claude, ChatGPT, OpenAI Codex, GitHub Copilot and Gemini responsibly inside a senior engineering workflow: where they accelerate work, and where they still need a human decision.
Patterns for building component libraries where accessible behavior - keyboard interaction, focus management, ARIA - is a property of the component API, not an integration afterthought for consumers.
Exploring how static analysis and linting can catch a meaningful subset of accessibility issues at commit time, complementing - not replacing - manual and assistive-technology testing.