Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Landmark Structure

Action

4 landmarks

FIX

4 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page introuvable (404) ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

2 pass 18 fail WCAG AA

h1 Transformez Votre Vie

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Avec Nos 3 Expertises

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Nos 3 Expertises Intégrées

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Commencez Gratuitement

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ce Que Disent Nos Clients

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Questions Fréquentes

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Prêt à Transformer Votre Vie ?

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Coaching Progressif

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Astrologie Personnalisée

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Chiromancie Intelligente

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Formation Main 5 Jours

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Météo du Couple

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Challenge 7 Jours

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

19px · bottom of viewport

h3 🍪 Respect de votre vie privée

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ⚙️ Personnaliser vos préférences c…

2.77:1

#000000

#5F3FA9

needs 3.0:1 (large text)

19px · bottom of viewport

span Votre guidance personnalisée

2.27:1

#000000

#513591

needs 4.5:1 (normal text)

16px · top of page (header area)

a Astrologie

2.29:1

#000000

#523593

needs 4.5:1 (normal text)

16px · top of page (header area)

div Horoscopes

2.32:1

#000000

#533694

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Transformez Votre Vi…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h1 Avec Nos 3 Expertise…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h2 Nos 3 Expertises Int…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h2 Commencez Gratuiteme…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h2 Ce Que Disent Nos Cl…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h2 Questions Fréquente…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h2 Prêt à Transformer…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h3 Coaching Progressif	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h3 Astrologie Personnal…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h3 Chiromancie Intellig…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h3 Formation Main 5 Jou…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h3 Météo du Couple	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h3 Challenge 7 Jours	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h3 🍪 Respect de votr…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
h3 ⚙️ Personnaliser…	2.77:1	3.0:1	#000000	#5F3FA9	Fail
title MYMOONOVA - Dévelop…	9.90:1	4.5:1	#000000	#B2B2B2	Pass
a MyMoonova	9.90:1	4.5:1	#000000	#B2B2B2	Pass
span Votre guidance perso…	2.27:1	4.5:1	#000000	#513591	Fail
a Astrologie	2.29:1	4.5:1	#000000	#523593	Fail
div Horoscopes	2.32:1	4.5:1	#000000	#533694	Fail

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.

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H1 Transformez Votre VieAvec Nos 3 Expertises
H2 Nos 3 Expertises Intégrées
H3 Coaching Progressif
H3 Astrologie Personnalisée
H3 Chiromancie Intelligente
H2 Commencez Gratuitement
H3 Formation Main 5 Jours
H3 Météo du Couple
H3 Challenge 7 Jours
H2 Ce Que Disent Nos Clients
H2 Questions Fréquentes
H2 Prêt à Transformer Votre Vie ?
H3 🍪 Respect de votre vie privée
H3 ⚙️ Personnaliser vos préférences cookies

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#chatbot-input	text	Votre message	aria-label
#cookie-essential	checkbox		none
#cookie-analytics	checkbox		none
#cookie-marketing	checkbox		none
#cookie-preferences	checkbox		none

A+

Link & Button Quality

75 links, 11 buttons — all OK

PASS

75 links, 11 buttons — all OK

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /mymoonova/public/pages/legal/confidentialite.php

74 link(s) with descriptive text

75 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/mymoonova/public/pages/legal/confidenti…	Politique de confidentialité	new tab	Add '(opens in new tab)' to text

85 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

/mymoonova/public/pages/legal/confidentialite.php

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

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 22 passed

PASS

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
3 ressources offertes pour découvrir MYMOONOVA sans engagement ni carte bancair… `div.homepage-content > section.section > div.container > p.section-subtitle`
Gratuit · Sans carte bancaire · Annulable a tout moment `section.section > div.container > div.inscription-rapide > p.inscription-rapide-hint`
Lyon `div.container > div.testimonials-grid > div.testimonial-card > div.testimonial-location`
Paris `div.container > div.testimonials-grid > div.testimonial-card > div.testimonial-location`
Bordeaux `div.container > div.testimonials-grid > div.testimonial-card > div.testimonial-location`

These are opportunities to improve the legibility of your content.

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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

○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.

○Image elements have `[alt]` attributes

○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.

○No element has a `[tabindex]` value greater than 0

○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.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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.