When should ARIA attributes be used with button elements?

When should ARIA attributes be used with button elements?

• A. Use div elements with role='button' for flexibility.
• B. Use button or input type='button' semantics; ARIA attributes only when native semantics can’t convey state or role; do not override semantics.
• C. Always use ARIA attributes on all elements.
• D. ARIA should replace native button semantics for better control.

Answer: (B)

Buttons have built-in accessibility: they respond to keyboard activation and are announced as buttons by assistive technologies. You should use ARIA attributes only when the native button semantics can’t convey the needed state or role. If you need to reflect something about the button’s state (like a toggle), you can add ARIA attributes such as aria-pressed, but you still rely on the native button for proper keyboard support and default behavior. Avoid substituting a real button with a div and role="button," because that requires extra work to implement keyboard interactions and focus behavior, and it may still be less reliable across AT. ARIA is a helpful supplement, not a replacement for native semantics, and it shouldn’t be applied to every element.

Buttons have built-in accessibility: they respond to keyboard activation and are announced as buttons by assistive technologies. You should use ARIA attributes only when the native button semantics can’t convey the needed state or role. If you need to reflect something about the button’s state (like a toggle), you can add ARIA attributes such as aria-pressed, but you still rely on the native button for proper keyboard support and default behavior. Avoid substituting a real button with a div and role="button," because that requires extra work to implement keyboard interactions and focus behavior, and it may still be less reliable across AT. ARIA is a helpful supplement, not a replacement for native semantics, and it shouldn’t be applied to every element.