Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Landmark Structure

Action

1 landmarks

FIX

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

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

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

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 ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

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

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, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA 12 pass AA only

div Lorsque vous utilisez nos sites et appli…

4.43:1

#000000

#737373

needs 4.5:1 (normal text)

16px · above the fold

span Cookies

2.19:1

#000000

#454545

needs 4.5:1 (normal text)

16px · above the fold

span Les cookies (y compris les technologies …

2.09:1

#000000

#424242

needs 4.5:1 (normal text)

16px · above the fold

a politique relative aux cookies

2.03:1

#000000

#404040

needs 4.5:1 (normal text)

16px · above the fold

span pour en savoir plus.

1.96:1

#000000

#3E3E3E

needs 4.5:1 (normal text)

16px · mid-page

span cookies

1.96:1

#000000

#3E3E3E

needs 4.5:1 (normal text)

16px · mid-page

div pour :

3.60:1

#000000

#656565

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

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
h1 guce	5.24:1	3.0:1	#000000	#7F7F7F	Pass
title Vos paramètres de c…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
a guce	5.24:1	4.5:1	#000000	#7F7F7F	Pass
p Votre vie privée es…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
p Yahoo fait partie de…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span Famille de marques Y…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span Sites et application…	5.10:1	4.5:1	#000000	#7D7D7D	Pass
span famille de marques Y…	4.76:1	4.5:1	#000000	#787878	Pass
div Lorsque vous utilise…	4.43:1	4.5:1	#000000	#737373	Fail
span Cookies	2.19:1	4.5:1	#000000	#454545	Fail
span Les cookies (y compr…	2.09:1	4.5:1	#000000	#424242	Fail
a politique relative a…	2.03:1	4.5:1	#000000	#404040	Fail
span pour en savoir plus.	1.96:1	4.5:1	#000000	#3E3E3E	Fail
span cookies	1.96:1	4.5:1	#000000	#3E3E3E	Fail
div pour :	3.60:1	4.5:1	#000000	#656565	Fail
li vous fournir nos sit…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
li authentifier les uti…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span Mesure	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span Nous comptons le nom…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span mesurer	5.24:1	4.5:1	#000000	#7F7F7F	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.

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 22 passed

REVIEW

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.ltr `html.ltr`

These are opportunities to improve the interpretation of your content by users in different locales.

Contrast

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
nos partenaires `div#consent-text > div.content-section > div > a`

These are opportunities to improve the legibility of your content.

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
guce `div._yb_1hpv8qw > div._yb_123jq1u > div._yb_yqa3u4 > a#ybar-logo`
mesurer `div.content-section > ul.content-list > li.list-item > span.info`

○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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●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

●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

○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 a valid value for its `[lang]` attribute

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

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

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

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 guce

Alt Text Quality

1 of 7 images have issues

PASS

1 of 7 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

6 decorative image(s) correctly marked

7 images 6 decorative 1 missing

Issue	Count
missing	1 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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

6 links, 3 buttons — all OK

PASS

6 links, 3 buttons — all OK

4 link(s) open in new tab without warning

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

Got: /redirect?to=https%3A%2F%2Flegal.yahoo.com%2Fie%2Ffr%2Fyahoo%2Fprivacy%2Fcook…; /v2/partners-list?sessionId=3_cc-session_611ca8be-21bb-4500-bbde-26027010d097; /redirect?to=https%3A%2F%2Flegal.yahoo.com%2Fie%2Ffr%2Fyahoo%2Fprivacy%2Finde…; /redirect?to=https%3A%2F%2Flegal.yahoo.com%2Fie%2Ffr%2Fyahoo%2Fprivacy%2Fcook…

2 link(s) with descriptive text

6 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://fr.yahoo.com/	yahoo logo	img no alt	Add alt attribute to the image
/redirect?to=https%3A%2F%2Flegal.yahoo.c…	politique relative aux cookies	new tab	Add '(opens in new tab)' to text
/v2/partners-list?sessionId=3_cc-session…	nos partenaires	new tab	Add '(opens in new tab)' to text
/redirect?to=https%3A%2F%2Flegal.yahoo.c…	Politique de confidentialité	new tab	Add '(opens in new tab)' to text
/redirect?to=https%3A%2F%2Flegal.yahoo.c…	Politique concernant les cooki…	new tab	Add '(opens in new tab)' to text

5 links and buttons have descriptive text

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

/redirect?to=https%3A%2F%2Flegal.yahoo.com%2Fie%2Ffr%2Fyahoo%2Fprivacy%2Fcook…; /v2/partners-list?sessionId=3_cc-session_611ca8be-21bb-4500-bbde-26027010d097; /redirect?to=https%3A%2F%2Flegal.yahoo.com%2Fie%2Ffr%2Fyahoo%2Fprivacy%2Finde…; /redirect?to=https%3A%2F%2Flegal.yahoo.com%2Fie%2Ffr%2Fyahoo%2Fprivacy%2Fcook…

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

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