ARIA for Progressive Enhancement
You'll learn how to layer ARIA attributes onto already-functional HTML to enhance the experience specifically for screen reader users without breaking basic functionality.
The Core Philosophy
Progressive enhancement means building your interface with solid, semantic HTML first—ensuring it works for everyone—then adding ARIA to make the experience even better for assistive technology users. Think of it like building a house: HTML is your foundation and walls (must be structurally sound), and ARIA is the paint and decorative trim (makes it nicer, but doesn't hold up the building).
Your baseline must always be functional without ARIA. A button should be a <button>, a form should use proper <label> elements, and navigation should use semantic landmarks. Only after confirming everything works with keyboard and screen readers should you consider adding ARIA.
Why This Approach Works
When you add ARIA as an enhancement layer, you're giving screen readers additional context that might not be obvious from HTML alone. For example, a working tab interface built with native buttons can be enhanced with role="tablist", aria-selected, and aria-controls to announce the tab pattern explicitly.
If you start with <div role="button">, you've already failed—you're using ARIA as a replacement for HTML, which violates the first rule of ARIA. Instead, start with <button>, verify it works, then add ARIA properties if they genuinely add value.
This approach protects you: if ARIA is misconfigured or unsupported, the underlying HTML still functions. You haven't created barriers; you've only added helpful hints.
Key Takeaway: Build fully functional interfaces with semantic HTML first, test them thoroughly, then add ARIA attributes only where they provide clear additional context for screen reader users—never as a substitute for proper HTML.