aria-disabled vs disabled Attribute
You'll learn when to use the ARIA aria-disabled state versus the native HTML disabled attribute, and why choosing the right one matters for accessibility.
The Core Difference
Both aria-disabled and the disabled attribute communicate that an element is not currently interactive, but they work very differently under the hood.
The disabled attribute is a native HTML feature that actually prevents interaction. When you add disabled to a button or input, the browser removes it from the tab order, blocks all keyboard and mouse events, and visually styles it as inactive. The element becomes completely inert.
The aria-disabled attribute is purely informational. It tells assistive technologies like screen readers that an element is disabled, but the element remains fully functional—it can still be focused, clicked, and receive keyboard events. You must manually prevent interactions with JavaScript.
When to Use Each
Use disabled when you want the browser to handle everything automatically:
- Form inputs that shouldn't accept input
- Buttons that should be completely inactive
- Standard interactive elements where native behavior is sufficient
Use aria-disabled="true" when you need:
- Custom components where you want to maintain focus order
- Elements that should remain keyboard-navigable but appear disabled
- Situations where you need to explain why something is disabled while keeping it in the accessibility tree
Think of it like a locked door versus a sign saying "closed." The disabled attribute locks the door—nobody can enter. The aria-disabled attribute puts up a sign, but you still need to prevent people from walking through.
Key Takeaway: Use native disabled for standard form controls and let the browser handle behavior automatically; use aria-disabled only for custom components where you need manual control over focus and interaction, remembering you must implement all disabled behavior yourself.