Skip to content
https://aruba.it

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

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

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

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

F
Heading Hierarchy
Action
89 headings, 12 skip(s)
FIX
89 headings, 12 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 HOSTING and DOMAINS
  • H2 FIBER
  • H2 PEC & Trust Services
  • H2 CLOUD AND DEDICATED SERVERS
  • H2 ARUBA BUSINESS
  • H2 CYBERSECURITY
  • H2 PRATICHE.it
  • H4 Hosting and domains skipped
  • H4 Internet connections
  • H4 Cloud
  • H4 Server and colocation
  • H4 Other services
  • H4 Customer area
  • H4 Hosting and domains
  • H4 Internet connections
  • H4 Cloud
  • H4 Servers and colocation
  • H5 Other service
  • H4 Aruba Business
  • H4 DV SSL Certificate
  • H4 Microsoft 365
  • H4 Pratiche.it
  • H4 SMS
  • H4 My account
  • H2 WordPress Hosting the Aruba solutions
  • H2 Connect instantly with the simyousoon eSIM
  • H1 Get unlimited sSl certificates
  • H2 Choose the independent cloud, built in Italy for Europe
  • H2 WordPress Hosting the Aruba solutions
  • H2 Connect instantly with the simyousoon eSIM
  • H2 For your online projects
  • H2 Hosting and domains
  • H4 All the tools to start selling and get noticed online. skipped
  • H2 Cloud and Dedicated Servers
  • H4 To manage and grow your company's digital projects with certified cloud services and dedicated servers. skipped
  • H2 PEC and trust services
  • H4 To simplify company processes and save on costs. skipped
  • H2 Aruba RENTRI Smart
  • H4 The digital waste management service, compliant with the RENTRI regulation, dedicated to small businesses. skipped
  • H2 Fiber internet
  • H4 Activate for free! Change your mind within a month for a full refund or cancel any time for €20. Not using it? Use Stop&Go to put fiber on hold and pay nothing! skipped
  • H4 Only genuine fiber optic
  • H2 E-invoicing
  • H4 Easily create, send, and store electronic invoices while staying compliant with regulations. skipped
  • H3 Our customers
  • H2 ARUBA ENTERPRISE
  • H4 We help companies, public administrations, and hyperscale cloud providers manage complex projects. skipped
  • H4 CLOUD | DATA CENTERS | TRUST SERVICES
  • H2 ARUBA BUSINESS
  • H4 Become our partner and unlock exclusive benefits skipped
  • H3 <img alt="" src="/images/home/aruba_azienda_certificata_color.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Certificati" class="imghover" src="/images/home/aruba_azienda_certifi
  • H3 <img alt="" src="/images/home/aruba_network_europeo_color.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Network Europeo" class="imghover" src="/images/home/aruba_network_europeo
  • H3 <img alt="" src="/images/home/aruba_prima_italia_color.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Italy's N. 1" class="imghover" src="/images/home/aruba_prima_italia.aspx" st
  • H3 <img alt="Always with you" src="/images/home/aruba_assitenza_h_24_color-en.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Always with you" class="imghover" src="/images/home/arub
  • H3 <img alt="Affordable" src="/images/home/aruba_economico_color.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Affordable" class="imghover" src="/images/home/aruba_economico.aspx"
  • H3 <img alt="" src="/images/home/aruba_sicura_color.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Dati protetti" class="imghover" src="/images/home/aruba_sicura.aspx" style="vertic
  • H3 <img alt="" src="/images/home/aruba_azienda_certificata_color.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Certificati" class="imghover" src="/images/home/aruba_azienda_certifi
  • H3 <img alt="" src="/images/home/aruba_network_europeo_color.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Network Europeo" class="imghover" src="/images/home/aruba_network_europeo
  • H3 <img alt="" src="/images/home/aruba_prima_italia_color.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Italy's N. 1" class="imghover" src="/images/home/aruba_prima_italia.aspx" st
  • H3 <img alt="Always with you" src="/images/home/aruba_assitenza_h_24_color-en.aspx" style="vertical-align: bottom;margin-right:-80px;" /><img alt="Always with you" class="imghover" src="/images/home/arub
  • H2 Aruba and data protection
  • H4 (empty)
  • H4 Your data stays in Europe
  • H4 Your data stays in Europe
  • H4 Guaranteed Data Centers in Italy and Europe
  • H4 Guaranteed Data Centers in Italy and Europe
  • H4 You alone control your data
  • H4 You alone control your data
  • H4 Uncompromising Privacy & Confidentiality
  • H4 Uncompromising Privacy & Confidentiality
  • H4 ISO 27001 certification
  • H4 ISO 27001 certification
  • H4 Infrastructure security
  • H4 Infrastructure security
  • H5 Green by design
  • H4 Respect for the environment is at the core of our philosophy
  • H4 Energy production
  • H4 Guarantee of Origin (GO)
  • H2 Aruba Racing - Ducati SBK Team
  • H2 News
  • H4 European Cloud Providers and Industry Data Spaces Join Forces to Bring 10,000 SMEs into Trusted Data Network skipped
  • H4 Europe, Let’s Build This Together: SECA API Call for Comments open until 15 September as European Cloud Leaders Issue Public Challenge to Industry
  • H4 Aruba's electronic signature passes Potential Consortium tests and for European interoperability
  • H3 Guides
  • H3 Support
  • H2 Company
  • H2 Payment
  • H2 Info
  • H4 Are you trying to sign in to the customer area skipped

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

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

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

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

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

F
Form Accessibility
Action
7 of 12 controls have issues
FIX
7 of 12 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <select>
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text">
Info::
5 control(s) properly labeled
12 controls
5 labeled
2 placeholder only
5 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessary cookiesfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreference cookiesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatistics cookiesfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketing cookiesfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
inputtext(type your domain here)placeholder only
inputtext(search your domain here)placeholder only
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
selectselect(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <select>

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

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

<input type="text">; <input type="text">

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Info::
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: #f86313
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 4 <nav> element(s)
Back to Top
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.
C
Alt Text Quality
Action
12 of 155 images have issues
REVIEW
12 of 155 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
9 image(s) with generic alt text
Info::
46 decorative image(s) correctly marked
Info::
97 image(s) with good alt text
155 images 97 good alt text 46 decorative 9 generic 3 missing
IssueCount
missing3 image(s)
generic9 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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | Aruba.it ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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)
ElementRatioRequiredFGBGResult
h2 HOSTING and DOMAINS19.26:13.0:1
#000000
#F5F5F5
Pass
h2 FIBER19.26:13.0:1
#000000
#F5F5F5
Pass
h2 PEC & Trust Services19.26:13.0:1
#000000
#F5F5F5
Pass
h2 CLOUD AND DEDICATED …19.26:13.0:1
#000000
#F5F5F5
Pass
h2 ARUBA BUSINESS19.26:13.0:1
#000000
#F5F5F5
Pass
h2 CYBERSECURITY19.26:13.0:1
#000000
#F5F5F5
Pass
h2 PRATICHE.it19.26:13.0:1
#000000
#F5F5F5
Pass
h2 the Aruba solutions19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Connect instantly wi…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 the simyousoon eSIM19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Choose the independe…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 built in Italy for E…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 the Aruba solutions19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Connect instantly wi…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 the simyousoon eSIM19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Hosting and domains19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Cloud and Dedicated …19.26:13.0:1
#000000
#F5F5F5
Pass
h2 PEC and trust servic…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Aruba RENTRI Smart19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Fiber internet19.26:13.0:1
#000000
#F5F5F5
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 91/100 — 3 failing, 29 passed
PASS
91

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.

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
restrictions div.row > div.col-xs-12 > p.a-right > a
Green by design div.row > div.col-xs-12 > div.green-title > h5
HELP body.LTR > form#form > div.navbar-header > button#assist-xs-toggle
Customer Care 24/7 body.LTR > form#form > div.navbar-header > div.visible-xs

These are opportunities to improve the legibility of your content.

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
All the tools to start selling and get noticed online. div.Card > div.Card-Body > div.Card-Subtitle > h4
To manage and grow your company's digital projects with certified cloud service… div.Card > div.Card-Body > div.Card-Subtitle > h4
To simplify company processes and save on costs. div.Card > div.Card-Body > div.Card-Subtitle > h4
The digital waste management service, compliant with the RENTRI regulation, ded… div.Card > div.Card-Body > div.Card-Subtitle > h4
Activate for free! Change your mind within a month for a full refund or cancel … div.Card > div.Card-Body > div.Card-Subtitle > h4.m-bottom-24
Easily create, send, and store electronic invoices while staying compliant with… div.Card > div.Card-Body > div.Card-Subtitle > h4
We help companies, public administrations, and hyperscale cloud providers manag… div.homepage > div.EnterpriseZone > div.container > h4.m-top-20
Become our partner and unlock exclusive benefits div.homepage > div.BusinessZone > div.container > h4
  div.GDPRflipBlu > div.container > div.text-center > h4
European Cloud Providers and Industry Data Spaces Join Forces to Bring 10,000 S… div.PressHomePage > div.row > div.col-xs-12 > h4.PressTitle

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
.it .cloud .com .eu .net .org .biz .info .es .co.uk .de .us .org.uk .name .gov.… div.col-xs-12 > div.row > div.col-xs-12 > select.form-control

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.

○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
●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.
●`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
●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
●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
○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 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
○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.
○`<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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback