# agent live-region fix announced every keystroke: screen reader spam - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent's live-region fix announces every keystroke, spamming screen-reader users. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
agent live-region fix announced every keystroke: screen reader spam
```

## Fix it step by step

### Step 1

Use aria-live polite with debounced updates: announce the settled value, not each keystroke.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 2

Never use assertive for typing feedback; reserve it for genuine emergencies.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 3

Consider announcing on blur or on a short idle delay instead of per input event.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 4

Test with a screen reader while typing; you should hear one calm update, not a stutter.

Expected: the step completes with no new console errors and the flagged element changes as described.

## When to use this skill

- Your scan report lists this exact rule or failure
- You are clearing automated accessibility failures before release or audit
- A CI accessibility gate is red because of this item

## When NOT to use this skill

- More announcements are not more accessible.
- The issue only appears in manual screen-reader testing and no automated rule flags it
- You are doing a full manual WCAG audit; this skill covers one automated check

## Compatibility

Agent workflow guardrail; manual screen-reader test.

## Variant phrasings

### agent live region announced every keystroke screen reader spam

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

## Why it happens

The agent's live-region fix announces every keystroke, spamming screen-reader users. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AEGKpw4h5WDzSK1ivWxBqA
