# Aquizzit VoiceOver test protocol

Version 1.0 — 29 July 2026  
Standard: WCAG 2.2 A and AA  
Combination: macOS, Safari and VoiceOver

## Preparation

1. Start Safari without browser extensions.
2. Enable VoiceOver with Command + F5.
3. Test once with Quick Nav off and once with Quick Nav on.
4. Clear cookies or use a private window.
5. Record the device, macOS version, Safari version, outcome, actual
   announcement and any blocker for every scenario.

## Expected scenarios

| Scenario | Action | Expected outcome |
|---|---|---|
| Skip link | Open the homepage and press Tab once | “Skip to the main content” is announced; Enter moves focus to main |
| Landmarks | Open the VoiceOver rotor | Main and named navigation landmarks can be found separately |
| Headings | Open Headings in the rotor | One H1; sections follow a logical H2/H3 structure |
| Main navigation | Operate the menu and dropdowns without a mouse | Name, role, expanded state and links are announced correctly |
| Language switcher | Move to the flags | Current language is announced as the current page; both links have a language name |
| Sourcing Radar | Type “cloud”, use arrow keys and Enter | Combobox, suggestions, active option and updated analysis are announced |
| Supplier Top 250 | Search and change filters | Search field, filter state, result count and selected supplier profile remain understandable |
| Maturity Scan | Select an answer and continue | Question number, question, answer meaning, example and selected state are announced |
| Contract Health Check | Answer a question and open the result | Question group, choice, progress, score and advice follow a logical reading order |
| FAQ | Open and close a question with Enter | Label and expanded state are audible; the answer follows the question |
| Ask Aquizzit | Open with Enter, ask a question and close with Escape | Focus moves to Close; new answers are announced once; Escape closes and restores focus |
| Contact form | Submit with required fields empty | Every problem is associated with the right field; error and success states are announced |

## Acceptance criteria

- No keyboard trap.
- No unnamed links, buttons, inputs or interactive images.
- Focus and reading order follow the visual and content hierarchy.
- Changes to `aria-expanded`, `aria-pressed`, results and status messages are
  announced meaningfully.
- Decorative animations and duplicates do not appear in the rotor or reading
  order.
- No unexpected context change on focus or input.

VoiceOver results must be recorded separately. Automated axe and accessibility
tree tests do not replace this session and do not constitute a formal WCAG
conformance claim on their own.