Course contentsShow
← Web Development
Lesson 1041 of 2,98218. Accessibility FundamentalsFree lesson

Decision Framework: Native vs ARIA

Apply a systematic approach to determine whether a feature needs ARIA or semantic HTML alone.

Decision Framework: Native vs ARIA

What you'll learn: A systematic checklist for deciding whether to use semantic HTML alone or add ARIA attributes.

The Core Decision Process

Think of this like choosing between buying something pre-made versus customizing it. Native HTML is the ready-made solution—if it fits your needs perfectly, use it. ARIA is the customization layer for when the built-in option falls short.

Here's your step-by-step framework:

1. Can native HTML do the job? Check if a standard element exists: <button>, <nav>, <main>, <select>, etc. If yes, stop here. Use the native element without ARIA.

2. Is the native element almost right? Sometimes a <button> or <input> does 90% of what you need but lacks one piece of information (like a toggle's expanded state). Add only the minimal ARIA to fill the gap: aria-expanded, aria-pressed, etc.

3. Is this truly custom behavior? Building a tabs widget, tree view, or date picker? No native equivalent exists. Now ARIA roles, states, and properties become necessary.

4. Test without ARIA first Before adding ARIA, test with a screen reader. You might discover the semantic structure already works. ARIA should solve a real problem, not be added "just in case."

5. Progressive enhancement check Would removing ARIA break core functionality? If yes, reconsider your approach. ARIA should enhance, not replace, working HTML.

Quick Decision Tree

  • Does native HTML exist? → Use it
  • Is native HTML incomplete? → Add minimal ARIA
  • Is this a complex custom widget? → Build with ARIA
  • Unsure? → Test without ARIA first

Key Takeaway: Default to semantic HTML; add ARIA only when native elements don't exist or need specific enhancements. When in doubt, test with assistive technology before deciding.