Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

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

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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

4 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 4 <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

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page introuvable (404) | Mathéo Olsen ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Développeur Web Freelance à Reims

1.20:1

#000000

#181B08

needs 3.0:1 (large text)

32px · above the fold

h2 Les chiffres parlent

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Des solutions sur mesure

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Là où créativité

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Des résultats

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Vous avez des questions ?

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Lancez votre

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 projet avec

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Un projet en tête ?

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Navigation

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Services

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Informations légales

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Derniers articles

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Site Vitrine

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Application Métier

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Landing Page

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

19px · bottom of viewport

h3 E-commerce

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Refonte

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

19px · bottom of viewport

h3 NXTEP

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

19px · bottom of viewport

h3 NXTEP Blog

1.07:1

#000000

#0B0B09

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Développeur Web Fre…	1.20:1	3.0:1	#000000	#181B08	Fail
h2 Les chiffres parlent	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Des solutions sur me…	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Là où créativité	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Des résultats	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Vous avez des questi…	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Lancez votre	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 projet avec	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Un projet en tête ?	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Navigation	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Services	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Informations légale…	1.07:1	3.0:1	#000000	#0B0B09	Fail
h2 Derniers articles	1.07:1	3.0:1	#000000	#0B0B09	Fail
h3 Site Vitrine	1.07:1	3.0:1	#000000	#0B0B09	Fail
h3 Application Métier	1.07:1	3.0:1	#000000	#0B0B09	Fail
h3 Landing Page	1.07:1	3.0:1	#000000	#0B0B09	Fail
h3 E-commerce	1.07:1	3.0:1	#000000	#0B0B09	Fail
h3 Refonte	1.07:1	3.0:1	#000000	#0B0B09	Fail
h3 NXTEP	1.07:1	3.0:1	#000000	#0B0B09	Fail
h3 NXTEP Blog	1.07:1	3.0:1	#000000	#0B0B09	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.

Landmark Structure

20 landmarks

PASS

20 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

34 headings

PASS

34 headings

Single H1 present

H1 Développeur Web Freelance à Reims
H2 Clients satisfaits
H2 Technologies maîtrisées
H2 Les chiffres parlent
H2 Des solutions sur mesurepour chaque besoin
H3 Site Vitrine
H3 Application Métier
H3 Landing Page
H3 E-commerce
H3 Refonte
H2 Là où créativitérencontre performance
H3 NXTEP
H3 NXTEP Blog
H3 StatueAddict'Z
H3 SwordTales
H2 Des résultatsqui parlent d'eux-mêmes
H2 Vous avez des questions ?
H3 Comment se déroule un projet avec vous ?
H3 Pourquoi choisir un développeur freelance à Reims plutôt qu'une agence ?
H3 Quels sont les délais pour créer mon site ?
H3 Puis-je voir et ajuster mon site pendant le développement ?
H3 Comment fonctionnent vos tarifs ?
H3 Pourquoi investir dans un site sur mesure plutôt qu'utiliser Wix ou un template ?
H3 Que se passe-t-il après la mise en ligne ?
H2 Lancez votreprojet avecun expertdu web
H3 Parlons de votre projet
H2 Un projet en tête ?
H2 Navigation
H2 Services
H2 Informations légales
H2 Derniers articles& conseils
H3 Création de Site Internet à Reims : Guide Complet 2026
H3 Combien Coûte un Site Internet en 2026 ? Prix Réels et Complets
H3 Site Vitrine Professionnel : Le Guide Complet 2026

Alt Text Quality

All 9 images OK

PASS

All 9 images OK

3 image(s) with alt text over 125 characters

6 image(s) with good alt text

9 images 6 good alt text

Issue	Count
too long	3 image(s)

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
#_R_59lbr5udb_-name	text	Nom *(obligatoire)	for/id
#_R_59lbr5udb_-email	email	Email *(obligatoire)	for/id
#_R_59lbr5udb_-project	select	Type de projet *(obligatoire)	for/id
#_R_59lbr5udb_-budget	select	Budget estimé	for/id
#_R_59lbr5udb_-message	textarea	Décrivez votre projet *(obligatoire)	for/id

Link & Button Quality

63 links, 15 buttons — all OK

PASS

63 links, 15 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://nxtep.fr; https://rinaorc.com; https://fr.linkedin.com/in/mathéo-olsen-aa2903292; https://github.com/NeosiaNexus

59 link(s) with descriptive text

63 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://nxtep.fr	Visiter le site de NXTEP	new tab	Add '(opens in new tab)' to text
https://rinaorc.com	Visiter le site de Rinaorc Stu…	new tab	Add '(opens in new tab)' to text
https://fr.linkedin.com/in/mathéo-olsen…	Suivez-moi sur LinkedIn (nouve…	new tab	Add '(opens in new tab)' to text
https://github.com/NeosiaNexus	Suivez-moi sur GitHub (nouvell…	new tab	Add '(opens in new tab)' to text

74 links and buttons have descriptive text

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

https://nxtep.fr; https://rinaorc.com; https://fr.linkedin.com/in/mathéo-olsen-aa2903292; https://github.com/NeosiaNexus

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 97/100 — 1 failing, 29 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.

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
div.animate-fade-in-up > div.mt-8 > div.pt-2 > a.group `div.animate-fade-in-up > div.mt-8 > div.pt-2 > a.group`

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.

●Select elements have associated label elements.

●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

●`<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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

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