fixing-accessibility

You can fix accessibility issues by applying small, targeted diffs to HTML elements. This skill audits interactive controls, forms, and dialogs, then generates minimal patches for accessible names, keyboard access, focus management, and semantics.

Auditing ARIA roles and keyboard navigation involves evaluating interactive controls against priority rules. This skill checks visible focus indicators, accessible names, and semantic markup to identify violations across your UI components.

The best way to improve focus management and color contrast is to evaluate them against WCAG criteria. This skill enforces priority rules for focus indicators and contrast, providing common fixes to meet accessibility standards.

Yes, you can fix accessibility for both forms and dialogs. The skill applies to interactive controls, forms, dialogs, and navigation, handling disabled states, form inputs, and focus management across these components.

Keyboard navigation fails on interactive controls when they lack proper focus management and accessible names. This skill audits HTML elements for missing semantics and focus indicators, then applies targeted diffs to restore keyboard access.

No specific frameworks are required to apply accessibility fixes. The skill works with standard HTML interfaces, auditing and patching elements like buttons, inputs, and menus with minimal, targeted diffs regardless of your frontend stack.