fixing-accessibility

Run a review of the file against the accessibility rule set, which reports each violation with the exact snippet, why it matters, and a concrete code-level fix. Critical issues like accessible names, keyboard access, and focus management are fixed first.

Icon-only buttons must have an accessible name via aria-label or aria-labelledby so screen readers can announce their purpose. Decorative icons inside labeled controls should be marked aria-hidden.

Dialogs must trap focus while open, set initial focus inside, restore focus to the trigger on close, and close on Escape. Opening a dialog should also not scroll the page unexpectedly.

Prefer native elements like button, a, and input over role-based hacks, since they provide built-in semantics and keyboard behavior. Only add aria when native semantics cannot solve the problem, and include all required attributes for any role used.

It is not suited for large-scale UI rewrites or migrating component libraries, since it enforces minimal targeted fixes. For complex widgets like comboboxes, prefer established accessible primitives over custom behavior.