{"enrichment":{"faq":[{"a":"accessibility-a11y helps you build interfaces that meet WCAG 2.2 compliance by guiding you through semantic HTML structure, ARIA labeling, keyboard navigation, and color contrast requirements. The skill covers both foundational principles\u2014like proper heading hierarchy and form field associations\u2014and advanced patterns such as live regions for dynamic content and focus management for complex interactive components. You'll learn to evaluate your site systematically and implement fixes that ensure users with disabilities can navigate and interact with your content effectively.","q":"How do I make a website accessible to WCAG 2.2 standards?"},{"a":"accessibility-a11y emphasizes that screen reader testing and keyboard navigation are core pillars of accessible design. The skill teaches you to test with assistive technologies like NVDA and VoiceOver to verify that your content is properly announced, and to implement full keyboard-only navigation so users who cannot use a mouse can access all interactive features. You'll learn focus management techniques, ARIA patterns for custom widgets, and how to structure forms with error messages that screen readers can announce clearly.","q":"What role does screen reader testing and keyboard navigation play in accessibility-a11y?"},{"a":"accessibility-a11y shows you how to embed automated testing tools like Jest and Axe into your development workflow so accessibility checks run continuously. By integrating these tools into your CI/CD pipeline, you catch violations early\u2014before they reach production\u2014and maintain compliance as your codebase evolves. The skill guides you through setting up test configurations, interpreting results, and combining automated checks with manual testing to ensure comprehensive coverage of accessibility requirements.","q":"How can I integrate automated accessibility testing into my CI/CD pipeline?"},{"a":"accessibility-a11y teaches you to associate form labels with inputs using semantic HTML, implement ARIA labels and descriptions for complex fields, and announce validation errors in ways that screen readers can communicate to users. The skill covers techniques like using aria-invalid, aria-describedby, and live regions to ensure error messages are announced dynamically when validation fails, making it clear to all users\u2014especially those relying on assistive technology\u2014what went wrong and how to correct it.","q":"What are the best practices for implementing accessible form fields with error messages?"},{"a":"accessibility-a11y provides patterns for building accessible modal dialogs and dropdown menus that work across frameworks like React. For modals, you'll learn to manage focus (trapping it within the dialog), handle keyboard events (like Escape to close), and use ARIA attributes like role=\"dialog\" and aria-labelledby. For dropdowns, the skill covers keyboard interactions (arrow keys, Enter, Escape), focus management, and ARIA patterns that ensure screen reader users understand the component's state and can navigate options efficiently.","q":"How do I implement an accessible modal dialog or dropdown menu in React?"},{"a":"accessibility-a11y emphasizes that semantic HTML is the foundation of accessibility\u2014using native elements like