Drupal RGAA check

Status: initial version. The Drupal-specific checklist (core and contrib markup pitfalls, Paragraphs, Views, Webform, media, CKEditor content) is under construction. Until it exists, this skill applies the RGAA 4.1.2 criteria that fit the component, using the procedure below. Only this file changes as it grows; the contract does not.

Call contract (frozen)

Input — given by the caller, asked if missing:

Output — in French, ready to paste in the MR:

## RGAA — <unit>

Verdict : conforme | non conforme (<n> bloquants)
Référentiel : RGAA 4.1.2 (critères applicables au composant) — checklist Drupal en construction.

| Critère | Statut | Preuve / remarque | Bloquant |
|---|---|---|---|
| 7.3 Composants contrôlables au clavier | C | Entrée/Espace ouvrent l'élément, Échap ferme | — |
| 10.7 Focus visible | NC | Bouton « Fermer » : contour 1 px, ratio 1.9:1 sur fond gris | oui |
| 5.x Tableaux | NA | Aucun tableau | — |

C conforme, NC non conforme, NA non applicable. Bloquant = a non-conformity on a criterion the unit is responsible for. Return the list of blocking points first, each with the fix to make; the caller fixes them and calls again with the same input.

Procedure

Load the claude-in-chrome skill and the Chrome tools in one ToolSearch call. For each page, at each breakpoint:

1. axe first (already in make test-e2e): read its result for the pages. Each violation is a lead, mapped to its RGAA criterion; absence of violations proves little.
2. Keyboard: Tab through the scope from the address bar. Every interactive element is reachable, in a logical order, operable (Enter, Space, arrows where the pattern expects them, Escape closes), never trapped; nothing receives focus while hidden.
3. Focus visible on every focusable element, contrast of the indicator ≥ 3:1 against its background.
4. Contrast: text 4.5:1 (3:1 large), UI components and meaningful icons 3:1 — computed on the rendered colours (getComputedStyle), including hover, focus, disabled and error states, and text over images. Colours the editor picks from a palette are reported as « dépend de la contribution » with the decision of decisions.md; only the default pairs and the pairs of the demo content can be blocking.
5. Text alternatives: informative images and icons have a relevant alternative; decorative ones are hidden (alt="", aria-hidden); icon-only buttons and links have an accessible name.
6. Structure: heading outline without jumps that break the page's hierarchy, one h1 per page; landmarks (header, nav with distinct labels, main, footer); lists marked as lists.
7. Forms: every field has a label tied to it, required fields indicated in text, errors tied to fields and summarised, autocomplete on personal data fields, status messages announced.
8. Zoom 200 % (text): no loss of content or function.
9. Reflow at 320 px width: no horizontal scroll, except content that needs two dimensions (tables, maps).
10. Motion and time: moving or auto-updating content can be paused; prefers-reduced-motion honoured.
11. Language: lang on the page, lang on any passage in another language (language switcher included).

RGAA 4.1.2 criteria by category

Apply the rows of the category; add any other criterion the component obviously touches, and the criteria of the unit's a11y requirements (a design accessibility checklist lands there in the intake). Numbers per RGAA 4.1.2 — check the wording against the official reference (accessibilite.numerique.gouv.fr) when in doubt.

Under construction — Drupal checklist

The checks to add here, as they are confirmed on real builds:

• core markup that fails by default and the template to override;
• Paragraphs and CKEditor content an editor can break (heading levels, empty links, images without alt);
• Views exposed filters, pagers and AJAX announcements;
• Webform and Form API error handling;
• media library and responsive images;
• the admin forms an editor uses (when the CDC puts the back office in scope).