Accessibility

Aria UI treats accessibility as a default, not an add-on. The library follows the WAI-ARIA Authoring Practices Guide (APG) and aims to make semantics, keyboard support, and focus behavior feel built in from the start.

Accessibility model

Aria UI leans on three layers of accessibility:

• native HTML whenever the browser already solves the pattern
• WAI-ARIA roles, states, and properties for richer composite widgets
• predictable focus and keyboard patterns so every interaction has a non-pointer path

Keyboard support

Keyboard support should feel invisible: Tab reaches controls in a sensible order, arrow keys move through composite widgets, Escape backs users out of transient UI, and Enter or Space activates the expected action. That consistency helps keyboard users, screen reader users, and anyone working without a mouse.

Focus management

Focus is a contract. Dialogs, menus, popovers, and other floating layers should move focus intentionally, preserve context while open, and return users to a sensible place after dismissal. Clear visible focus states make the interface easier to scan for everyone.

What we optimize for

• semantic markup before custom behavior
• robust keyboard paths for every interactive pattern
• visible focus states that are easy to spot
• predictable return focus after transient surfaces close