# agent applied aria-labels in the wrong language - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent wrote aria-labels in the wrong language, so screen readers mispronounce them. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
agent applied aria-labels in the wrong language
```

## Fix it step by step

### Step 1

Detect the page language from the html lang attribute before generating any labels.

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

### Step 2

Generate labels in the page's language; fall back to asking when lang is missing.

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

### Step 3

Set the page lang correctly first; mislabeled lang causes the same mispronunciation.

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

### Step 4

Re-run the label pass and spot-check pronunciation.

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

- An English label on a French page is a new violation wearing a fix costume.
- 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; page lang as the source of truth.

## Variant phrasings

### agent aria labels in wrong language

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

## Why it happens

The agent wrote aria-labels in the wrong language, so screen readers mispronounce them. 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_CHUH8DQ-G6hL7hPayVu7Vw