Screen Reader Testing Script

You are an accessibility testing expert helping me create a test script for screen reader evaluation. I need to systematically test my product with assistive technology.

Test Context:
- Product/feature to test: [What you're testing]
- Screen readers to use: [VoiceOver, NVDA, JAWS, TalkBack]
- Key user flows: [Critical paths to test]
- Target WCAG level: [A, AA, or AAA]

Please create a comprehensive screen reader test script:

1. Test Environment Setup
   
   VoiceOver (macOS):
   - Enable: Command + F5
   - Rotor: VO + U
   - Navigation: VO + arrows
   - Key commands reference: [List essential commands]
   
   NVDA (Windows):
   - Enable: Ctrl + Alt + N
   - Elements list: NVDA + F7
   - Navigation: Arrow keys
   - Key commands reference: [List essential commands]
   
   Browser combinations to test:
   - macOS: Safari + VoiceOver, Chrome + VoiceOver
   - Windows: Firefox + NVDA, Chrome + NVDA
   - Mobile: iOS Safari + VoiceOver, Android Chrome + TalkBack

2. Pre-Test Checklist
   □ Screen reader installed and updated
   □ Browser zoom at 100%
   □ Test page loaded fresh
   □ Keyboard focus visible
   □ Audio working

3. Landmark & Structure Test
   □ Page has proper landmarks (main, nav, header, footer)
   □ Landmarks are announced correctly
   □ Heading structure is logical (h1 → h2 → h3)
   □ Skip links work and are announced
   □ Page title is descriptive
   
   What to check:
   - Use rotor/elements list to view landmarks
   - Navigate by headings - is the hierarchy correct?
   - Check if skip link moves focus appropriately

4. Navigation Test
   □ All interactive elements reachable by keyboard
   □ Focus order matches visual order
   □ Focus indicator visible
   □ No focus traps
   □ Menu/dropdown accessible
   □ Modal dialogs trap focus correctly
   
   What to check:
   - Tab through entire page - any elements skipped?
   - Can you exit all menus and dialogs?
   - Is focus ever lost or invisible?

5. Interactive Elements Test
   For each button/link/control:
   □ Role announced correctly (button, link, checkbox, etc.)
   □ Name/label is descriptive
   □ State announced (pressed, expanded, selected)
   □ Instructions provided if needed
   □ Feedback announced on interaction
   
   Common issues:
   - Clickable divs not announced as buttons
   - Icons without accessible names
   - State changes not announced

6. Form Test
   For each form field:
   □ Label associated and announced
   □ Required fields indicated
   □ Error messages announced
   □ Success feedback announced
   □ Autocomplete suggestions accessible
   □ Date pickers/custom controls work
   
   What to check:
   - Enter each field - is label clear?
   - Submit with errors - are they announced?
   - Can you complete the form eyes-closed?

7. Dynamic Content Test
   □ Live regions announce updates
   □ Loading states announced
   □ Notifications/toasts announced
   □ Infinite scroll accessible
   □ Auto-updating content manageable
   
   What to check:
   - Do status messages get announced?
   - Can users pause auto-updating content?

8. Image & Media Test
   □ Images have alt text
   □ Alt text is descriptive (not "image" or filename)
   □ Decorative images hidden from AT
   □ Complex images have long descriptions
   □ Video has captions
   □ Audio has transcripts
   
   What to check:
   - Navigate to each image - is alt text useful?
   - Are decorative images silent?

9. User Flow Testing
   For each critical flow ([list your flows]):
   
   Flow: [e.g., Sign up for account]
   □ Step 1: [Action] - Announced: [Expected announcement]
   □ Step 2: [Action] - Announced: [Expected announcement]
   □ Step 3: [Action] - Announced: [Expected announcement]
   □ Success: [Outcome announced correctly]
   
   Can a user complete this flow using only a screen reader?

10. Issue Documentation Template
    Issue #[X]:
    - Screen reader: [Which SR]
    - Browser: [Which browser]
    - Location: [Page/component]
    - Steps to reproduce: [How to find it]
    - What was announced: [Actual]
    - What should be announced: [Expected]
    - WCAG criterion: [Which guideline]
    - Severity: [Critical/Serious/Moderate/Minor]