Skip to content
https://ecolecybele.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
D
Alt Text Quality
Action
5 of 35 images have issues
FIX
5 of 35 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
6 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
35 images 24 good alt text 6 decorative 5 missing
IssueCount
missing5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Tap Target Adequacy
Action
12 tap target(s) too small or too close together
FIX
12 tap target(s) too small or too close together
Warning::
12 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.
D
Web Manifest
Action
Not found
FIX
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
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.

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

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

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

B
Heading Hierarchy
50 headings, 1 skip(s)
REVIEW
50 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Contact
  • H1 Formations Doula & Thanadoula
  • H2 ÉCOLE INTERNATIONALE
  • H2 D'ACCOMPAGNEMENT CYBÈLE
  • H3 De la naissance à la fin de vie : le cursus à large spectre d’excellence en accompagnement humain, 100 % EN LIGNE et accessible à toute la francophonie!
  • H1 Formations Doula & Thanadoula duplicate H1
  • H2 ÉCOLE INTERNATIONALE
  • H2 D'ACCOMPAGNEMENT CYBÈLE
  • H3 De la naissance à la fin de vie : le cursus à large spectre d’excellence en accompagnement humain, 100 % EN LIGNE et accessible à toute la francophonie!
  • H2 Choisissez votre voie : nos deux cursus d'excellence
  • H2 DEVENEZ DOULA
  • H3 Accompagnant(e) périnatal(e)
  • H2 DEVENEZ THANADOULA
  • H3 Accompagnant(e) à la fin de vie et au deuil
  • H2 Formation en ligne =  Flexibilité totale !
  • H4 La profondeur de cursus supérieurs skipped
  • H4 La flexibilité d'un réseau mondial
  • H4 La force d'un véritable accompagnement humain
  • H4 L'intelligence d'un budget maîtrisé
  • H2 Cette formation est-elle faite pour vous?
  • H3 Nous avons créé ces cursus pour celles et ceux qui ressentent un appel profond. Voyez si vous vous reconnaissez.
  • H3 Si ces aspirations résonnent en vous, vous êtes au bon endroit!
  • H2 Découvrez toutes les formations offertes par l'École Cybèle
  • H2 Reconnue par l'industrie, louangée par nos étudiants
  • H2 L'École Cybèle dans la presse
  • H2 Accréditations scolaires
  • H2 Associations professionnelles
  • H3 Volet doula
  • H3 Volet thanadoula
  • H2 Témoignages
  • H2 Nombreux autres témoignages sur Google!
  • H2 Rejoignez une communauté de 2 000+ accompagnants dans 40 pays!
  • H3 étudiants
  • H3 pays
  • H2 Prêt(e) à commencer votre propre chemin?
  • H2 DEVENEZ DOULA
  • H3 Accompagnant(e) périnatal(e)
  • H2 DEVENEZ THANADOULA
  • H3 Accompagnant(e) à la fin de vie et au deuil
  • H2 L'École Cybèle
  • H2 <img decoding="async" src="https://ecolecybele.com/wp-content/uploads/2025/04/CYBELE-blanc-1024x585.webp" width="151" height="86" alt="" class="wp-image-66799 aligncenter size-large" />
  • H3 Les certifications
  • H3 Autres pages
  • H4 Courriel
  • H4 Adresse
  • H4 Téléphone
  • H2 L'École Cybèle
  • H2 <img decoding="async" src="https://ecolecybele.com/wp-content/uploads/2025/04/CYBELE-blanc-1024x585.webp" width="151" height="86" alt="" class="wp-image-66799 aligncenter size-large" />
  • H3 Les certifications
  • H3 Autres pages

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
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
B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 25 passed
REVIEW
87

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
Accepter div#cmplz-cookiebanner-container > div#cmplz-cookiebanner-1-optin > div.cmplz-buttons > button.cmplz-btn
Articles 0 div.et_pb_menu_inner_container > div.et_pb_menu__wrap > a.et_pb_menu__icon > span.et_pb_menu__cart-count
De la naissance à la fin de vie : le cursus à large spectre d’excellence en acc… div.et_pb_column_6 > div.et_pb_text_5 > div.et_pb_text_inner > h3

These are opportunities to improve the legibility of your content.

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
La profondeur de cursus supérieurs div.et_pb_column_11 > div.et_pb_text_14 > div.et_pb_text_inner > h4.sg-title

These are opportunities to improve keyboard navigation in your application.

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

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
Go to slide 1 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 7 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 8 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 9 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 10 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 11 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 12 div#cdf-c-77757-33ec24 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet

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
●`[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
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●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
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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>`.
○Uses ARIA roles only on compatible elements
○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.
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 152 chars - H3: 152 chars - H2: 185 chars
Got: 3 >120-char heading(s)
Info::
8 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 8 all-caps heading(s)
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optincheckboxFonctionnelfor/id
#cmplz-preferences-optincheckboxPréférencesfor/id
#cmplz-statistics-optincheckboxStatistiquesfor/id
#cmplz-marketing-optincheckboxMarketingfor/id
A+
Form Input Types
4 form control(s) checked, no type mismatches
PASS
4 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
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
15 explicit tabindex attribute(s) checked, no anti-patterns
PASS
15 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 150 visible text node(s) render at >= 12 CSS pixels
PASS
All 150 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::
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 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
h1 Formations Doula & T…14.03:13.0:1
#000000
#D3D3D3
Pass
h1 Formations Doula & T…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 ÉCOLE INTERNATIONAL…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 D'ACCOMPAGNEMENT CYB…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 ÉCOLE INTERNATIONAL…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 D'ACCOMPAGNEMENT CYB…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 Choisissez votre voi…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 DEVENEZ DOULA14.03:13.0:1
#000000
#D3D3D3
Pass
h2 DEVENEZ THANADOULA14.03:13.0:1
#000000
#D3D3D3
Pass
h2 Formation en ligne =…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 Cette formation est-…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 Découvrez toutes le…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 L'École Cybèle dan…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 Accréditations scol…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 Rejoignez une commun…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 Prêt(e) à commence…14.03:13.0:1
#000000
#D3D3D3
Pass
h2 DEVENEZ DOULA14.03:13.0:1
#000000
#D3D3D3
Pass
h2 DEVENEZ THANADOULA14.03:13.0:1
#000000
#D3D3D3
Pass
h2 L'École Cybèle14.03:13.0:1
#000000
#D3D3D3
Pass
h2 L'École Cybèle14.03:13.0:1
#000000
#D3D3D3
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