Answer
WAI-ARIA defines roles, states, and properties that expose custom interface semantics to assistive technology. • ARIA supplements a host language such as HTML; it does not create keyboard behavior by itself. • Use native HTML whenever it already provides the required semantics and behavior. • ARIA roles and properties must follow the authoring rules for the chosen HTML element and widget pattern.
💡 Simple Example
<button type="button" aria-expanded="false" aria-controls="help-panel">Help</button><div id="help-panel" hidden><p>Contact support.</p></div>
⚡ Quick Revision
ARIA adds accessibility semantics to custom interfaces, but native HTML remains the first choice.