Accessibility

D

Heading Hierarchy

Action

75 headings, 2 skip(s)

FIX

75 headings, 2 skip(s)

Single H1 present

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: H3 → H5 (missing H4)

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

5 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Create a website
H3 Create a website
H3 Create a showcase website
H3 Open an e-commerce shop
H3 Create a blog
H2 Domain names
H3 Domain names
H2 Email
H3 Custom email addresses
H2 TLS/SSL Certificates
H3 TLS/SSL Certificates
H2 Web hosting
H3 Web hosting
H3 Hosting for WordPress
H3 Hosting for Prestashop
H3 Hosting for Nextcloud
H2 Cloud Hosting
H3 GandiCloud VPS
H3 GandiCloud block storage
H2 Advanced business services
H3 Advanced small/medium business services
H2 Business solutions
H3 Large account services
H3 Gandi reseller program
H3 Small- and medium-sized business solutions
H3 Advanced small/medium business services
H1 A domain name for a secure online space
H2 Gather all your web projects under a single interface
H3 50% off your first website
H3 Personalized emails
H3 Your SSL certificates
H3 Your VPS servers
H2 Easily launch your project with Gandi
H2 Benefit from robust and reliable services for your web project and those of your customers.
H3 Public API
H3 Infra-as-Code to pilot your servers
H3 WordPress, Prestashop, and other open-source solutions
H3 Anycast DNS, DNSSEC, anti-DDoS solutions
H3 Protected emails
H3 Extended validation, multi-domain SAN, wildcard
H2 Key accounts: protect your online identity with a personalized service
H3 Protect and accompany
H3 Monitor and defend
H3 Secure
H2 Your guarantees with Gandi
H4 Choice skipped
H4 Ease of use
H4 Confidentiality
H3 (empty)
H2 Need help? Here are all the ways that you can contact us.
H3 (empty)
H2 Expert support, in constant contact with the developers
H3 (empty)
H2 Promises kept for over 20 years
H3 (empty)
H2 Transparency and Integrity
H3 (empty)
H2 We defend a web that is open to everyone
H2 Frequently Asked Questions
H3 How do I purchase a domain name?
H3 Who does a domain name belong to?
H3 How do I recover or re-purchase a domain name?
H3 What is a web host?
H3 Which web host should I choose?
H2 News and Sales
H2 Subscribe to our newsletter
H3 Confirmation email sent
H3 Choose your region
H3 Choose your language
H5 Products skipped
H5 Services
H5 Help & Documentation
H5 Shop
H5 Legal
H5 About Us

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

D

Link & Button Quality

Action

10 issue(s) across 148 links and 10 buttons

FIX

10 issue(s) across 148 links and 10 buttons

7 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://helpdesk.gandi.net/hc/en-us/requests/new?ticket_form_id=1361859712220… ("here"); https://www.facebook.com/GandiBar (""); https://twitter.com/gandibar (""); https://www.linkedin.com/company/gandi/ (""); https://github.com/Gandi (""); https://www.youtube.com/user/gandinet (""); https://www.instagram.com/gandi_net/ ("")

4 link(s) open in new tab without warning

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

Got: https://helpdesk.gandi.net/hc/en-us; /en-US/contracts/privacy-policy; https://helpdesk.gandi.net/hc/en-us; https://helpdesk.gandi.net/hc/en-us

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.footer__language-picker-close (#733 on page); button.footer__language-picker-close (#789 on page); button.chat-info__opened-close (#929 on page)

137 link(s) with descriptive text

148 links

0 empty

7 generic text

4 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://helpdesk.gandi.net/hc/en-us/requ…	here	generic text	Replace with descriptive text
Before: here Suggested: New?Ticket Form Id=13618597122204&Tf 13618597122204=Feedback
https://helpdesk.gandi.net/hc/en-us	Get help	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/GandiBar	link	generic text	Replace with descriptive text
Before: link Suggested: Gandibar
https://twitter.com/gandibar	link	generic text	Replace with descriptive text
Before: link Suggested: Gandibar
https://www.linkedin.com/company/gandi/	link	generic text	Replace with descriptive text
Before: link Suggested: Gandi
https://github.com/Gandi	link	generic text	Replace with descriptive text
Before: link Suggested: Gandi
https://www.youtube.com/user/gandinet	link	generic text	Replace with descriptive text
Before: link Suggested: Gandinet
https://www.instagram.com/gandi_net/	link	generic text	Replace with descriptive text
Before: link Suggested: Gandi Net
/en-US/contracts/privacy-policy	our privacy and cookie use pol…	new tab	Add '(opens in new tab)' to text
https://helpdesk.gandi.net/hc/en-us	use our support form	new tab	Add '(opens in new tab)' to text
https://helpdesk.gandi.net/hc/en-us	Use form instead	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

144 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://helpdesk.gandi.net/hc/en-us/requests/new?ticket_form_id=1361859712220… ("here"); https://www.facebook.com/GandiBar (""); https://twitter.com/gandibar (""); https://www.linkedin.com/company/gandi/ (""); https://github.com/Gandi (""); https://www.youtube.com/user/gandinet (""); https://www.instagram.com/gandi_net/ ("")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://helpdesk.gandi.net/hc/en-us; /en-US/contracts/privacy-policy; https://helpdesk.gandi.net/hc/en-us; https://helpdesk.gandi.net/hc/en-us

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.footer__language-picker-close (#733 on page); button.footer__language-picker-close (#789 on page); button.chat-info__opened-close (#929 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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.

Got: black-translucent

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 5 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

B

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 Page Not Found - Gandi.net ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

B

Favicon & Branding

5 icon(s) detected

REVIEW

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

✓ Multiple Sizes Present

A

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

5 <nav> landmark(s) found

3 of 5 <nav> elements are unlabeled

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

No banner (header) landmark

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

A+

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

8 decorative image(s) correctly marked

8 images 8 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
search	text	Try a word or a domain name	aria-label
email	email	Email Address	aria-label

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 A domain name for a …	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Create a website	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Domain names	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Email	20.86:1	3.0:1	#000000	#FFFEFE	Pass
h2 TLS/SSL Certificates	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Web hosting	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Cloud Hosting	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Advanced business se…	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Business solutions	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Gather all your web …	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Easily launch your p…	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Benefit from robust …	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 : protect your onlin…	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Your guarantees with…	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Need help? Here are …	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Expert support, in c…	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Promises kept for ov…	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Transparency and Int…	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 We defend a web that…	19.32:1	3.0:1	#000000	#FFF3EF	Pass
h2 Frequently Asked Que…	19.32:1	3.0:1	#000000	#FFF3EF	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.

A

Lighthouse Accessibility Audits

Score 94/100 — 3 failing, 30 passed

PASS

94

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
How do I purchase a domain name? Who does a domain name belong to? How do I rec… `section.section > section#faq > div.accordion__inner > div.accordion__sections-container`

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.

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
Choice `div.grid > ul.arguments__items > li.argument > h4.argument__title`
Simplified email management: discover the new space dedicated to mailboxes and … `div.grid > div.news-feed__container > a.news-feed__post > h4.news-feed__post-title`
Products `nav.footer__nav > div.footercolumn > div#footercolumn-nav-header-1 > h5.footercolumn__title`

These are opportunities to improve keyboard navigation in your application.

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
Subscribe `form.registration__form > div.registration__form-default > div.search-bar > button.search-bar__button`

○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

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

●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 are distinguishable without relying on color.

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

●`[lang]` attributes have a valid value

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

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

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

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○Uses ARIA roles only on compatible elements

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

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