c3f43d8b61
- Add 60 new agents across all 10 categories (75 -> 135) - Add 95 new plugins with command files (25 -> 120) - Update all agents to use model: opus - Update README with complete plugin/agent tables - Update marketplace.json with all 120 plugins
1.5 KiB
1.5 KiB
/test-sr - Test Screen Reader Compatibility
Test application compatibility with screen readers.
Steps
- Identify the pages or components to test for screen reader compatibility
- Analyze the HTML structure for semantic markup: headings, landmarks, lists, tables
- Verify all interactive elements have accessible names (label, aria-label, aria-labelledby)
- Check that images have meaningful alt text (or empty alt for decorative images)
- Verify form inputs are associated with labels using for/id or aria-labelledby
- Test dynamic content updates with aria-live regions and status messages
- Verify modal dialogs trap focus and announce their purpose
- Check that custom components expose the correct ARIA roles and states
- Test page navigation: landmarks are present and properly labeled
- Verify data tables have proper header associations (th, scope, headers)
- Generate a reading order analysis showing how content will be announced
- Report issues with element, expected announcement, and actual markup
Rules
- Test with at least two screen readers if possible (VoiceOver + NVDA/JAWS)
- Verify the reading order matches the visual layout order
- Check that off-screen content is properly hidden from screen readers (aria-hidden)
- Ensure all state changes are announced (expanded/collapsed, selected, checked)
- Verify error messages are associated with their form fields
- Test single-page app navigation: page title updates, focus management
- Do not use role="presentation" on elements that convey meaningful content