You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Epic tracking the accessibility of learn-dev against the RGAA (Referentiel general d'amelioration de l'accessibilite), the French application of WCAG 2.1 AA used as the accessibility yardstick for the DWWM certification.
What the DWWM expects: not a full 106-criteria audit, but demonstrated integration of the accessibility essentials in the produced interfaces and the ability to verify them with tools. The criteria map below tracks what the frontend implements and where; the companion document docs/rgaa.md explains each criterion in depth.
Criteria map (implemented)
1.2 Decorative content ignored by assistive tech: aria-hidden on the home code card and feature emoji
3.1 Information not conveyed by color alone: form errors (border + bold text + aria-invalid), current nav item (bold + underline + aria-current)
3.2 Text contrast >= 4.5:1: every token pair computed in docs/design/theme-exploration.md (worst pair 4.73:1)
6.1 Explicit links: all link texts meaningful out of context
8.3 / 8.4 Page language present and relevant: lang="en" on pages, lang="fr" on the privacy policy
Epic tracking the accessibility of learn-dev against the RGAA (Referentiel general d'amelioration de l'accessibilite), the French application of WCAG 2.1 AA used as the accessibility yardstick for the DWWM certification.
What the DWWM expects: not a full 106-criteria audit, but demonstrated integration of the accessibility essentials in the produced interfaces and the ability to verify them with tools. The criteria map below tracks what the frontend implements and where; the companion document
docs/rgaa.mdexplains each criterion in depth.Criteria map (implemented)
aria-hiddenon the home code card and feature emojiaria-invalid), current nav item (bold + underline +aria-current)docs/design/theme-exploration.md(worst pair 4.73:1)lang="en"on pages,lang="fr"on the privacy policy<title>per pagelang="en"inside the French privacy pageh1per page describing the page, orderedh2/h3header/nav/main/footerlandmarks via the layout fragmentsul/li:focus-visibleoutline, never removedlabel foron every inputtype="email",required, server-side Bean Validationrole="alert"summary plus per-field message wired witharia-describedbyautocomplete="username" / "email" / "new-password" / "current-password"prefers-reduced-motionRemaining work