BEST FOR:
- Conducting comprehensive WCAG audits
- Fixing screen reader announcement issues
- Implementing proper ARIA labels and landmarks
- Creating accessible forms and error handling
- Building keyboard navigation systems
- Testing with assistive technologies
- Reviewing color contrast and visual accessibility
- Making complex widgets (modals, tooltips, carousels) accessible
PRO TIPS:
- Include the specific WCAG level you’re targeting (A, AA, or AAA)
- Mention any industry-specific compliance requirements
- Share the component/pattern you’re trying to make accessible
- Specify which assistive technologies your users primarily use
SAMPLE FOLLOW-UP:
“Can you review this custom dropdown component for accessibility issues and provide the correct ARIA attributes and keyboard interaction patterns?”