fixing-accessibility

Link error messages to fields using aria-describedby, set aria-invalid on invalid inputs, mark required fields so they are announced, and associate helper text with inputs. Critical errors should use aria-live regions so screen readers announce them.

Add an aria-label or aria-labelledby attribute to the button so assistive technologies announce its purpose, and mark the inner SVG icon with aria-hidden="true" so it is treated as decorative.

Critical categories come first: accessible names for all interactive controls, full keyboard access with visible focus, and focus trapping with restoration in dialogs. Semantics, forms, and announcements follow at high and medium priority.

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

Avoid large rewrites or UI library migrations unless requested. The guidance favors minimal, targeted fixes and explicitly avoids adding ARIA where native semantics already work or refactoring unrelated code.