https://melenchon2027.fr
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
72
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
2412 PASS 5 REVIEW 7 FIX
DLandmark StructureAction18 landmarksFIX
Landmark Structure
Action18 landmarks
18 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
12 <nav> landmark(s) found
Warning::
5 of 12 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Why this matters
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
Multiple navigations need aria-label to distinguish them for screen readers.
Why this matters
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Why this matters
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
FHeading HierarchyAction41 headings, 7 skip(s)FIX
Heading Hierarchy
Action41 headings, 7 skip(s)
41 headings, 7 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- H4 Le corpus de la France insoumise
- H2 L'Avenir en commun, édition 2025
- H2 Les livrets 2022
- H2 Les plans 2022
- H2 Programme de la NUPES 2022
- H2 Programme du NFP 2024
- H4 Le processus programmatique skipped
- H2 Comment a été conçu le programme
- H2 La construction du programme pour 2027
- H2 Actualités des groupes thématiques
- H2 Rejoindre un groupe thématique pour contribuer
- H4 Le corpus de la France insoumise skipped
- H2 L'Avenir en commun, édition 2025
- H2 Les livrets 2022
- H2 Les plans 2022
- H2 Programme de la NUPES 2022
- H2 Programme du NFP 2024
- H4 Le processus programmatique skipped
- H2 Comment a été conçu le programme
- H2 La construction du programme pour 2027
- H2 Actualités des groupes thématiques
- H2 Rejoindre un groupe thématique pour contribuer
- H2 Partagez l’appel à soutiens
- H6 Déjà 241 332 soutiens ! skipped
- H6 Élection présidentielle 2027
- H2 Soutenez la candidature de Jean‑Luc Mélenchon
- H2 Lettre au peuple de France
- H2 Lettre au peuple de France
- H2 Le programme
- H6 Participez à L’Avenir en commun skipped
- H2 Bientôt : les contributions citoyennes sur le programme
- H2 Dons
- H6 Soutien financier skipped
- H2 Faites un don pour la campagne
- H2 Commandez le matériel de campagne
- H2 Commandez le matériel de campagne
- H6 Élection présidentielle 2027 skipped
- H2 Soutenez la candidature de Jean‑Luc Mélenchon
- H2 Le menu
- H2 Les réseaux
- H2 Les sites amis
Every page should have one H1 that describes the page content.
Why this matters
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
DTabindex Anti-PatternsAction0 positive, 62 -1-on-focusableFIX
Tabindex Anti-Patterns
Action0 positive, 62 -1-on-focusable
0 positive, 62 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="sm-17784209852597253-1">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="sm-17784209852597253-3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
DWeb ManifestActionNot foundFIX
Web Manifest
ActionNot found
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
BAlt Text Quality2 of 19 images have issuesREVIEW
Alt Text Quality
2 of 19 images have issues
2 of 19 images have issues
Warning::
2 image(s) with generic alt text
Info::
9 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
19 images 6 good alt text 2 decorative 2 generic
| Issue | Count |
|---|---|
| generic | 2 image(s) |
| too long | 9 image(s) |
BLink & Button Quality1 issue(s) across 161 links and 6 buttonsREVIEW
Link & Button Quality
1 issue(s) across 161 links and 6 buttons
1 issue(s) across 161 links and 6 buttons
Critical::
1 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: #top
Warning::
56 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: https://actionpopulaire.fr/dons/; https://actionpopulaire.fr/dons/; https://melenchon2027.fr/wp-content/uploads/2026/04/PROGRAMME-FRONT-POPULAIRE…; https://melenchon2027.fr/wp-content/uploads/2026/04/PROGRAMME-FRONT-POPULAIRE…; https://actionpopulaire.fr/dons/; https://actionpopulaire.fr/dons/; https://melenchon2027.fr/wp-content/uploads/2026/04/PROGRAMME-FRONT-POPULAIRE…; https://melenchon2027.fr/wp-content/uploads/2026/04/PROGRAMME-FRONT-POPULAIRE…; https://www.facebook.com/sharer/sharer.php?u=https%3A//melenchon2027.fr; https://twitter.com/intent/post?text=Je%20soutiens%20la%20candidature%20de%20… (+46 more)
Info::
104 link(s) with descriptive text
161 links
1 empty
0 generic text
56 new tab
0 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://actionpopulaire.fr/dons/ | Faire un don | new tab | Add '(opens in new tab)' to text |
| https://actionpopulaire.fr/dons/ | Faire un don | new tab | Add '(opens in new tab)' to text |
| https://melenchon2027.fr/wp-content/uplo… | Programme du NFP 2024 | new tab | Add '(opens in new tab)' to text |
| https://melenchon2027.fr/wp-content/uplo… | Programme du NFP 2024 | new tab | Add '(opens in new tab)' to text |
| https://actionpopulaire.fr/dons/ | Faire un don | new tab | Add '(opens in new tab)' to text |
| https://actionpopulaire.fr/dons/ | Faire un don | new tab | Add '(opens in new tab)' to text |
| https://melenchon2027.fr/wp-content/uplo… | Programme du NFP 2024 | new tab | Add '(opens in new tab)' to text |
| https://melenchon2027.fr/wp-content/uplo… | Programme du NFP 2024 | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/sharer/sharer.p… | new tab | Add '(opens in new tab)' to text | |
| https://twitter.com/intent/post?text=Je%… | X-twitter | new tab | Add '(opens in new tab)' to text |
| https://t.me/share/url?url=https%3A//mel… | Telegram | new tab | Add '(opens in new tab)' to text |
| https://www.threads.com/intent/post?text… | Threads | new tab | Add '(opens in new tab)' to text |
| https://api.whatsapp.com/send?text=Je%20… | new tab | Add '(opens in new tab)' to text | |
| https://actionpopulaire.fr/soutien/infor… | J'habite à l'étranger | new tab | Add '(opens in new tab)' to text |
| https://lafranceinsoumise.fr/principes/ | les Principes | new tab | Add '(opens in new tab)' to text |
| https://actionpopulaire.fr/dons/ | faire un don | new tab | Add '(opens in new tab)' to text |
| https://materiel.actionpopulaire.fr/ | Je commande | new tab | Add '(opens in new tab)' to text |
| https://materiel.actionpopulaire.fr/ | Je commande | new tab | Add '(opens in new tab)' to text |
| https://materiel.actionpopulaire.fr/ | Illustration montrant une tort… | new tab | Add '(opens in new tab)' to text |
| https://materiel.actionpopulaire.fr/ | Affiche de campagne La France … | new tab | Add '(opens in new tab)' to text |
| https://actionpopulaire.fr/soutien/infor… | J'habite à l'étranger | new tab | Add '(opens in new tab)' to text |
| https://lafranceinsoumise.fr/principes/ | les Principes | new tab | Add '(opens in new tab)' to text |
| https://actionpopulaire.fr/financer/ | Faire un don | new tab | Add '(opens in new tab)' to text |
| https://actionpopulaire.fr/financer/ | Faire un don | new tab | Add '(opens in new tab)' to text |
| https://whatsapp.com/channel/0029VaF8ghI… | new tab | Add '(opens in new tab)' to text | |
| https://t.me/JLMelenchon | Telegram | new tab | Add '(opens in new tab)' to text |
| https://www.twitch.tv/jlmelenchon | Twitch | new tab | Add '(opens in new tab)' to text |
| https://www.youtube.com/@JLMelenchon | Youtube | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/jlmelenchon/ | new tab | Add '(opens in new tab)' to text | |
| https://www.tiktok.com/@jlmelenchon | Tiktok | new tab | Add '(opens in new tab)' to text |
| https://x.com/jlmelenchon | X | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/JLMelenchon | new tab | Add '(opens in new tab)' to text | |
| https://www.threads.com/@jlmelenchon | Threads | new tab | Add '(opens in new tab)' to text |
| https://bsky.app/profile/jlmelenchon.bsk… | Bluesky | new tab | Add '(opens in new tab)' to text |
| https://whatsapp.com/channel/0029VaF8ghI… | new tab | Add '(opens in new tab)' to text | |
| https://t.me/JLMelenchon | Telegram | new tab | Add '(opens in new tab)' to text |
| https://www.twitch.tv/jlmelenchon | Twitch | new tab | Add '(opens in new tab)' to text |
| https://www.youtube.com/@JLMelenchon | Youtube | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/jlmelenchon/ | new tab | Add '(opens in new tab)' to text | |
| https://www.tiktok.com/@jlmelenchon | Tiktok | new tab | Add '(opens in new tab)' to text |
| https://x.com/jlmelenchon | X | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/JLMelenchon | new tab | Add '(opens in new tab)' to text | |
| https://www.threads.com/@jlmelenchon | Threads | new tab | Add '(opens in new tab)' to text |
| https://bsky.app/profile/jlmelenchon.bsk… | Bluesky | new tab | Add '(opens in new tab)' to text |
| https://actionpopulaire.fr/ | Action populaire | new tab | Add '(opens in new tab)' to text |
| https://lafranceinsoumise.fr/ | La France insoumise | new tab | Add '(opens in new tab)' to text |
| https://melenchon.fr/ | Blog de Jean-Luc Mélenchon | new tab | Add '(opens in new tab)' to text |
| https://linsoumission.fr/ | L’insoumission | new tab | Add '(opens in new tab)' to text |
| https://desintox.lafranceinsoumise.fr/ | Désintox | new tab | Add '(opens in new tab)' to text |
| https://discord.gg/lfi | Le discord | new tab | Add '(opens in new tab)' to text |
| https://actionpopulaire.fr/ | Action populaire | new tab | Add '(opens in new tab)' to text |
| https://lafranceinsoumise.fr/ | La France insoumise | new tab | Add '(opens in new tab)' to text |
| https://melenchon.fr/ | Blog de Jean-Luc Mélenchon | new tab | Add '(opens in new tab)' to text |
| https://linsoumission.fr/ | L’insoumission | new tab | Add '(opens in new tab)' to text |
| https://desintox.lafranceinsoumise.fr/ | Désintox | new tab | Add '(opens in new tab)' to text |
| https://discord.gg/lfi | Le discord | new tab | Add '(opens in new tab)' to text |
| #top | (empty) | empty | Add link text or aria-label |
110 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
#top
Why this matters
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://actionpopulaire.fr/dons/; https://actionpopulaire.fr/dons/; https://melenchon2027.fr/wp-content/uploads/2026/04/PROGRAMME-FRONT-POPULAIRE…; https://melenchon2027.fr/wp-content/uploads/2026/04/PROGRAMME-FRONT-POPULAIRE…; https://actionpopulaire.fr/dons/; https://actionpopulaire.fr/dons/; https://melenchon2027.fr/wp-content/uploads/2026/04/PROGRAMME-FRONT-POPULAIRE…; https://melenchon2027.fr/wp-content/uploads/2026/04/PROGRAMME-FRONT-POPULAIRE…; https://www.facebook.com/sharer/sharer.php?u=https%3A//melenchon2027.fr; https://twitter.com/intent/post?text=Je%20soutiens%20la%20candidature%20de%20… (+46 more)
Why this matters
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
BTap Target Adequacy2 tap target(s) too small or too close togetherREVIEW
Tap Target Adequacy
2 tap target(s) too small or too close together
2 tap target(s) too small or too close together
Info::
2 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B404 Error PageHTTP 404, custom pageREVIEW
404 Error Page
HTTP 404, custom page
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - Mélenchon 2027 : Soutenez ma candidature à l’élection présidentielle ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
CFavicon & BrandingAction3 icon(s) detectedREVIEW
Favicon & Branding
Action3 icon(s) detected
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A+Heading Text QualityAll 41 heading(s) have substantive, well-formed textPASS
Heading Text Quality
All 41 heading(s) have substantive, well-formed text
All 41 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+Form AccessibilityAll 12 controls labeledPASS
Form Accessibility
All 12 controls labeled
All 12 controls labeled
Info::
12 control(s) properly labeled
12 controls
12 labeled
0 placeholder only
0 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| #form-field-firstName | text | Prénom | for/id |
| #form-field-lastName | text | Nom | for/id |
| #form-field-email | Adresse e-mail | for/id | |
| #form-field-contactPhone | tel | Téléphone | for/id |
| #form-field-zip | number | Code postal | for/id |
| #form-field-consentAP-0 | checkbox | En soutenant la campagne, j'accepte de recevoir les informations de la France insoumise et je m'engage à en respecter les Principes et le programme.* | for/id |
| #form-field-firstName | text | Prénom | for/id |
| #form-field-lastName | text | Nom | for/id |
| #form-field-email | Adresse e-mail | for/id | |
| #form-field-contactPhone | tel | Téléphone | for/id |
| #form-field-zip | number | Code postal | for/id |
| #form-field-consentAP-0 | checkbox | En soutenant la campagne, j'accepte de recevoir les informations de la France insoumise et je m'engage à en respecter les Principes et le programme.* | for/id |
A+Form Input Types12 form control(s) checked, no type mismatchesPASS
Form Input Types
12 form control(s) checked, no type mismatches
12 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+Form Input Quality12 form control(s) checked, no input-semantic issuesPASS
Form Input Quality
12 form control(s) checked, no input-semantic issues
12 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
Mobile Keyboard & Autofill
No autofill-eligible form controls
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+Document LanguageLang attribute set to "fr-FR"PASS
Document Language
Lang attribute set to "fr-FR"
Lang attribute set to "fr-FR"
Info::
<html lang="fr-FR"> is set and valid
Got: fr-FR
AIframe Accessibility1/1 iframe(s) missing title; 0 placeholder(s)PASS
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+Mobile-Readable Font SizesAll 86 visible text node(s) render at >= 12 CSS pixelsPASS
Mobile-Readable Font Sizes
All 86 visible text node(s) render at >= 12 CSS pixels
All 86 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+PWA DepthNo PWA depth issues detectedPASS
PWA Depth
No PWA depth issues detected
No PWA depth issues detected
Info::
No PWA depth issues detected
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
Mobile UX Depth
1 mobile-depth signal(s) detected
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
20 pass
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Partagez | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 l’appel à soutien… | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Soutenez la candidat… | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Lettre au peuple de … | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Lettre au peuple de … | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Le programme | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Bientôt : les contr… | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Dons | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Faites un don pou… | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Commandez le matéri… | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Commandez le matéri… | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Soutenez la candidat… | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Le menu | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Les réseaux | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| h2 Les sites amis | 20.48:1 | 3.0:1 | #000000 | #FFFCF4 | Pass |
| title JLM2027 Soutenir la … | 20.48:1 | 4.5:1 | #000000 | #FFFCF4 | Pass |
| a Aller au contenu | 20.48:1 | 4.5:1 | #000000 | #FFFCF4 | Pass |
| a Accueil | 20.48:1 | 4.5:1 | #000000 | #FFFCF4 | Pass |
| a Construction du prog… | 20.48:1 | 4.5:1 | #000000 | #FFFCF4 | Pass |
| a Le corpus de la Fran… | 20.48:1 | 4.5:1 | #000000 | #FFFCF4 | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
ALighthouse Accessibility AuditsScore 90/100 — 5 failing, 30 passedPASS
Lighthouse Accessibility Audits
Score 90/100 — 5 failing, 30 passed
90
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Déjà 250 349 soutiens ! div.e-con-inner > div.elementor-element > div.elementor-element > h6 |
Participez à L’Avenir en commun div.elementor-element > div.e-con-inner > div.elementor-element > h6.e-5725095-aa0ed69 |
Soutien financier div.elementor-element > div.e-con-inner > div.elementor-element > h6.e-561efdd-dab65ad |
Élection présidentielle 2027 div.e-con-inner > div.elementor-element > div.elementor-element > h6.e-5395e84-8f4a5fc |
These are opportunities to improve keyboard navigation in your application.
Names and labels
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Illustration montrant une tortue violette transportant des colis, reliée par de… div.elementor-element > div.elementor-element > div.e-con-inner > a.e-image-link-base |
div.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon |
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Aller au contenu body.home > a.skip-link |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
J'habite à l'étranger form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-number > a.etranger |
J'habite à l'étranger form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-number > a.etranger |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.