As a certified RGAA accessibility specialist with over 7 years in web development, I’ve often noticed how even experienced teams underestimate the structural obligations defined by RGAA, especially compared to the broader WCAG guidelines. This article explores how the two standards differ when it comes to page titles, navigation, button semantics and required HTML5 elements.
Page Titles (<title>)
WCAG requires that each page have a descriptive title (SC 2.4.2), but it doesn’t define strict formatting or site-wide uniqueness.
RGAA, on the other hand:
- Requires a
<title>tag on every page (RGAA 8.5 [A]) - It must be relevant, precise, and ideally unique across the site (RGAA 8.6 [A])
- Titles must clearly reflect the purpose or content of the page – generic or reused titles are not compliant.
Why it matters: This strictness avoids confusion for screen reader users who rely on titles to understand where they are.
Navigation (<nav>)
WCAG encourages multiple ways to navigate content (SC 2.4.5) and requires keyboard accessibility and visible focus (SC 2.1.1, 2.4.7), but doesn’t enforce specific HTML structure.
RGAA mandates:
- Use of semantic
<nav>tags for primary and secondary navigation (RGAA 9.2 [A]) - Burger menus must be inside
<nav> - All navigation must be keyboard-operable and logically ordered
Why it matters: It ensures a consistent experience across screen readers and keyboard-only navigation.
Structural HTML5 Tags
WCAG only recommends logical structure using headings and landmarks (SC 1.3.1, 2.4.1), leaving tag choice to developers.
RGAA strictly requires:
- Use of:
<header><main>(must be unique on the page)<footer><nav>(for all navigation)
<aside>for secondary or non-critical content (optional)
(RGAA 9.2 [A])
Why it matters: These landmarks help assistive technologies create a reliable “map” of the page, ensuring consistent navigation models across sites.
Buttons and roles
WCAG allows flexibility: as long as an interactive element behaves accessibly (focusable, labeled, operable), its tag or role doesn’t matter much.
RGAA enforces correct semantic use:
- Use
<button>for actions, not clickable<div>or<span>(RGAA 8.9 [A]) - ARIA roles like
role="button"are only accepted when absolutely necessary - Duplicate roles or misused attributes lead to non-conformance
Why it matters: Correct semantics ensure native accessibility, reducing reliance on fragile ARIA fixes.
Mandatory elements summary (RGAA / WCAG)
| Element | Required by RGAA | Optional in WCAG |
|---|---|---|
<title> | Yes | Yes |
<main> | Yes, only once | Not required |
<nav> | Yes | Not required |
| Skip Links | Yes | Recommended |
| Semantic Buttons | Yes | Indirectly |
<header>, <footer> | Yes | Optional |
While WCAG provides a broad, international framework focused on functional outcomes, RGAA defines a more prescriptive and enforceable structure, especially regarding HTML semantics and layout.
Understanding these differences isn’t just a technical detail—it’s a way to build cleaner, more inclusive, legally compliant websites in France and across Europe.
Leave a Reply