Accessibility

D

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

D

Heading Hierarchy

Action

13 headings, 3 skip(s)

FIX

13 headings, 3 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 .
H1 Good hair speaks louder than words… duplicate H1
H3 " EndisBarbers est la concrétisation d'un concept du barber idéal perçu skipped
H3 par son créateur, un lieu où l'on revient sans hésiter !
H3 Salon de coiffure situé à Genève « Eaux Vives ».
H3 Vous êtes les bienvenus ! "
H2 CE N'EST PAS JUSTE UNE COIFFURE,
H2 C'EST UNE EXPERIENCE.
H4 Vous donnez une coupe de cheveux légendaire avec un service traditionnel. Nous sélectionnons notre matériel avec soin parmi les marques les plus réputées. Grâce à un grand choix d’outils, ch skipped
H2 Nos Tarifs sur les coupes et nos produits mis en vente dans notre BARBERSHOP !
H2 Réservation
H4 Parce que les champions du monde doivent être beaux. skipped
H4 Clique sur l'icône pour accéder aux réseaux sociaux

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

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

F

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

D

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.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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.

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

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

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

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Favicon & Branding

11 icon(s) detected

REVIEW

11 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only

h2 CE N'EST PAS JUSTE UNE COIFFURE,

1.46:1

#000000

on

#232B2F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 C'EST UNE EXPERIENCE.

1.46:1

#000000

on

#232B2F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Réservation

1.46:1

#000000

on

#232B2F

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

title Endis Barbers

1.23:1

#000000

on

#1C1C1C

needs 4.5:1 (normal text)

16px · top of page (header area)

strong EndiS BarberS

1.23:1

#000000

on

#1C1C1C

needs 3.0:1 (large text)

16px · top of page (header area)

span Accueil

4.48:1

#000000

on

#677776

needs 4.5:1 (normal text)

16px · top of page (header area)

span Présentation

4.34:1

#000000

on

#647574

needs 4.5:1 (normal text)

16px · top of page (header area)

span Les Prix

4.34:1

#000000

on

#647574

needs 4.5:1 (normal text)

16px · above the fold

span Contactez-nous

4.08:1

#000000

on

#5F7170

needs 4.5:1 (normal text)

16px · above the fold

span Contactez-nous

3.97:1

#000000

on

#5D6F6F

needs 4.5:1 (normal text)

16px · above the fold

i …

3.88:1

#000000

on

#5A6E6C

needs 4.5:1 (normal text)

16px · above the fold

span Accueil

3.83:1

#000000

on

#596D6C

needs 4.5:1 (normal text)

16px · above the fold

span Présentation

3.76:1

#000000

on

#576C6A

needs 4.5:1 (normal text)

16px · above the fold

span Les Prix

3.64:1

#000000

on

#546A69

needs 4.5:1 (normal text)

16px · above the fold

span Contactez-nous

3.64:1

#000000

on

#546A69

needs 4.5:1 (normal text)

16px · above the fold

span Contactez-nous

3.59:1

#000000

on

#536968

needs 4.5:1 (normal text)

16px · above the fold

a Réserver

3.70:1

#000000

on

#556B6A

needs 4.5:1 (normal text)

16px · mid-page

span Accueil

3.55:1

#000000

on

#546866

needs 4.5:1 (normal text)

16px · mid-page

span Présentation

3.65:1

#000000

on

#546A6A

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 CE N'EST PAS JUSTE U…	1.46:1	3.0:1	#000000	#232B2F	Fail
h2 C'EST UNE EXPERIENCE…	1.46:1	3.0:1	#000000	#232B2F	Fail
h2 Réservation	1.46:1	3.0:1	#000000	#232B2F	Fail
title Endis Barbers	1.23:1	4.5:1	#000000	#1C1C1C	Fail
strong EndiS BarberS	1.23:1	3.0:1	#000000	#1C1C1C	Fail
span Accueil	4.48:1	4.5:1	#000000	#677776	Fail
span Présentation	4.34:1	4.5:1	#000000	#647574	Fail
span Les Prix	4.34:1	4.5:1	#000000	#647574	Fail
span Contactez-nous	4.08:1	4.5:1	#000000	#5F7170	Fail
span Contactez-nous	3.97:1	4.5:1	#000000	#5D6F6F	Fail
i …	3.88:1	4.5:1	#000000	#5A6E6C	Fail
span Accueil	3.83:1	4.5:1	#000000	#596D6C	Fail
span Présentation	3.76:1	4.5:1	#000000	#576C6A	Fail
span Les Prix	3.64:1	4.5:1	#000000	#546A69	Fail
span Contactez-nous	3.64:1	4.5:1	#000000	#546A69	Fail
span Contactez-nous	3.59:1	4.5:1	#000000	#536968	Fail
a Réserver	3.70:1	4.5:1	#000000	#556B6A	Fail
strong EndiS BarberS	3.63:1	3.0:1	#000000	#536A68	Pass
span Accueil	3.55:1	4.5:1	#000000	#546866	Fail
span Présentation	3.65:1	4.5:1	#000000	#546A6A	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.

B

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 19 passed

REVIEW

88

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.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.s-component-content > div > iframe#s-map `div > div.s-component-content > div > iframe#s-map`

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.

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
" EndisBarbers est la concrétisation d'un concept du barber idéal perçu `div > div.s-component-content > div > h3.h3Tag`
Vous donnez une coupe de cheveux légendaire avec un service traditionnel. N… `div.s-component > div > div.s-component-content > h4`
Parce que les champions du monde doivent être beaux. `div > div > div > h4.s-subtitle`

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Appelez Réserver `div.css-1mq3izu > div.s-floated-components > div#s-new-mobile-actions-wrapper > ul.s-mobile-actions`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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

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

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

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

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

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

8 decorative image(s) correctly marked

5 image(s) with good alt text

13 images 5 good alt text 8 decorative

All images have appropriate alt text.

A

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

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

Got: <input type="text">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
input	text	(none)	none

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

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

A

Link & Button Quality

30 links, 2 buttons — all OK

PASS

30 links, 2 buttons — all OK

6 link(s) open in new tab without warning

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

Got: https://calendly.com/endisbarbers/rendez-vous-coiffure; https://calendly.com/endisbarbers/rendez-vous-coiffure; https://calendly.com/endisbarbers/rendez-vous-coiffure; https://www.facebook.com/profile.php?id=100071602154200; https://www.instagram.com/endisbarbers/; /pages/cookie-policy

24 link(s) with descriptive text

30 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://calendly.com/endisbarbers/rendez…	Réserver	new tab	Add '(opens in new tab)' to text
https://calendly.com/endisbarbers/rendez…	Réserver	new tab	Add '(opens in new tab)' to text
https://calendly.com/endisbarbers/rendez…	Cliquez ici pour prendre Rende…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/profile.php?id=…	image link	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/endisbarbers/	image link	new tab	Add '(opens in new tab)' to text
/pages/cookie-policy	En savoir plus	new tab	Add '(opens in new tab)' to text

26 links and buttons have descriptive text

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

https://calendly.com/endisbarbers/rendez-vous-coiffure; https://calendly.com/endisbarbers/rendez-vous-coiffure; https://calendly.com/endisbarbers/rendez-vous-coiffure; https://www.facebook.com/profile.php?id=100071602154200; https://www.instagram.com/endisbarbers/; /pages/cookie-policy

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+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Document Language

Lang attribute set to "fr"

PASS

Lang attribute set to "fr"

<html lang="fr"> is set and valid

Got: fr

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page