Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

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.

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: #187dc1

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.

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

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 2 pass AA only

span TransIP

1.19:1

#000000

#021C23

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

div VPS

1.02:1

#000000

#02020D

needs 4.5:1 (normal text)

16px · top of page (header area)

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 High Performance Ser…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 to Power your Infras…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 internet for every i…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Flexible, simple, sc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Deploy, scale, autom…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Redundant cloud infr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Scalable storage	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 OpenClaw on VPS: a p…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Exit: limitations.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Enter: growth.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Own your idea	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Supported by our inf…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Notice	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 %%domain%%	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 %%priceDataFormatted…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Video	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title TransIP \| Cloud, Vir…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span Skip to content	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span TransIP	1.19:1	4.5:1	#000000	#021C23	Fail
div VPS	1.02:1	4.5:1	#000000	#02020D	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.

A+

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

14 headings, 1 skip(s)

PASS

14 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 High Performance Servers to Power your Infrastructure
H3 %%domain%%%%tld%% skipped
H3 %%priceDataFormatted.firstPeriodCosts%%*/ /yr
H2 internet for every idea.
H2 Flexible, simple, scalable
H2 Deploy, scale, automate
H2 Redundant cloud infra
H2 Scalable storage
H2 OpenClaw on VPS: a powerful AI assistant
H3 Video
H2 Exit: limitations.Enter: growth.
H2 Own your idea
H2 Supported by our infrastructure
H2 Notice

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

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

4 decorative image(s) correctly marked

1 image(s) with good alt text

5 images 1 good alt text 4 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	search	Domain name	aria-label
search-bulk	textarea	Enter multiple domain names at once	aria-label

Link & Button Quality

121 links, 18 buttons — all OK

PASS

121 links, 18 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://www.facebook.com/transipnl; https://twitter.com/transip; https://youtube.com/channel/UC-pq8pz6AMEwpt1ivOVvnPQ; https://www.iubenda.com/privacy-policy/49412707/cookie-policy?an=no&s_ck=fals…

117 link(s) with descriptive text

121 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/transipnl	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/transip	Twitter	new tab	Add '(opens in new tab)' to text
https://youtube.com/channel/UC-pq8pz6AME…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/4…	cookie policy	new tab	Add '(opens in new tab)' to text

135 links and buttons have descriptive text

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

https://www.facebook.com/transipnl; https://twitter.com/transip; https://youtube.com/channel/UC-pq8pz6AMEwpt1ivOVvnPQ; https://www.iubenda.com/privacy-policy/49412707/cookie-policy?an=no&s_ck=fals…

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+

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.

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
Accept `div.iubenda-cs-rationale > div.iubenda-cs-opt-group > div.iubenda-cs-opt-group-consent > button.iubenda-cs-accept-btn`

These are opportunities to improve the legibility of your content.

○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

●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 have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

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