Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-bezip1

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://xs4all.nl/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://xs4all.nl/manifest.json

Manifest contains invalid JSON.

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: #ffc300

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

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

Heading Hierarchy

11 headings, 2 skip(s)

REVIEW

11 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

H1 XS4ALL en KPN
H2 Al meer dan 25 jaar de beste service
H2 Klant van XS4ALL?
H5 Waarmee kunnen wij u helpen? skipped
H6 XS4ALL en KPN
H2 Nieuwe abonnementen verkrijgbaar via KPN
H3 Werken bij XS4ALL
H3 Vragen mag altijd
H4 Klantenservice
H6 Vragen? skipped
H6 Storing en onderhoud

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Favicon & Branding

17 icon(s) detected

REVIEW

17 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 16 fail WCAG AA

REVIEW

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

4 pass 16 fail WCAG AA

h1 XS4ALL en KPN

1.00:1

#000000

needs 3.0:1 (large text)

32px · mid-page

h2 Al meer dan 25 jaar de beste service

1.00:1

#000000

needs 3.0:1 (large text)

24px · mid-page

title XS4ALL - First Class Internet

1.19:1

#000000

#191919

needs 4.5:1 (normal text)

16px · top of page (header area)

a Pakketten

1.19:1

#000000

#191919

needs 4.5:1 (normal text)

16px · top of page (header area)

a Overzicht

1.21:1

#000000

#1A1A1A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Internet

1.21:1

#000000

#1A1A1A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Internet & Televisie

1.21:1

#000000

#1A1A1A

needs 4.5:1 (normal text)

16px · above the fold

a Internet & Bellen

1.21:1

#000000

#1A1A1A

needs 4.5:1 (normal text)

16px · above the fold

a Alles-in-1

1.19:1

#000000

#191919

needs 4.5:1 (normal text)

16px · above the fold

a Ondernemers

1.13:1

#000000

#131313

needs 4.5:1 (normal text)

16px · above the fold

a Shop

1.10:1

#000000

#101010

needs 4.5:1 (normal text)

16px · above the fold

a Service

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

a Webmail

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

a Mijn KPN

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · above the fold

span MENU

1.02:1

#000000

#030303

needs 4.5:1 (normal text)

16px · above the fold

a Bestel nu

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 XS4ALL en KPN	1.00:1	3.0:1	#000000	#000000	Fail
h2 Al meer dan 25 jaar …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Klant van XS4ALL?	13.06:1	3.0:1	#000000	#FFC300	Pass
h2 Nieuwe abonnementen …	13.06:1	3.0:1	#000000	#FFC300	Pass
h3 Werken bij XS4ALL	13.06:1	3.0:1	#000000	#FFC300	Pass
h3 Vragen mag altijd	13.06:1	3.0:1	#000000	#FFC300	Pass
title XS4ALL - First Class…	1.19:1	4.5:1	#000000	#191919	Fail
a Pakketten	1.19:1	4.5:1	#000000	#191919	Fail
a Overzicht	1.21:1	4.5:1	#000000	#1A1A1A	Fail
a Internet	1.21:1	4.5:1	#000000	#1A1A1A	Fail
a Internet & Televisie	1.21:1	4.5:1	#000000	#1A1A1A	Fail
a Internet & Bellen	1.21:1	4.5:1	#000000	#1A1A1A	Fail
a Alles-in-1	1.19:1	4.5:1	#000000	#191919	Fail
a Ondernemers	1.13:1	4.5:1	#000000	#131313	Fail
a Shop	1.10:1	4.5:1	#000000	#101010	Fail
a Service	1.08:1	4.5:1	#000000	#0D0D0D	Fail
a Webmail	1.06:1	4.5:1	#000000	#0A0A0A	Fail
a Mijn KPN	1.04:1	4.5:1	#000000	#060606	Fail
span MENU	1.02:1	4.5:1	#000000	#030303	Fail
a Bestel nu	1.00:1	4.5:1	#000000	#000000	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.

Alt Text Quality

2 of 5 images have issues

PASS

2 of 5 images have issues

2 image(s) with filename as alt text

3 image(s) with good alt text

5 images 3 good alt text 2 generic

Issue	Count
filename	2 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

32 links, 1 buttons — all OK

PASS

32 links, 1 buttons — all OK

7 link(s) open in new tab without warning

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

Got: https://www.randstad.nl/werknemers/vacatures/topwerkgevers/xs4all; https://www.youngcapital.nl/vacatures?utf8=%E2%9C%93&search%5Bzipcode_eq%5D=&…; https://www.kpn.com/beleef/xs4all.htm; https://www.facebook.com/xs4all; https://twitter.com/xs4all; https://www.youtube.com/user/xs4all; https://www.kpn.com/beleef/xs4all.htm

25 link(s) with descriptive text

32 links

0 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.randstad.nl/werknemers/vacat…	Randstad Uitzendbureau	new tab	Add '(opens in new tab)' to text
https://www.youngcapital.nl/vacatures?ut…	YoungCapital	new tab	Add '(opens in new tab)' to text
https://www.kpn.com/beleef/xs4all.htm	Ga naar het XS4ALL Blog	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/xs4all	Ons webcareteam …	new tab	Add '(opens in new tab)' to text
https://twitter.com/xs4all	Ook via Twitter …	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/xs4all	Tips bekijken op …	new tab	Add '(opens in new tab)' to text
https://www.kpn.com/beleef/xs4all.htm	Meer info …	new tab	Add '(opens in new tab)' to text

26 links and buttons have descriptive text

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

https://www.randstad.nl/werknemers/vacatures/topwerkgevers/xs4all; https://www.youngcapital.nl/vacatures?utf8=%E2%9C%93&search%5Bzipcode_eq%5D=&…; https://www.kpn.com/beleef/xs4all.htm; https://www.facebook.com/xs4all; https://twitter.com/xs4all; https://www.youtube.com/user/xs4all; https://www.kpn.com/beleef/xs4all.htm

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

Lighthouse Accessibility Audits

Score 92/100 — 4 failing, 17 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
Bestel bij KPN `div.row > div.col-12 > span.button-wrapper > a.button`

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
Waarmee kunnen wij u helpen? `div.row > div.col-12 > div.text > h5`
Vragen? `div.main-footer__combined > div.main-footer__questions > div.main-footer__question > h6`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

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
MENU `body > header#xs4all-main-header > div.main-header__wrapper > button.main-header__navigation-toggle`

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

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

●Touch targets have sufficient size and spacing.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

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

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