fixing-accessibility

Link error messages to fields with aria-describedby, set aria-invalid on invalid inputs, mark required fields so they are announced, and associate helper text with inputs. The Skill reviews these patterns and suggests minimal code-level fixes.

Add an aria-label or aria-labelledby attribute to the button so it has an accessible name, and mark the inner SVG as aria-hidden="true" since it is decorative. Every interactive control must expose a name to assistive technology.

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

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

Avoid large rewrites, unrelated refactors, or migrating UI libraries unless requested. The guidance favors minimal targeted fixes and established accessible primitives for complex widgets like menus and comboboxes.