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 6 REVIEW 3 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 ✗

Landmark Structure

13 landmarks

REVIEW

13 landmarks

<main> landmark present

4 <nav> landmark(s) found

2 of 4 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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.

Search landmark 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

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

Link & Button Quality

55 links, 1 buttons — all OK

REVIEW

55 links, 1 buttons — all OK

3 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/documenten/formulieren/2014/02/06/formulier-toestemming-reizen-met-minderjar…"]; a[href="/onderwerpen/veiligheidsregios-en-crisisbeheersing/vraag-en-antwoord/wat-zit-…"]; a[href="/onderwerpen/woning-huren/vraag-en-antwoord/welke-kosten-zijn-voor-de-huurder…"]

52 link(s) with descriptive text

55 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/documenten/formulieren/2014/02/06/formu…	Reizen met kinderen …	img no alt	Add alt attribute to the image
/onderwerpen/veiligheidsregios-en-crisis…	Stel uw noodpakket samen …	img no alt	Add alt attribute to the image
/onderwerpen/woning-huren/vraag-en-antwo…	Kosten onderhoud huurwoning …	img no alt	Add alt attribute to the image

53 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/documenten/formulieren/2014/02/06/formulier-toestemming-reizen-met-minderjar…"]; a[href="/onderwerpen/veiligheidsregios-en-crisisbeheersing/vraag-en-antwoord/wat-zit-…"]; a[href="/onderwerpen/woning-huren/vraag-en-antwoord/welke-kosten-zijn-voor-de-huurder…"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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 Pagina niet gevonden | Rijksoverheid.nl ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Breadcrumb navigation detected

Got: aria-label

Search functionality detected

Got: role-search

4 navigation landmark(s) detected

Breadcrumbs aria-label navigation

Search role='search' landmark

Skip Link

Labeled Navigation 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

h2 Veel bekeken

2.73:1

#000000

#535353

needs 3.0:1 (large text)

24px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Informatie van de Ri…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Veel bekeken	2.73:1	3.0:1	#000000	#535353	Fail
h2 Hoofdmenu	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Direct naar	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Nieuws	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Service	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h2 Over deze site	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Belastingen, uitkeri…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Bouwen en wonen	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Economie	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Familie, zorg en gez…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Internationale samen…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Klimaat, milieu en n…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Migratie en reizen	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Onderwijs	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Overheid en democrat…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Recht, veiligheid en…	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Verkeer en vervoer	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Werk	18.93:1	3.0:1	#000000	#F3F3F3	Pass
h3 Reizen met kinderen	18.93:1	3.0:1	#000000	#F3F3F3	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+

Heading Hierarchy

28 headings

PASS

28 headings

Single H1 present

H2 Veel bekeken
H2 Hoofdmenu
H3 Belastingen, uitkeringen en toeslagen
H3 Bouwen en wonen
H3 Economie
H3 Familie, zorg en gezondheid
H3 Internationale samenwerking
H3 Klimaat, milieu en natuur
H3 Migratie en reizen
H3 Onderwijs
H3 Overheid en democratie
H3 Recht, veiligheid en defensie
H3 Verkeer en vervoer
H3 Werk
H1 Informatie van de Rijksoverheid
H2 Direct naar
H3 Reizen met kinderen
H3 Stel uw noodpakket samen
H3 Kosten onderhoud huurwoning
H2 Nieuws
H3 Aansluitstop stroomnet Flevopolder-Gelderland-Utrecht grotendeels voorkomen door stevige maatregelen
H3 Minister-president Jetten naar informele Europese Raad in Cyprus
H3 Vogelgriep neemt af, landelijke ophok- en afschermplicht grotendeels ingetrokken
H3 Koninklijk Paar opent Nederlands Paviljoen Biënnale Venetië
H3 Regeling voor kwijtschelden WIA-voorschotten in consultatie
H3 Kabinet zet stap met toezicht op Europese AI-regels
H2 Service
H2 Over deze site

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 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
#search-keyword	text	Zoeken binnen Rijksoverheid.nl	for/id

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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Vragen? Bel Informatie Rijksoverheid: 1400 `div.wrapper > aside > div.brick > a`
Meld u aan voor de Nieuwsbrief Regeringsnieuws `div.wrapper > aside > div.brick > a`

These are opportunities to improve the semantics of the controls in your application. This 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

●Form elements have associated labels

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

●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

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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○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

○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

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

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

○Identical links have the same purpose.

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