Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 3 REVIEW 3 FIX

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 ✗

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

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 European Cloud & AI.

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

32px · bottom of viewport

h2 What if your cloud met European expectat…

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 They trust us

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Discover our AI Product Range

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why Scaleway

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Choose the cloud built for what's next

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Start your Cloud journey with the right …

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Data Sovereignty

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Open, Independent Technology

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Transparent Pricing

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Fast-moving Innovation

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Bare Metal

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Compute

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Network

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Storage & Database

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Containers

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI and Machine Learning

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Customer data sovereignty

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Sustainable data centers

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Low latency

1.22:1

#000000

#151A2D

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 European Cloud & AI.	1.22:1	3.0:1	#000000	#151A2D	Fail
h2 What if your cloud m…	1.22:1	3.0:1	#000000	#151A2D	Fail
h2 They trust us	1.22:1	3.0:1	#000000	#151A2D	Fail
h2 Discover our AI Pro…	1.22:1	3.0:1	#000000	#151A2D	Fail
h2 Why Scaleway	1.22:1	3.0:1	#000000	#151A2D	Fail
h2 Choose the cloud bui…	1.22:1	3.0:1	#000000	#151A2D	Fail
h2 Start your Cloud jou…	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Data Sovereignty	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Open, Independent Te…	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Transparent Pricing	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Fast-moving Innovati…	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Bare Metal	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Compute	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Network	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Storage & Database	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Containers	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 AI and Machine Learn…	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Customer data sovere…	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Sustainable data cen…	1.22:1	3.0:1	#000000	#151A2D	Fail
h3 Low latency	1.22:1	3.0:1	#000000	#151A2D	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

6 landmarks

PASS

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

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

A+

Heading Hierarchy

24 headings

PASS

24 headings

Single H1 present

H1 European Cloud & AI.
H2 What if your cloud met European expectations?
H2 They trust us
H2 Discover our AI Product Range
H2 Why Scaleway
H3 Data Sovereignty
H3 Open, Independent Technology
H3 Transparent Pricing
H3 Fast-moving Innovation
H2 Access a comprehensiveportfolio of 100+cloud & AI products
H3 Bare Metal
H3 Compute
H3 Network
H3 Storage & Database
H3 Containers
H3 AI and Machine Learning
H2 Choose the cloud built for what's next
H3 Customer data sovereignty
H3 Sustainable data centers
H3 Low latency
H2 Start your Cloud journey with the right resources
H3 Documentation
H3 API
H3 Changelog and Status

A+

Alt Text Quality

All 39 images OK

PASS

All 39 images OK

17 decorative image(s) correctly marked

22 image(s) with good alt text

39 images 22 good alt text 17 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

201 links, 14 buttons — all OK

PASS

201 links, 14 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://labs.scaleway.com/en/

200 link(s) with descriptive text

201 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://labs.scaleway.com/en/	LabsEastShortIconEastShortIcon	new tab	Add '(opens in new tab)' to text

214 links and buttons have descriptive text

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

https://labs.scaleway.com/en/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Scaleway

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Scaleway ✓192×192 icon ✓512×512 icon ✓Start URL /en/ ✓Display Mode standalone ✓

Name Scaleway Display Mode standalone Theme Color #4f0599 Background Color transparent Icons 2 icon(s)

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 26 passed

PASS

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

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
Cookie time! Scaleway uses cookies (or similar technologies) that are necessar… `div.inter_724de5d0-module__j-XtIa__variable > div#portal > div._container_2gf4i_1 > aside.undefined`

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.

○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

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

●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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

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

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

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

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