Accessibility conformance (BR)

accessibility specs/accessibility/conformance-br.kmd

How a Koder surface declares accessibility conformance against the three Brazilian-relevant standards at once: WCAG 2.2 AA (technical baseline), eMAG 3.1 (Modelo de Acessibilidade em Governo Eletrônico), and LBI — Lei Brasileira de Inclusão (Lei 13.146/2015, arts. 63 & 75, digital accessibility). Defines the cross-standard requirement matrix + the public conformance-declaration artifact. Required for gov.br-facing and public-sector Koder deployments.

When this spec applies

Primary triggers

All triggers

Spec — Accessibility conformance (BR)

Status: v0.1.0 — Draft. Promoted from the gov.br (DS Gov) parity scan (meta/docs/stack #098). Sources: WCAG 2.2 (W3C), eMAG 3.1 (gov.br), LBI — Lei nº 13.146/2015.

R1 — Single technical baseline, three declarations

Koder builds to one technical baseline — WCAG 2.2 Level AA — and maps that conformance onto the two Brazilian instruments. There is no separate "eMAG codebase": eMAG and LBI are satisfied through documented WCAG conformance plus the BR-specific additions in R3. Meeting WCAG AA is necessary but not by itself sufficient (R3).

R2 — The conformance matrix

Each surface tracks, per requirement area, how it satisfies all three:

Area (WCAG principle)WCAG 2.2 AAeMAG 3.1LBI 13.146
Perceivable1.x SC (contrast 1.4.3, text-resize 1.4.4, non-text 1.1.1)Marcação / Apresentação recsart. 63 (acessibilidade obrigatória)
Operable2.x SC (keyboard 2.1.1, focus 2.4.7, target size 2.5.8)Comportamento recsart. 63
Understandable3.x SC (labels 3.3.2, errors 3.3.1)Conteúdo/Informação recsart. 63; plain language → plain-language-ptbr.kmd
Robust4.x SC (name/role/value 4.1.2, status 4.1.3)Marcação recsart. 63

Cells record the Koder evidence (which spec/test proves it). The matrix is the source of truth for the declaration (R4).

R3 — BR additions beyond WCAG AA

WCAG AA does not cover everything eMAG/LBI expect; a conformant BR surface also:

  • carries an accessibility statement page (R4) — eMAG requires a documented declaration with contact for accessibility issues;
  • provides pt-BR plain-language copy (specs/content/plain-language-ptbr.kmd) — LBI emphasizes comprehensible communication;
  • supports Libras/text alternatives where eMAG calls for them on public institutional content (video captions + transcript);
  • keeps keyboard + screen-reader paths verified against the personas in specs/accessibility/personas.kmd.

R4 — The declaration artifact

A conformant surface publishes a declaração de acessibilidade:

  • the conformance target (WCAG 2.2 AA + eMAG 3.1 + LBI 13.146);
  • scope (which pages/flows), assessment date, and method (automated + manual + AT);
  • known limitations + remediation timeline (honest partial-conformance is allowed; silent over-claiming is not);
  • a contact channel to report accessibility barriers. This pairs with specs/accessibility/nutrition-labels.kmd (the per-feature a11y label) — the nutrition label is per-feature, the declaration is per-surface.

R5 — Verification

  • Automated checks (axe-core class) gate CI for the WCAG-machine-checkable subset; manual + AT verification covers the rest (most SC are not machine-decidable).
  • The matrix cell stays "unverified" until evidence exists — never marked conformant on assumption (Stack Regra 1).

Não-escopo

  • The full WCAG technique catalogue (referenced, not restated).
  • Per-component a11y rules (each component spec owns its own a11y section).
  • Legal advice / certification (this is the engineering contract, not a legal opinion).

References