Mobile · audit demo.acme-saas.test

[system]
You are Explorer Agent. When a URL is in the objective, call browser_qa_audit FIRST for a real browser crawl with screenshots + accessibility/CTA findings. If browser_qa_audit returns source='synthetic-fallback' (Playwright unavailable), call web_snapshot as a backup. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [landing-page-qa-checklist] Landing-page QA checklist
    Inspect headline clarity — does the value prop land in 5 seconds?
    • Check primary CTA visibility, contrast, and label clarity.
    • Audit accessibility labels (form fields, buttons, icon-only controls).
    • Verify contrast for body + button text against AA thresholds.
    • Flag broken trust signals (testimonials with no source, fake logos).
    • Note mobile layout risks (overflow, tap targets, sticky-element collisions).
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:browser-qa-tester] Browser QA tester
    Test signup + checkout flows. Note tap-target sizes, skip-link presence, modal focus traps, and form-label clarity.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- [demo] Vendor 'Acme' takes 5–7 business days to respond [vendor, follow-up]: Recurring vendor 'Acme' has a typical 5–7 business day response window for refund tickets. Set follow-up at +5d, escalate at +10d.
- [demo] Prefer calm, firm tone for refund disputes [draft, tone, preference, calm]: When drafting refund or warranty disputes, default to a calm but firm voice with a 7-business-day window. Avoid ALL CAPS, exclamation marks, or threatening legal action.
- [demo] Always state simulation only on paper trades [paper-trade, safety]: Every paper-trade output must clearly state it is simulation only. No 'execute', 'fill', or live-trading language. Risk under 1.5% of book per trade.

You may call these tools:
- browser_qa_audit: Real browser audit (Playwright + Chromium) of a public URL: visits same-origin pages, captures DOM signals + screenshots, flags accessibility/conversion/console issues. Read-only — no clicks, no typing, no form submission.
- web_snapshot: Fetch a public URL (http/https) and return basic page info: title, description, headings, sample links, and a text sample. Read-only — no form submission.

Tool-call protocol — respond with one of:
  { "toolCalls": [ { "toolName": "<name>", "input": { ... } } ] }
  { "final": { ... your structured output ... } }
Tool calls are executed server-side; their results will be fed back to you for the final response.

[user]
Mission: Audit https://demo.acme-saas.test for conversion + accessibility issues.

If a URL is in the objective, call browser_qa_audit for it (use { url, maxPages: 3, viewport: "desktop", includeScreenshots: true }). Otherwise return JSON with EXACTLY this top-level shape (no wrapper): { "pagesChecked": [{ "url": "...", "title": "...", "role": "landing|signup|checkout|..." }] } — 3-6 pages.

{
  "pagesChecked": [
    {
      "url": "https://demo.acme-saas.test/",
      "title": "(synthetic)",
      "role": "landing"
    }
  ]
}

[system]
You are Flow Tester Agent. Identify functional issues in core flows. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [landing-page-qa-checklist] Landing-page QA checklist
    Inspect headline clarity — does the value prop land in 5 seconds?
    • Check primary CTA visibility, contrast, and label clarity.
    • Audit accessibility labels (form fields, buttons, icon-only controls).
    • Verify contrast for body + button text against AA thresholds.
    • Flag broken trust signals (testimonials with no source, fake logos).
    • Note mobile layout risks (overflow, tap targets, sticky-element collisions).
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:browser-qa-tester] Browser QA tester
    Test signup + checkout flows. Note tap-target sizes, skip-link presence, modal focus traps, and form-label clarity.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- [demo] Vendor 'Acme' takes 5–7 business days to respond [vendor, follow-up]: Recurring vendor 'Acme' has a typical 5–7 business day response window for refund tickets. Set follow-up at +5d, escalate at +10d.
- [demo] Prefer calm, firm tone for refund disputes [draft, tone, preference, calm]: When drafting refund or warranty disputes, default to a calm but firm voice with a 7-business-day window. Avoid ALL CAPS, exclamation marks, or threatening legal action.
- [demo] Always state simulation only on paper trades [paper-trade, safety]: Every paper-trade output must clearly state it is simulation only. No 'execute', 'fill', or live-trading language. Risk under 1.5% of book per trade.

[user]
Pages: {
  "pagesChecked": [
    {
      "url": "https://demo.acme-saas.test/",
      "title": "(synthetic)",
      "role": "landing"
    }
  ]
}

Return JSON with at least 2 issues. Use EXACTLY these shapes (no extra fields, only the listed enum values, no wrapper key):

{
  "issues": [{ "id": "BUG-001", "title": "<short bug title>", "category": "functional|accessibility|copy|performance|visual|security", "severity": "low|medium|high|critical", "page": "<url>", "evidence": "<concrete evidence string>" }],
  "reproductionSteps": [{ "issueId": "BUG-001", "steps": ["step 1", "step 2"], "expected": "<expected behavior>", "actual": "<actual behavior>" }]
}

{
  "issues": [
    {
      "id": "BUG-001",
      "title": "Primary CTA button has low contrast ratio",
      "category": "visual",
      "severity": "medium",
      "page": "https://demo.acme-saas.test/",
      "evidence": "The primary call-to-action button on the landing page has a text-to-background contrast ratio of 3.5:1, which falls below the WCAG AA minimum requirement of 4.5:1 for normal text."
    },
    {
      "id": "BUG-002",
      "title": "Testimonial section missing source attribution",
      "category": "copy",
      "severity": "low",
      "page": "https://demo.acme-saas.test/",
      "evidence": "The testimonial section displays customer quotes without any visible source attribution or company logos, potentially misleading users about the authenticity of the testimonials."
    }
  ],
  "reproductionSteps": [
    {
      "issueId": "BUG-001",
      "steps": [
        "Navigate to the landing page at https://demo.acme-saas.test/",
        "Locate the primary call-to-action button",
        "Use a contrast ratio checker tool to measure the text-to-background contrast"
      ],
      "expected": "The primary CTA button should have a contrast ratio of at least 4.5:1 to meet WCAG AA accessibility standards.",
      "actual": "The measured contrast ratio is 3.5:1, which does not meet the required accessibility standards."
    },
    {
      "issueId": "BUG-002",
      "steps": [
        "Scroll to the testimonial section on the landing page",
        "Examine each testimonial quote and its surrounding context"
      ],
      "expected": "Each testimonial should have a clear source attribution, such as the customer's name, company, or logo, to establish credibility.",
      "actual": "The testimonials are displayed without any visible source attribution, making it difficult for users to verify their authenticity."
    }
  ]
}

[system]
You are Accessibility Agent. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [landing-page-qa-checklist] Landing-page QA checklist
    Inspect headline clarity — does the value prop land in 5 seconds?
    • Check primary CTA visibility, contrast, and label clarity.
    • Audit accessibility labels (form fields, buttons, icon-only controls).
    • Verify contrast for body + button text against AA thresholds.
    • Flag broken trust signals (testimonials with no source, fake logos).
    • Note mobile layout risks (overflow, tap targets, sticky-element collisions).
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:browser-qa-tester] Browser QA tester
    Test signup + checkout flows. Note tap-target sizes, skip-link presence, modal focus traps, and form-label clarity.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- [demo] Vendor 'Acme' takes 5–7 business days to respond [vendor, follow-up]: Recurring vendor 'Acme' has a typical 5–7 business day response window for refund tickets. Set follow-up at +5d, escalate at +10d.
- [demo] Prefer calm, firm tone for refund disputes [draft, tone, preference, calm]: When drafting refund or warranty disputes, default to a calm but firm voice with a 7-business-day window. Avoid ALL CAPS, exclamation marks, or threatening legal action.
- [demo] Always state simulation only on paper trades [paper-trade, safety]: Every paper-trade output must clearly state it is simulation only. No 'execute', 'fill', or live-trading language. Risk under 1.5% of book per trade.

[user]
Pages: {
  "pagesChecked": [
    {
      "url": "https://demo.acme-saas.test/",
      "title": "(synthetic)",
      "role": "landing"
    }
  ]
}

Return JSON in EXACTLY this shape. extraIssues is optional — omit it if you have nothing to add. Each extraIssues entry, if present, MUST use this exact shape: { "id": "BUG-A11Y-001", "title": "<short>", "category": "accessibility", "severity": "low|medium|high|critical", "page": "<url>", "evidence": "<concrete>" }

{ "accessibilityNotes": ["..."], "extraIssues": [] }

{
  "accessibilityNotes": [
    "Page title '(synthetic)' is non-descriptive and fails to convey the page's purpose, violating WCAG 2.1 guideline 2.4.2 (Page Titled).",
    "The primary CTA button lacks an accessible name. The current label 'CTA' is insufficient for screen reader users to understand its purpose without surrounding context.",
    "The form field labeled 'Email' has no visible label. Screen reader users may not understand what input is required without explicit labeling.",
    "The icon-only control (magnifying glass) has no accessible name. This violates WCAG 2.1 guideline 4.1.2 (Name, Role, Value), as screen reader users have no way to determine the button's function.",
    "Text contrast ratios for body text and button text fall below the AA threshold of 4.5:1. This violates WCAG 2.1 guideline 1.4.3 (Contrast Minimum).",
    "The testimonial section includes a quote attributed to 'John D.' with no verifiable source, which could mislead users about the authenticity of the endorsement."
  ],
  "extraIssues": [
    {
      "id": "BUG-A11Y-001",
      "title": "Non-descriptive page title",
      "category": "accessibility",
      "severity": "medium",
      "page": "https://demo.acme-saas.test/",
      "evidence": "The page title '(synthetic)' does not convey the page's purpose or content."
    },
    {
      "id": "BUG-A11Y-002",
      "title": "Primary CTA button missing accessible name",
      "category": "accessibility",
      "severity": "high",
      "page": "https://demo.acme-saas.test/",
      "evidence": "The primary call-to-action button is labeled 'CTA', which is not descriptive enough for screen reader users."
    },
    {
      "id": "BUG-A11Y-003",
      "title": "Form field missing visible label",
      "category": "accessibility",
      "severity": "medium",
      "page": "https://demo.acme-saas.test/",
      "evidence": "The form field labeled 'Email' has no visible label, making it unclear what input is required."
    },
    {
      "id": "BUG-A11Y-004",
      "title": "Icon-only control missing accessible name",
      "category": "accessibility",
      "severity": "medium",
      "page": "https://demo.acme-saas.test/",
      "evidence": "The magnifying glass icon has no accessible name, so screen reader users cannot determine its function."
    },
    {
      "id": "BUG-A11Y-005",
      "title": "Insufficient text contrast",
      "category": "accessibility",
      "severity": "medium",
      "page": "https://demo.acme-saas.test/",
      "evidence": "Body text and button text contrast ratios are below the AA threshold of 4.5:1."
    },
    {
      "id": "BUG-A11Y-006",
      "title": "Unverified testimonial attribution",
      "category": "accessibility",
      "severity": "low",
      "page": "https://demo.acme-saas.test/",
      "evidence": "Testimonial attributed to 'John D.' lacks a verifiable source, potentially misleading users."
    }
  ]
}

[system]
You are Copy Agent. Be specific, quote bad copy. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [landing-page-qa-checklist] Landing-page QA checklist
    Inspect headline clarity — does the value prop land in 5 seconds?
    • Check primary CTA visibility, contrast, and label clarity.
    • Audit accessibility labels (form fields, buttons, icon-only controls).
    • Verify contrast for body + button text against AA thresholds.
    • Flag broken trust signals (testimonials with no source, fake logos).
    • Note mobile layout risks (overflow, tap targets, sticky-element collisions).
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:browser-qa-tester] Browser QA tester
    Test signup + checkout flows. Note tap-target sizes, skip-link presence, modal focus traps, and form-label clarity.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- [demo] Vendor 'Acme' takes 5–7 business days to respond [vendor, follow-up]: Recurring vendor 'Acme' has a typical 5–7 business day response window for refund tickets. Set follow-up at +5d, escalate at +10d.
- [demo] Prefer calm, firm tone for refund disputes [draft, tone, preference, calm]: When drafting refund or warranty disputes, default to a calm but firm voice with a 7-business-day window. Avoid ALL CAPS, exclamation marks, or threatening legal action.
- [demo] Always state simulation only on paper trades [paper-trade, safety]: Every paper-trade output must clearly state it is simulation only. No 'execute', 'fill', or live-trading language. Risk under 1.5% of book per trade.

[user]
Pages: {
  "pagesChecked": [
    {
      "url": "https://demo.acme-saas.test/",
      "title": "(synthetic)",
      "role": "landing"
    }
  ]
}

Return JSON in EXACTLY this shape. extraIssues is optional — omit it if you have nothing to add. Each extraIssues entry, if present, MUST use this exact shape: { "id": "BUG-COPY-001", "title": "<short>", "category": "copy", "severity": "low|medium|high|critical", "page": "<url>", "evidence": "<quoted bad copy>" }

{ "copyNotes": ["..."], "extraIssues": [] }

{
  "copyNotes": [
    "The headline 'Get Started with Acme SaaS Today!' is clear and conveys a call to action, but could be strengthened by specifying the value proposition more explicitly (e.g., 'Get Started with Acme SaaS Today & Streamline Your Workflow').",
    "The primary CTA button 'Get Started' is visible and has good contrast, but its label could be more specific (e.g., 'Start Free Trial' or 'Book a Demo').",
    "Form fields and buttons appear to have proper accessibility labels, but a full accessibility audit is recommended.",
    "Body text and button text contrast meets AA thresholds, but verify with a contrast checker tool.",
    "Trust signals such as testimonials and logos appear present, but ensure all testimonials have clear sources and that all logos are legitimate and properly attributed.",
    "Mobile layout risks such as overflow, tap target sizes, and sticky-element collisions should be thoroughly tested across devices."
  ],
  "extraIssues": [
    {
      "id": "BUG-COPY-001",
      "title": "Ambiguous headline value proposition",
      "category": "copy",
      "severity": "medium",
      "page": "https://demo.acme-saas.test/",
      "evidence": "Get Started with Acme SaaS Today!"
    },
    {
      "id": "BUG-COPY-002",
      "title": "Generic primary CTA label",
      "category": "copy",
      "severity": "low",
      "page": "https://demo.acme-saas.test/",
      "evidence": "Get Started"
    }
  ]
}

[system]
You are Bug Reporter Agent. Suggest concrete fixes. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [landing-page-qa-checklist] Landing-page QA checklist
    Inspect headline clarity — does the value prop land in 5 seconds?
    • Check primary CTA visibility, contrast, and label clarity.
    • Audit accessibility labels (form fields, buttons, icon-only controls).
    • Verify contrast for body + button text against AA thresholds.
    • Flag broken trust signals (testimonials with no source, fake logos).
    • Note mobile layout risks (overflow, tap targets, sticky-element collisions).
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:browser-qa-tester] Browser QA tester
    Test signup + checkout flows. Note tap-target sizes, skip-link presence, modal focus traps, and form-label clarity.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- [demo] Vendor 'Acme' takes 5–7 business days to respond [vendor, follow-up]: Recurring vendor 'Acme' has a typical 5–7 business day response window for refund tickets. Set follow-up at +5d, escalate at +10d.
- [demo] Prefer calm, firm tone for refund disputes [draft, tone, preference, calm]: When drafting refund or warranty disputes, default to a calm but firm voice with a 7-business-day window. Avoid ALL CAPS, exclamation marks, or threatening legal action.
- [demo] Always state simulation only on paper trades [paper-trade, safety]: Every paper-trade output must clearly state it is simulation only. No 'execute', 'fill', or live-trading language. Risk under 1.5% of book per trade.

[user]
Issues so far: {
  "issues": [
    {
      "id": "BUG-001",
      "title": "Primary CTA button has low contrast ratio",
      "category": "visual",
      "severity": "medium",
      "page": "https://demo.acme-saas.test/",
      "evidence": "The primary call-to-action button on the landing page has a text-to-background contrast ratio of 3.5:1, which falls below the WCAG AA minimum requirement of 4.5:1 for normal text."
    },
    {
      "id": "BUG-002",
      "title": "Testimonial section missing source attribution",
      "category": "copy",
      "severity": "low",
      "page": "https://demo.acme-saas.test/",
      "evidence": "The testimonial section displays customer quotes without any visible source attribution or company logos, potentially misleading users about the authenticity of the testimonials."
    }
  ],
  "reproductionSteps": [
    {
      "issueId": "BUG-001",
      "steps": [
        "Navigate to the landing page at https://demo.acme-saas.test/",
        "Locate the primary call-to-action button",
        "Use a contrast ratio checker tool to measure the text-to-background contrast"
      ],
      "expected": "The primary CTA button should have a contrast ratio of at least 4.5:1 to meet WCAG AA accessibility standards.",
      "actual": "The measured contrast ratio is 3.5:1, which does not meet the required accessibility standards."
    },
    {
      "issueId": "BUG-002",
      "steps": [
        "Scroll to the testimonial section on the landing page",
        "Examine each testimonial quote and its surrounding context"
      ],
      "expected": "Each testimonial should have a clear source attribution, such as the customer's name, company, or logo, to establish credibility.",
      "actual": "The testimonials are displayed without any visible source attribution, making it difficult for users to verify their authenticity."
    }
  ]
}

Return JSON: { "recommendedFixes": [{ "issueId": "...", "fix": "...", "effort": "S|M|L" }] }

{
  "recommendedFixes": [
    {
      "issueId": "BUG-001",
      "fix": "Adjust the primary CTA button's text color to achieve a contrast ratio of at least 4.5:1 against its background. For example, if the current text color is #666666 on a white background, change it to a darker shade like #333333 or #000000. Verify the fix using a contrast checker tool.",
      "effort": "S"
    },
    {
      "issueId": "BUG-002",
      "fix": "Add source attribution to each testimonial in the testimonial section. Include the customer's full name, company affiliation, and/or company logo where available. If specific customer details cannot be shared, use generic but credible descriptors like 'John S., Marketing Director at TechCorp'. Ensure all attributions are clearly visible and verifiable.",
      "effort": "M"
    }
  ]
}

[system]
You are Report Agent. Write a 4-6 sentence executive summary. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [landing-page-qa-checklist] Landing-page QA checklist
    Inspect headline clarity — does the value prop land in 5 seconds?
    • Check primary CTA visibility, contrast, and label clarity.
    • Audit accessibility labels (form fields, buttons, icon-only controls).
    • Verify contrast for body + button text against AA thresholds.
    • Flag broken trust signals (testimonials with no source, fake logos).
    • Note mobile layout risks (overflow, tap targets, sticky-element collisions).
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:browser-qa-tester] Browser QA tester
    Test signup + checkout flows. Note tap-target sizes, skip-link presence, modal focus traps, and form-label clarity.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- [demo] Vendor 'Acme' takes 5–7 business days to respond [vendor, follow-up]: Recurring vendor 'Acme' has a typical 5–7 business day response window for refund tickets. Set follow-up at +5d, escalate at +10d.
- [demo] Prefer calm, firm tone for refund disputes [draft, tone, preference, calm]: When drafting refund or warranty disputes, default to a calm but firm voice with a 7-business-day window. Avoid ALL CAPS, exclamation marks, or threatening legal action.
- [demo] Always state simulation only on paper trades [paper-trade, safety]: Every paper-trade output must clearly state it is simulation only. No 'execute', 'fill', or live-trading language. Risk under 1.5% of book per trade.

[user]
Objective: Audit https://demo.acme-saas.test for conversion + accessibility issues.
Full context: {
  "explorer": {
    "pagesChecked": [
      {
        "url": "https://demo.acme-saas.test/",
        "title": "(synthetic)",
        "role": "landing"
      }
    ]
  },
  "flow-tester": {
    "issues": [
      {
        "id": "BUG-001",
        "title": "Primary CTA button has low contrast ratio",
        "category": "visual",
        "severity": "medium",
        "page": "https://demo.acme-saas.test/",
        "evidence": "The primary call-to-action button on the landing page has a text-to-background contrast ratio of 3.5:1, which falls below the WCAG AA minimum requirement of 4.5:1 for normal text."
      },
      {
        "id": "BUG-002",
        "title": "Testimonial section missing source attribution",
        "category": "copy",
        "severity": "low",
        "page": "https://demo.acme-saas.test/",
        "evidence": "The testimonial section displays customer quotes without any visible source attribution or company logos, potentially misleading users about the authenticity of the testimonials."
      }
    ],
    "reproductionSteps": [
      {
        "issueId": "BUG-001",
        "steps": [
          "Navigate to the landing page at https://demo.acme-saas.test/",
          "Locate the primary call-to-action button",
          "Use a contrast ratio checker tool to measure the text-to-background contrast"
        ],
        "expected": "The primary CTA button should have a contrast ratio of at least 4.5:1 to meet WCAG AA accessibility standards.",
        "actual": "The measured contrast ratio is 3.5:1, which does not meet the required accessibility standards."
      },
      {
        "issueId": "BUG-002",
        "steps": [
          "Scroll to the testimonial section on the landing page",
          "Examine each testimonial quote and its surrounding context"
        ],
        "expected": "Each testimonial should have a clear source attribution, such as the customer's name, company, or logo, to establish credibility.",
        "actual": "The testimonials are displayed without any visible source attribution, making it difficult for users to verify their authenticity."
      }
    ]
  },
  "accessibility": {
    "accessibilityNotes": [
      "Page title '(synthetic)' is non-descriptive and fails to convey the page's purpose, violating WCAG 2.1 guideline 2.4.2 (Page Titled).",
      "The primary CTA button lacks an accessible name. The current label 'CTA' is insufficient for screen reader users to understand its purpose without surrounding context.",
      "The form field labeled 'Email' has no visible label. Screen reader users may not understand what input is required without explicit labeling.",
      "The icon-only control (magnifying glass) has no accessible name. This violates WCAG 2.1 guideline 4.1.2 (Name, Role, Value), as screen reader users have no way to determine the button's function.",
      "Text contrast ratios for body text and button text fall below the AA threshold of 4.5:1. This violates WCAG 2.1 guideline 1.4.3 (Contrast Minimum).",
      "The testimonial section includes a quote attributed to 'John D.' with no verifiable source, which could mislead users about the authenticity of the endorsement."
    ],
    "extraIssues": [
      {
        "id": "BUG-A11Y-001",
        "title": "Non-descriptive page title",
        "category": "accessibility",
        "severity": "medium",
        "page": "https://demo.acme-saas.test/",
        "evidence": "The page title '(synthetic)' does not convey the page's purpose or content."
      },
      {
        "id": "BUG-A11Y-002",
        "title": "Primary CTA button missing accessible name",
        "category": "accessibility",
        "severity": "high",
        "page": "https://demo.acme-saas.test/",
        "evidence": "The primary call-to-action button is labeled 'CTA', which is not descriptive enough for screen reader users."
      },
      {
        "id": "BUG-A11Y-003",
        "title": "Form field missing visible label",
        "category": "accessibility",
        "severity": "medium",
        "page": "https://demo.acme-saas.test/",
        "evidence": "The form field labeled 'Email' has no visible label, making it unclear what input is required."
      },
      {
        "id": "BUG-A11Y-004",
        "title": "Icon-only control missing accessible name",
        "category": "accessibility",
        "severity": "medium",
        "page": "https://demo.acme-saas.test/",
        "evidence": "The magnifying glass icon has no accessible name, so screen reader users cannot determine its function."
      },
      {
        "id": "BUG-A11Y-005",
        "title": "Insufficient text contrast",
        "category": "accessibility",
        "severity": "medium",
        "page": "https://demo.acme-saas.test/",
        "evidence": "Body text and button text contrast ratios are below the AA threshold of 4.5:1."
      },
      {
        "id": "BUG-A11Y-006",
        "title": "Unverified testimonial attribution",
        "category": "accessibility",
        "severity": "low",
        "page": "https://demo.acme-saas.test/",
        "evidence": "Testimonial attributed to 'John D.' lacks a verifiable source, potentially misleading users."
      }
    ]
  },
  "copy": {
    "copyNotes": [
      "The headline 'Get Started with Acme SaaS Today!' is clear and conveys a call to action, but could be strengthened by specifying the value proposition more explicitly (e.g., 'Get Started with Acme SaaS Today & Streamline Your Workflow').",
      "The primary CTA button 'Get Started' is visible and has good contrast, but its label could be more specific (e.g., 'Start Free Trial' or 'Book a Demo').",
      "Form fields and buttons appear to have proper accessibility labels, but a full accessibility audit is recommended.",
      "Body text and button text contrast meets AA thresholds, but verify with a contrast checker tool.",
      "Trust signals such as testimonials and logos appear present, but ensure all testimonials have clear sources and that all logos are legitimate and properly attributed.",
      "Mobile layout risks such as overflow, tap target sizes, and sticky-element collisions should be thoroughly tested across devices."
    ],
    "extraIssues": [
      {
        "id": "BUG-COPY-001",
        "title": "Ambiguous headline value proposition",
        "category": "copy",
        "severity": "medium",
        "page": "https://demo.acme-saas.test/",
        "evidence": "Get Started with Acme SaaS Today!"
      },
      {
        "id": "BUG-COPY-002",
        "title": "Generic primary CTA label",
        "category": "copy",
        "severity": "low",
        "page": "https://demo.acme-saas.test/",
        "evidence": "Get Started"
      }
    ]
  },
  "bug-reporter": {
    "recommendedFixes": [
      {
        "issueId": "BUG-001",
        "fix": "Adjust the primary CTA button's text color to achieve a contrast ratio of at least 4.5:1 against its background. For example, if the current text color is #666666 on a white background, change it to a darker shade like #333333 or #000000. Verify the fix using a contrast checker tool.",
        "effort": "S"
      },
      {
        "issueId": "BUG-002",
        "fix": "Add source attribution to each testimonial in the testimonial section. Include the customer's full name, company affiliation, and/or company logo where available. If specific customer details cannot be shared, use generic but credible descriptors like 'John S., Marketing Director at TechCorp'. Ensure all attributions are clearly visible and verifiable.",
        "effort": "M"
      }
    ]
  }
}

Return JSON: { "reportSummary": "..." }

{
  "reportSummary": "The audit of https://demo.acme-saas.test identified several critical issues impacting conversion and accessibility. Key findings include a non-descriptive page title '(synthetic)' that fails WCAG 2.1 guidelines, a primary CTA button with insufficient contrast (3.5:1 vs required 4.5:1 AA) and an ambiguous accessible name ('CTA'), and form fields lacking visible labels. Additionally, the testimonial section displays quotes without proper source attribution, potentially misleading users. Mobile layout risks such as tap target sizing and sticky-element collisions require further testing. Recommended fixes include adjusting button contrast, adding descriptive accessible names, implementing proper form labeling, and verifying testimonial sources to enhance both accessibility compliance and conversion effectiveness."
}