Accessibility as Engineering Practice

<h2> The Problem: LLMs Generate Plausible Garbage </h2> <p>When you ask Claude or GPT to build a modal dialog with "proper accessibility," you'll get <code>role="dialog"</code>

<p>Ask a team what they built for accessibility and you will usually hear about screen reader support. Ask how far it got and the answer is normally a partial implementation that

<p><strong>The problem</strong></p> <p>Every time I found an accessibility issue in a PR review, the same thing happened: tab out to the WCAG docs, figure out the right fix, come

<p>Color contrast is one of the most commonly overlooked accessibility requirements in web development — and one of the easiest to fail accidentally. You pick a beautiful grey

<p>In Europe, web accessibility became mandatory in June 2025 under the <strong>European Accessibility Act (EAA)</strong>. But the EU doesn't define <em>how</em> to test — each

<p>From a high-level perspective, frontend engineering functions as the translation layer between raw, machine-readable data and human interaction through User Interfaces (UI) and

<p>The pattern that pushed me to build this: I'd fix an accessibility issue, ship, and a<br /> few deploys later it would quietly come back. A contrast tweak undone here, a

<p>Software engineering is not just about writing code that works. It’s about writing code that survives change, scale, and time.</p> <p>After working on multiple systems—from