The RGAA and the EAA require permanent access to the accessibility statement from every page of the site. In practice, this means a link in the footer — present everywhere, visible, and correctly worded. It's one of the quickest fixes to make, and one of the most scrutinised by the authorities, because its absence is immediately observable.
Why this link is mandatory
The accessibility statement is useless if no one can find it. The permanent-access obligation guarantees that a user — or an inspector — can reach it from any page, without hunting for it. The footer, present across the whole site, is the standard and expected place.
Recommended wording
"Accessibility: [status]" — where [status] is Full, Partial or Non-compliant. Example: "Accessibility: partial compliance". This wording, which states the level upfront, is the form expected by the authorities. A plain "Accessibility" is acceptable, but less explicit.
Integration by platform
- →PrestaShop: BO → Design → Footer links (or the "Link List" module) → add a URL to /accessibilite
- →WooCommerce / WordPress: Appearance → Menus → Footer location → add a custom link
- →Nuxt: add an entry to the links array of the AppFooter component
- →Shopify: Content → Menus → Footer → add an item pointing to the page
// The trap of the link that points nowhere
An "Accessibility" link that leads to a 404 or empty page is worse than no link: it proves you knew the obligation without meeting it. Check that /accessibilite exists and contains a real statement before publishing the link.
Check in 30 seconds
- 01Open any page of the site
- 02Scroll down to the footer
- 03Confirm the "Accessibility" link is present and clickable
- 04Click: the statement must display
Frequently asked questions
Must the link be on absolutely every page?
Yes: access must be permanent. Since the footer is shared across the whole site, adding it once to the footer covers all pages, including the purchase funnel.
Can I put it in a dropdown rather than visible?
The spirit of the text is direct, visible access. A link buried in a barely accessible submenu defeats the purpose. Prefer a visible footer link, itself reachable by keyboard.
Does it need a link separate from the legal notices?
Yes: the accessibility statement is a document distinct from the legal notices and the terms. Give it its own link, don't fold it into another page.
What exact text for the link?
"Accessibility: partial compliance" is the clearest and most expected wording. If you prefer to stay plain, "Accessibility" alone is accepted, provided the target page clearly states the compliance status.
Should the link open in a new tab?
No, it's not necessary and it's even discouraged: an unexpected tab change disorients screen-reader users. A normal internal link to /accessibilite is enough.
What if my footer is already very crowded?
The Accessibility link must stay visible, not buried. Group it with the legal links (Legal notices, Terms, Privacy): that's the usual and most logical place for the user.
Do I also need a link in the sitemap?
It's not mandatory if the footer link appears on every page, but adding it to the HTML sitemap costs nothing and reinforces access to the statement.
Check that your statement and its footer link are properly in place:
→ Run an audit