Skip to content
https://skynet.be

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-f7ib3r
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://skynet.be/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://skynet.be/manifest.json

Manifest contains invalid JSON.

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: #0a0a0a
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
9 headings
REVIEW
9 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Bepaal je cookievoorkeuren
  • H3 Cookievoorkeuren beheren
  • H4 Noodzakelijke en analytische cookies en soortgelijke technologieën
  • H4 Gepersonaliseerde Proximus-aanbiedingen en gepersonaliseerde surfervaring
  • H4 Cookies en soortgelijke technologieën die door derden worden geplaatst
  • H4 Cookies en soortgelijke technologieën die door Proximus en door derden worden gebruikt om doelgerichte advertenties weer te geven
  • H3 Performance Cookies
  • H3 (empty)
  • H4 (empty)

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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
C
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
h2 Bepaal je cookievoorkeuren
1.38:1
#000000
on
#292239
needs 3.0:1 (large text)
24px · above the fold
h3 Cookievoorkeuren beheren
1.38:1
#000000
on
#292239
needs 3.0:1 (large text)
19px · above the fold
h3 Performance Cookies
1.83:1
#000000
on
#3D364C
needs 3.0:1 (large text)
19px · bottom of viewport
title TV, sport, films en series live uitgezon…
1.33:1
#000000
on
#261F36
needs 4.5:1 (normal text)
16px · top of page (header area)
a Français
1.35:1
#000000
on
#272037
needs 4.5:1 (normal text)
16px · top of page (header area)
a Nederlands
1.36:1
#000000
on
#282138
needs 4.5:1 (normal text)
16px · top of page (header area)
span All rights reserved, Proximus 2026.
1.36:1
#000000
on
#282138
needs 4.5:1 (normal text)
16px · top of page (header area)
div Vink de cookies aan waarmee je instemt.
1.35:1
#000000
on
#272038
needs 4.5:1 (normal text)
16px · above the fold
button Alle toestaan
1.36:1
#000000
on
#282138
needs 4.5:1 (normal text)
16px · above the fold
h4 Noodzakelijke en analytische cookies en …
1.40:1
#000000
on
#2A233A
needs 3.0:1 (large text)
16px · above the fold
div Altijd actief
1.42:1
#000000
on
#2B243B
needs 4.5:1 (normal text)
16px · above the fold
p Ze zijn essentieel voor het functioneren…
1.44:1
#000000
on
#2C253C
needs 4.5:1 (normal text)
16px · above the fold
button Leveranciersdetails weergeven‎
1.46:1
#000000
on
#2D263D
needs 4.5:1 (normal text)
16px · above the fold
h4 Gepersonaliseerde Proximus-aanbiedingen …
1.48:1
#000000
on
#2E273E
needs 3.0:1 (large text)
16px · above the fold
span Gepersonaliseerde Proximus-aanbiedingen …
1.50:1
#000000
on
#2F283F
needs 4.5:1 (normal text)
16px · mid-page
p Andere cookies zorgen voor een meer gepe…
1.54:1
#000000
on
#312A40
needs 4.5:1 (normal text)
16px · mid-page
button Leveranciersdetails weergeven‎
1.56:1
#000000
on
#322B41
needs 4.5:1 (normal text)
16px · mid-page
h4 Cookies en soortgelijke technologieën d…
1.58:1
#000000
on
#332C42
needs 3.0:1 (large text)
16px · mid-page
span Cookies en soortgelijke technologieën d…
1.60:1
#000000
on
#342D43
needs 4.5:1 (normal text)
16px · mid-page
p Sommige cookies die door externe partner…
1.63:1
#000000
on
#352E45
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Bepaal je cookievoor…1.38:13.0:1
#000000
#292239
Fail
h3 Cookievoorkeuren beh…1.38:13.0:1
#000000
#292239
Fail
h3 Performance Cookies1.83:13.0:1
#000000
#3D364C
Fail
title TV, sport, films en …1.33:14.5:1
#000000
#261F36
Fail
a Français1.35:14.5:1
#000000
#272037
Fail
a Nederlands1.36:14.5:1
#000000
#282138
Fail
span All rights reserved,…1.36:14.5:1
#000000
#282138
Fail
div Vink de cookies aan …1.35:14.5:1
#000000
#272038
Fail
button Alle toestaan1.36:14.5:1
#000000
#282138
Fail
h4 Noodzakelijke en ana…1.40:13.0:1
#000000
#2A233A
Fail
div Altijd actief1.42:14.5:1
#000000
#2B243B
Fail
p Ze zijn essentieel v…1.44:14.5:1
#000000
#2C253C
Fail
button Leveranciersdetails …1.46:14.5:1
#000000
#2D263D
Fail
h4 Gepersonaliseerde Pr…1.48:13.0:1
#000000
#2E273E
Fail
span Gepersonaliseerde Pr…1.50:14.5:1
#000000
#2F283F
Fail
p Andere cookies zorge…1.54:14.5:1
#000000
#312A40
Fail
button Leveranciersdetails …1.56:14.5:1
#000000
#322B41
Fail
h4 Cookies en soortgeli…1.58:13.0:1
#000000
#332C42
Fail
span Cookies en soortgeli…1.60:14.5:1
#000000
#342D43
Fail
p Sommige cookies die …1.63:14.5:1
#000000
#352E45
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+
Alt Text Quality
All 4 images OK
PASS
All 4 images OK
Info::
4 image(s) with good alt text
4 images 4 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 8 controls have issues
PASS
1 of 8 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="vendor-search-handler" id="vendor-search-handler">
Info::
7 control(s) properly labeled
8 controls
7 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#ot-group-id-1checkboxGepersonaliseerde Proximus-aanbiedingen en gepersonaliseerde surfervaringfor/id
#ot-group-id-2checkboxCookies en soortgelijke technologieën die door derden worden geplaatstfor/id
#ot-group-id-3checkboxCookies en soortgelijke technologieën die door Proximus en door derden worden gebruikt om doelgerichte advertenties weer te gevenfor/id
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxSwitch Labelfor/id
#select-all-vendor-groups-handlercheckboxSwitch Labelfor/id
#select-all-vendor-leg-handlercheckboxSwitch Labelfor/id
#vendor-search-handlertext(none)none

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

<input type="text" name="vendor-search-handler" id="vendor-search-handler">

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

A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 26 passed
PASS
100

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.

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
Cookiebeleid div#onetrust-group-container > div#onetrust-policy > p#onetrust-policy-text > a
○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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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.
○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.
○Identical links have the same purpose.
○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