accessibility-compliance

WCAG 2.1 AA compliance requires implementing semantic HTML, ARIA roles and labels, keyboard navigation with visible focus indicators, sufficient color contrast ratios, and screen reader support. This Skill applies these standards across perceivable, operable, understandable, and robust guidelines to audit and fix accessibility issues systematically.

Use ARIA roles to define page structure, add aria-label and aria-labelledby attributes to interactive elements, and implement landmark regions like main, navigation, and complementary. Pair ARIA with semantic HTML tags to ensure screen readers announce content correctly and users can navigate efficiently.

Keyboard navigation requires managing focus order with logical tab sequences, implementing visible focus indicators on interactive elements, and ensuring all functionality is operable via keyboard alone. This Skill establishes focus management patterns that let users navigate forms, buttons, and links without a mouse.

WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. This Skill audits existing color pairs and recommends adjustments to ensure text remains readable for users with low vision while maintaining design intent.

Yes. Accessible forms pair input labels with form controls using explicit associations, provide error messages linked to fields via aria-describedby, and use ARIA attributes to indicate required fields and validation states. This approach ensures screen readers and keyboard users receive clear, actionable feedback.

You can audit and remediate components incrementally. This Skill identifies accessibility gaps in keyboard navigation, color contrast, ARIA labeling, focus indicators, and form semantics, then applies fixes systematically—whether addressing the full application or prioritizing high-impact areas first.