Skip to content
https://SOLIDARITES.ORG

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
8
REVIEW
2
PASS
14
INFO
0
Checks
24
14 PASS 2 REVIEW 8 FIX
F
Form Accessibility
Action
14 of 18 controls have issues
FIX
14 of 18 controls have issues
Critical::
10 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="searchsubmit">; <input type="submit" id="searchsubmit">; <input type="submit">; <input type="submit" id="searchsubmit">; <input type="submit" id="searchsubmit">; <input type="submit">; <select id="missions-current">; <select id="missions-previous">; <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="desktop-don-libre-montant">; <input type="text" id="desktop-don-libre-montant">; <input type="text" name="PRENOM">; <input type="email" name="email">
Info::
4 control(s) properly labeled
18 controls
4 labeled
4 placeholder only
10 unlabeled
ControlTypeLabelMethod
#stextRechercher:for/id
#stextRechercher:for/id
#stextRechercher:for/id
#stextRechercher:for/id
#desktop-don-libre-montanttext(Montant libre)placeholder only
#desktop-don-libre-montanttext(Montant libre)placeholder only
PRENOMtext(Prénom)placeholder only
emailemail(Email*)placeholder only
#searchsubmitsubmit(none)none
#searchsubmitsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none
#missions-currentselect(none)none
#missions-previousselect(none)none
#searchsubmitsubmit(none)none
#searchsubmitsubmit(none)none
inputsubmit(none)none
#g-recaptcha-responsetextarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" id="searchsubmit">; <input type="submit" id="searchsubmit">; <input type="submit">; <input type="submit" id="searchsubmit">; <input type="submit" id="searchsubmit">; <input type="submit">; <select id="missions-current">; <select id="missions-previous">; <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" id="desktop-don-libre-montant">; <input type="text" id="desktop-don-libre-montant">; <input type="text" name="PRENOM">; <input type="email" name="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" name="email">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="email">
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-n7bqdo
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://SOLIDARITES.ORG/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://SOLIDARITES.ORG/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 28 passed
REVIEW
83

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JE FAIS UN DON div.container > div#banner > div#donation-link > a.btn-rouge
JE FAIS UN DON div.container > div#banner > div#donation-link > a.btn-rouge
Missions en cours Afghanistan Bénin Burkina Faso Cameroun Éthiopie France Haïti… div.container > div.col-right > form#missions-status > select#missions-current
Missions antérieures Albanie Angola Balkans Bangladesh Bosnie Burundi Colombie … div.container > div.col-right > form#missions-status > select#missions-previous
25 PAYS D'INTERVENTION div.container > div.col-right > ul#missions-chiffres > li
5,6 M PERSONNES SECOURUES div.container > div.col-right > ul#missions-chiffres > li
2 666 EMPLOYÉS NATIONAUX ET INTERNATIONAUX div.container > div.col-right > ul#missions-chiffres > li
div.sib_signup_box_inside_4 > div#sol-newsletter > p.field > input.sib-PRENOM-area div.sib_signup_box_inside_4 > div#sol-newsletter > p.field > input.sib-PRENOM-area
div.sib_signup_box_inside_4 > div#sol-newsletter > p.field > input div.sib_signup_box_inside_4 > div#sol-newsletter > p.field > input
div.sib_signup_box_inside_4 > div#sol-newsletter > p.field > input div.sib_signup_box_inside_4 > div#sol-newsletter > p.field > input
Vos coordonnées sont utilisées pour vous envoyer nos actualités et faire appel … form#sib_signup_form_4 > div.sib_signup_box_inside_4 > div#sol-newsletter > p.mention-rgpd
En savoir plus sur la gestion de vos données et vos droits. div.sib_signup_box_inside_4 > div#sol-newsletter > p.mention-rgpd > a
EAU3 div.row > div.col-xs-12 > div.don-entry > strong
EAU5 div.row > div.col-xs-12 > div.don-entry > strong
EAU10 div.row > div.col-xs-12 > div.don-entry > strong

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
En savoir plus sur la gestion de vos données et vos droits. div.sib_signup_box_inside_4 > div#sol-newsletter > p.mention-rgpd > a

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Missions en cours Afghanistan Bénin Burkina Faso Cameroun Éthiopie France Haïti… div.container > div.col-right > form#missions-status > select#missions-current
Missions antérieures Albanie Angola Balkans Bangladesh Bosnie Burundi Colombie … div.container > div.col-right > form#missions-status > select#missions-previous

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
div.owl-wrapper > div.owl-item > div.don > a.link-image div.owl-wrapper > div.owl-item > div.don > a.link-image
div.owl-wrapper > div.owl-item > div.don > a.link-image div.owl-wrapper > div.owl-item > div.don > a.link-image
div.owl-wrapper > div.owl-item > div.don > a.link-image div.owl-wrapper > div.owl-item > div.don > a.link-image

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Continuer sans accepter div.sc-aemIz > div.sc-idOiZg > div.sc-dIUeWJ > button.sc-gsxoIA
J'accepte div.sc-aemIz > div.sc-idOiZg > div.sc-hKgJUU > button#axeptio_btn_acceptAll
○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
●`[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
●Input buttons have discernible text.
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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
●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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
A
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
25 headings
PASS
25 headings
Info::
Single H1 present
  • H1 Ce qui nous lie est-il plus fort
  • H2 En direct du terrain
  • H3 Trois années d’horreur à Gaza : les chiffres qui racontent…
  • H3 Saturnisme : en France, une menace toujours présente
  • H3 Anticiper les effets dramatiques d’El Niño
  • H3 Yémen : déplacements et pénuries d’eau aggravent les besoins humanitaires
  • H3 Ebola : SOLIDARITÉS INTERNATIONAL en première ligne grâce à son…
  • H3 Que connaissez-vous de la sécurité alimentaire ?
  • H3 Séisme au Venezuela : SOLIDARITÉS INTERNATIONAL mobilisée
  • H3 Vidéos : Gaza entre pénuries et insalubrité
  • H3 Rétablir l’eau, l’abri et l’espoir aux Ukrainiens touchés par la…
  • H3 Séismes au Venezuela : SOLIDARITÉS INTERNATIONAL se mobilise en urgence
  • H3 Témoignages : rétablir l’accès à l’eau potable dans les écoles…
  • H3 Gaza, au bord du monde
  • H2 Actualités de l'association
  • H2 S'informer c'est déjà aider plus loin
  • H2 Vos dons en action
  • H3 35€ soit 8,75€ après déduction fiscale
  • H3 80€ soit 20€ après déduction fiscale
  • H3 102€ soit 25,50€ après déduction fiscale
  • H3 35€ soit 8,75€ après déduction fiscale
  • H3 80€ soit 20€ après déduction fiscale
  • H3 102€ soit 25,50€ après déduction fiscale
  • H2 Je fais un don par SMS
  • H2 Postes à pourvoir
A+
Heading Text Quality
All 25 heading(s) have substantive, well-formed text
PASS
All 25 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 75 images OK
PASS
All 75 images OK
Info::
63 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
75 images 12 good alt text 63 decorative
All images have appropriate alt text.
A+
Form Input Types
18 form control(s) checked, no type mismatches
PASS
18 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
18 form control(s) checked, no input-semantic issues
PASS
18 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "fr-FR"
PASS
Lang attribute set to "fr-FR"
Info::
<html lang="fr-FR"> is set and valid
Got: fr-FR
A+
Tabindex Anti-Patterns
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/4 iframe(s) missing title; 0 placeholder(s)
PASS
1/4 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+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 54 visible text node(s) render at >= 12 CSS pixels
PASS
All 54 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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)
ElementRatioRequiredFGBGResult
h2 En direct du13.36:13.0:1
#000000
#CFCECD
Pass
h2 Actualités de13.36:13.0:1
#000000
#CFCECD
Pass
h2 S'informer c'est dé…13.36:13.0:1
#000000
#CFCECD
Pass
h2 Vos dons en13.36:13.0:1
#000000
#CFCECD
Pass
h2 Je fais un don par13.36:13.0:1
#000000
#CFCECD
Pass
h2 Postes à13.36:13.0:1
#000000
#CFCECD
Pass
h3 Trois années d’ho…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Saturnisme : en Fran…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Anticiper les effets…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Yémen : déplacemen…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Ebola : SOLIDARITÉS…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Que connaissez-vous …13.36:13.0:1
#000000
#CFCECD
Pass
h3 Séisme au Venezuela…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Vidéos : Gaza entre…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Rétablir l’eau, l…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Séismes au Venezuel…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Témoignages : réta…13.36:13.0:1
#000000
#CFCECD
Pass
h3 Gaza, au bord du mon…13.36:13.0:1
#000000
#CFCECD
Pass
title SOLIDARITÉS INTERNA…20.82:14.5:1
#000000
#FEFEFE
Pass
a Espace donateur21.00:14.5:1
#000000
#FFFFFF
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback