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 it has an accessible name, and mark the decorative SVG icon with aria-hidden="true". Every interactive control must expose a meaningful name to assistive technologies.

Fix critical categories first: accessible names for controls, full keyboard access, and focus management in dialogs. Then address high-priority semantics and form errors before medium-priority items like contrast and motion preferences.

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

Avoid large rewrites or refactoring unrelated code, and do not migrate UI libraries unless requested. The approach favors minimal, targeted fixes and established accessible primitives over custom widget behavior.