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 4 REVIEW 5 FIX

Link & Button Quality

Action

12 issue(s) across 713 links and 178 buttons

FIX

12 issue(s) across 713 links and 178 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.ovhcloud.com/fr/;

2 link(s) open in new tab without warning

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

Got: https://www.kimsufi.com/fr/; https://www.kimsufi.com/fr/?range=rise

10 button(s) with no accessible text

709 link(s) with descriptive text

713 links

2 empty

0 generic text

2 new tab

10 empty buttons

Element	Text	Issue	Suggested Fix
https://www.ovhcloud.com/fr/	(empty)	empty	Add link text or aria-label
https://www.kimsufi.com/fr/	Kimsufi (T1/T2)	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://www.kimsufi.com/fr/?range=rise	Serveurs dédiés Promotion …	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

877 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.ovhcloud.com/fr/;

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.kimsufi.com/fr/; https://www.kimsufi.com/fr/?range=rise

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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗

Icons 2 icon(s)

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 ✗

Lighthouse Accessibility Audits

Action

Score 66/100 — 10 failing, 23 passed

FIX

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Webmail Mon compte client Contact commercial Support France [€] Retourner au m… `div.ods-header-universe > aside.ovhcloud-menu-navbar > div.ovhcloud-menu-navbar__footer > ul.ods-header-topbar__content__menu`
div.text-left > div.odss-slider > div.odss-slider__controls > div.d-flex `div.text-left > div.odss-slider > div.odss-slider__controls > div.d-flex`

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated `li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated`
li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated `li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated`
li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated `li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated`
li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated `li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated`
li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated `li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated`
li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated `li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated`
li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated `li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated`
li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated `li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated`
li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated `li.lh-1 > div.otds-text > span.flex-shrink-0 > osds-icon.hydrated`
div.button__text-container > span.button__centered-text > span.d-block > osds-icon.hydrated `div.button__text-container > span.button__centered-text > span.d-block > osds-icon.hydrated`
button.link > span.link__text-container > span > osds-icon.hydrated `button.link > span.link__text-container > span > osds-icon.hydrated`
button.link > span.link__text-container > span > osds-icon.hydrated `button.link > span.link__text-container > span > osds-icon.hydrated`
button.link > span.link__text-container > span > osds-icon.hydrated `button.link > span.link__text-container > span > osds-icon.hydrated`
button.link > span.link__text-container > span > osds-icon.hydrated `button.link > span.link__text-container > span > osds-icon.hydrated`

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
La protection de vos données est notre priorité. Notre site internet et le… `body > div#tc-privacy-wrapper > div#header_tc_privacy`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > form#domain-search-header-form--2 > div.header--webcloud__input-wrapper > button.header--webcloud__button `div > form#domain-search-header-form--2 > div.header--webcloud__input-wrapper > button.header--webcloud__button`
div.odss-slider > div.odss-slider__controls > div.d-flex > button.odss-slider__pager__button `div.odss-slider > div.odss-slider__controls > div.d-flex > button.odss-slider__pager__button`
div.odss-slider > div.odss-slider__controls > div.d-flex > button.odss-slider__pager__button `div.odss-slider > div.odss-slider__controls > div.d-flex > button.odss-slider__pager__button`
div.odss-slider > div.odss-slider__controls > div.d-flex > button.odss-slider__pager__button `div.odss-slider > div.odss-slider__controls > div.d-flex > button.odss-slider__pager__button`
div.odss-slider > div.odss-slider__controls > div.d-flex > button.odss-slider__pager__button `div.odss-slider > div.odss-slider__controls > div.d-flex > button.odss-slider__pager__button`
div.text-left > div.odss-slider > div.odss-slider__controls > button.odss-slider__button--pause `div.text-left > div.odss-slider > div.odss-slider__controls > button.odss-slider__button--pause`
form#domain-search-form > div.d-flex > div.otds-button > button.button `form#domain-search-form > div.d-flex > div.otds-button > button.button`
div > div#block-federationtools > div.federation-tools-buttons > button.federation-tools-buttons__btn `div > div#block-federationtools > div.federation-tools-buttons > button.federation-tools-buttons__btn`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#header_tc_privacy_text > div#privacy_center_wrapper > div.privacy_center_img > img `div#header_tc_privacy_text > div#privacy_center_wrapper > div.privacy_center_img > img`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ods-header-topbar > div.ods-header-topbar__content > div.py-lg-3 > a `div.ods-header-topbar > div.ods-header-topbar__content > div.py-lg-3 > a`

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.

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
Devise `form.odss-sub-selection-form > div.odss-sub-selection-form__fields > div.odss-sub-selection-form__field > p.odss-sub-selection-form__label`
Sélectionner une devise `div.odss-sub-selection-form__fields > div.odss-sub-selection-form__field > div.odss-dropdown > div.odss-dropdown__title`
Site web (langue) `form.odss-sub-selection-form > div.odss-sub-selection-form__fields > div.odss-sub-selection-form__field > p.odss-sub-selection-form__label`
Sélectionner un site web `div.odss-sub-selection-form__fields > div.odss-sub-selection-form__field > div.odss-dropdown > div.odss-dropdown__title`
Nouveau `div.card-layout > div.d-flex > span > span.ods-badge`

These are opportunities to improve the legibility of your content.

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
li.ods-footer__menu__item > div.ods-footer__menu__item__block > div > ul.ods-footer__menu `li.ods-footer__menu__item > div.ods-footer__menu__item__block > div > ul.ods-footer__menu`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
France [€] Retourner au menu Le choix du pays et/ou de la région peut modifie… `aside.ovhcloud-menu-navbar > div.ovhcloud-menu-navbar__footer > ul.ods-header-topbar__content__menu > li.language-switcher`
X logo `ul.ods-footer__menu > li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item`
linkedin logo `ul.ods-footer__menu > li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item`
facebook logo `ul.ods-footer__menu > li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item`
youtube logo `ul.ods-footer__menu > li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item`
twitch logo `ul.ods-footer__menu > li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item`
discord logo `ul.ods-footer__menu > li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item`
blog logo `ul.ods-footer__menu > li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item`
github logo `ul.ods-footer__menu > li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item`

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

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
En savoir plus `div.card-layout > div.contextual-region > div.otds-link > button.link`
En savoir plus `div.card-layout > div.contextual-region > div.otds-link > button.link`
En savoir plus `div.card-layout > div.contextual-region > div.otds-link > button.link`
En savoir plus `div.card-layout > div.contextual-region > div.otds-link > button.link`
X logo `li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item > a.ods-footer__link__icon`
linkedin logo `li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item > a.ods-footer__link__icon`
facebook logo `li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item > a.ods-footer__link__icon`
youtube logo `li.ods-footer__menu__item > nav#block-ovhcloud-social-networks > li.ods-footer__menu__item > a.ods-footer__link__icon`

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]`s are contained by their required parent element

●`[role]` values are valid

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

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

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

●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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

Form Accessibility

3 of 4 controls have issues

REVIEW

3 of 4 controls have issues

3 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" id="edit-domain-name--2">; <input type="text">; <input type="text">

1 control(s) properly labeled

4 controls

1 labeled

3 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-domain-name	text	Recherche en masse de noms de domaine	for/id
input	text	(Rechercher)	placeholder only
#edit-domain-name--2	text	(Rechercher un nom de domaine)	placeholder only
input	text	(Rechercher)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 - Page not found | OVHcloud Worldwide ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Breadcrumb navigation detected

Got: aria-label

Skip navigation link detected

104 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs aria-label navigation

Skip Link Skip link detected

Labeled Navigation 104 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

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 OVHcloud

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

32px · bottom of viewport

h1 La protection de vos données est notre …

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Backup Agent

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Travaillez mieux ensemble avec Zimbra Pr…

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 200 € de crédit offert

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Découvrir nos offres conçues pour votr…

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Partenaires et clients d'OVHcloud

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Comment OVHcloud peut vous aider

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Pourquoi choisir OVHcloud ?

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Rise-S/M/L/XL

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Nouvelle gamme VPS disponible

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Choisissez votre infrastructure

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Optez pour une solution Enterprise

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Démarrez votre projet cloud

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Gérez votre présence en ligne

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Déployez une plateforme big data et ana…

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Démarrez vos instances avec des ressour…

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Créez un site internet en 5 étapes

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Évitez les pannes d'accès à Internet …

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 About Us

1.54:1

#000000

#000D9C

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 OVHcloud	1.54:1	3.0:1	#000000	#000D9C	Fail
h1 La protection de vos…	1.54:1	3.0:1	#000000	#000D9C	Fail
h2 Backup Agent	1.54:1	3.0:1	#000000	#000D9C	Fail
h2 Travaillez mieux ens…	1.54:1	3.0:1	#000000	#000D9C	Fail
h2 200 € de crédit o…	1.54:1	3.0:1	#000000	#000D9C	Fail
h2 Découvrir nos offre…	1.54:1	3.0:1	#000000	#000D9C	Fail
h2 Partenaires et clien…	1.54:1	3.0:1	#000000	#000D9C	Fail
h2 Comment OVHcloud peu…	1.54:1	3.0:1	#000000	#000D9C	Fail
h2 Pourquoi choisir OVH…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Rise-S/M/L/XL	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Nouvelle gamme VPS d…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Choisissez votre inf…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Optez pour une solut…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Démarrez votre proj…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Gérez votre présen…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Déployez une platef…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Démarrez vos instan…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Créez un site inter…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 Évitez les pannes d…	1.54:1	3.0:1	#000000	#000D9C	Fail
h3 About Us	1.54:1	3.0:1	#000000	#000D9C	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

141 landmarks

PASS

141 landmarks

<main> landmark present

104 <nav> landmark(s) found

69 of 104 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

25 headings

PASS

25 headings

Multiple H1 headings (2 found)

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

H1 OVHcloud
H2 Backup Agent
H2 Travaillez mieux ensemble avec Zimbra Pro
H3 Rise-S/M/L/XL
H3 Nouvelle gamme VPS disponible
H2 200 € de crédit offert
H2 Découvrir nos offres conçues pour votre activité
H3 Choisissez votre infrastructure
H3 Optez pour une solution Enterprise
H3 Démarrez votre projet cloud
H3 Gérez votre présence en ligne
H2 Partenaires et clients d'OVHcloud
H2 Comment OVHcloud peut vous aider
H3 Déployez une plateforme big data et analytics en moins d'une heure !
H3 Démarrez vos instances avec des ressources garanties
H3 Créez un site internet en 5 étapes
H3 Évitez les pannes d'accès à Internet avec OverTheBox
H3 About Us
H2 Pourquoi choisir OVHcloud ?
H3 Comme nos 1,6 million de clients, rejoignez un cloud libre, durable et de confiance.
H3 Un cloud libre et fédérateur
H3 Leader mondial du cloud de confiance
H3 Un cloud durable by design
H3 Meilleur ratio performance/prix du marché
H1 La protection de vos données est notre priorité. duplicate H1

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

Alt Text Quality

1 of 27 images have issues

PASS

1 of 27 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

26 image(s) with good alt text

27 images 26 good alt text 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

Favicon & Branding

7 icon(s) detected

PASS

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

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