Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 1 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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

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

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

A+

Heading Hierarchy

22 headings

PASS

22 headings

Single H1 present

H2 Hoofdnavigatie
H3 Submenu kop
H1 Belastingdienst
H2 Uitgelicht
H3 Aangifte inkomstenbelasting 2025
H3 Ik heb aangifte 2025 gedaan, wanneer hoor ik iets?
H3 Ik wacht op mijn nabestaandenmachtiging
H3 Nieuw rekeningnummer Belastingdienst
H2 Belangrijke thema's
H2 Actueel
H3 Nieuws
H3 Verstoringen - onderhoud
H3 Belangrijke datums
H2 Grote plannen? Of verandert er iets?
H2 Algemene informatie
H3 Over de Belastingdienst
H3 Inloggen
H3 Over deze site
H3 Language
H4 English
H4 Deutsch
H3 Footer links

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#bldSearchInput	text	Waar bent u naar op zoek?	for/id

A+

Link & Button Quality

134 links, 5 buttons — all OK

PASS

134 links, 5 buttons — all OK

134 link(s) with descriptive text

134 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

139 links and buttons have descriptive text

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Helaas kunnen we de pagina die u zoekt niet vinden | Belastingdienst ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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)

Element	Ratio	Required	FG	BG	Result
h1 Belastingdienst	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Hoofdnavigatie	13.37:1	3.0:1	#000000	#D0CECB	Pass
h2 Uitgelicht	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Belangrijke thema's	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Actueel	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Grote plannen? Of ve…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Algemene informatie	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Submenu kop	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Aangifte inkomstenbe…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Ik heb aangifte 2025…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Ik wacht op mijn nab…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Nieuw rekeningnummer…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Nieuws	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Verstoringen - onder…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Belangrijke datums	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Over de Belastingdie…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Inloggen	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Over deze site	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Footer links	18.93:1	3.0:1	#000000	#F3F3F3	Pass
title Belastingdienst Nede…	21.00:1	4.5:1	#000000	#FFFFFF	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 96/100 — 1 failing, 27 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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ga naar hoofdinhoud `div.container > ul > li > a#skiplink-mainContentSkip`
Ga direct naar hoofdnavigatie `div.container > ul > li > a#skiplink-navContentSkip`
Ga direct naar footer `div.container > ul > li > a#skiplink-footer`
Logo Belastingdienst \| Ministerie van Financiën, link naar homepage van Belasti… `div.container > div.row > div.col-12 > a`
Home `div.container > ul#navContentSkip > li.nav-item > a.nav-link`
Menu `div.container > ul#navContentSkip > li.nav-item > a#bld-megamenu`
Open zoeken `div.container > ul#navContentSkip > li.nav-item > a#bld-zoeken`
Inloggen `div.container > ul#navContentSkip > li.nav-item > a#bld-loginmenu`

These are opportunities to improve keyboard navigation in your application.

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

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

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