Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 3 REVIEW 3 FIX

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

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

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

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <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.

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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title - Rijksmuseum ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

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 Cookiegebruik

1.23:1

#000000

#171C24

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Bezoekersinformatie

1.04:1

#000000

#0A0603

needs 3.0:1 (large text)

24px · bottom of viewport

title Rijksmuseum, hét museum van Nederland

1.16:1

#000000

#12161C

needs 4.5:1 (normal text)

16px · top of page (header area)

p Het Rijksmuseum maakt gebruik van cookie…

1.29:1

#000000

#1B2128

needs 4.5:1 (normal text)

16px · top of page (header area)

a cookiebeleid

1.33:1

#000000

#1E232D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Accepteren

1.31:1

#000000

#232124

needs 4.5:1 (normal text)

16px · above the fold

span Nee, liever niet

1.11:1

#000000

#111011

needs 4.5:1 (normal text)

16px · above the fold

a Direct naar de inhoud

1.16:1

#000000

#171615

needs 4.5:1 (normal text)

16px · above the fold

span Language

1.19:1

#000000

#191918

needs 4.5:1 (normal text)

16px · above the fold

span Inloggen

1.18:1

#000000

#171816

needs 4.5:1 (normal text)

16px · above the fold

span Giftshop

1.12:1

#000000

#131212

needs 4.5:1 (normal text)

16px · above the fold

span Rijksmuseum

1.23:1

#000000

#201B15

needs 4.5:1 (normal text)

16px · above the fold

span Bezoek het Rijksmuseum

1.32:1

#000000

#28211C

needs 4.5:1 (normal text)

16px · above the fold

p Het museum neemt je mee naar Rembrandt, …

1.15:1

#000000

#18140E

needs 4.5:1 (normal text)

16px · above the fold

p HOOFDPARTNERS

2.43:1

#000000

#594936

needs 4.5:1 (normal text)

16px · mid-page

span Bezoek en tickets

1.27:1

#000000

#241E12

needs 4.5:1 (normal text)

16px · mid-page

span Collectie

2.31:1

#000000

#4E483B

needs 4.5:1 (normal text)

16px · mid-page

span Stories

1.44:1

#000000

#352618

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

span Language

1.36:1

#000000

#2A2419

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

span Nederlands (Dutch)

1.13:1

#000000

#161211

needs 4.5:1 (normal text)

16px · mid-page

2 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
h2 Cookiegebruik	1.23:1	3.0:1	#000000	#171C24	Fail
h2 Bezoekersinformatie	1.04:1	3.0:1	#000000	#0A0603	Fail
title Rijksmuseum, hét mu…	1.16:1	4.5:1	#000000	#12161C	Fail
p Het Rijksmuseum maak…	1.29:1	4.5:1	#000000	#1B2128	Fail
a cookiebeleid	1.33:1	4.5:1	#000000	#1E232D	Fail
span Accepteren	1.31:1	4.5:1	#000000	#232124	Fail
span Nee, liever niet	1.11:1	4.5:1	#000000	#111011	Fail
a Direct naar de inhou…	1.16:1	4.5:1	#000000	#171615	Fail
span Language	1.19:1	4.5:1	#000000	#191918	Fail
span Inloggen	1.18:1	4.5:1	#000000	#171816	Fail
span Giftshop	1.12:1	4.5:1	#000000	#131212	Fail
span Rijksmuseum	1.23:1	4.5:1	#000000	#201B15	Fail
span Bezoek het Rijksmuse…	1.32:1	4.5:1	#000000	#28211C	Fail
p Het museum neemt je …	1.15:1	4.5:1	#000000	#18140E	Fail
p HOOFDPARTNERS	2.43:1	4.5:1	#000000	#594936	Fail
span Bezoek en tickets	1.27:1	4.5:1	#000000	#241E12	Fail
span Collectie	2.31:1	4.5:1	#000000	#4E483B	Fail
span Stories	1.44:1	4.5:1	#000000	#352618	Fail
span Language	1.36:1	4.5:1	#000000	#2A2419	Fail
span Nederlands (Dutch)	1.13:1	4.5:1	#000000	#161211	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+

Heading Hierarchy

8 headings

PASS

8 headings

Single H1 present

H2 Cookiegebruik
H2 Bezoek het Rijksmuseum
H1 Highlights en tickets
H2 Meivakantie
H2 Metamorfosen
H2 Metamorfosen in de Rijksmuseum shop
H2 Collectie
H2 Bezoekersinformatie

A+

Alt Text Quality

All 30 images OK

PASS

All 30 images OK

12 decorative image(s) correctly marked

18 image(s) with good alt text

30 images 18 good alt text 12 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

59 links, 5 buttons — all OK

PASS

59 links, 5 buttons — all OK

2 link(s) open in new tab without warning

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

Got: /nl/footer/cookiebeleid; /nl/steun/doneer/anbi-informatie

57 link(s) with descriptive text

59 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/nl/footer/cookiebeleid	cookiebeleid	new tab	Add '(opens in new tab)' to text
/nl/bezoek	Bezoek het Rijksmuseum …	img no alt	Add alt attribute to the image
/nl/bezoek	Rijksmuseum High…	img no alt	Add alt attribute to the image
/nl/zien-en-doen/families-kinderen/meiva…	Meivakantie …	img no alt	Add alt attribute to the image
/nl/zien-en-doen/tentoonstellingen/metam…	Metamorfosen …	img no alt	Add alt attribute to the image
https://www.rijksmuseumshop.nl/nl/actuee…	Metamorfosen in de Rijksmuseum…	img no alt	Add alt attribute to the image
/nl/collectie	Collectie …	img no alt	Add alt attribute to the image
/nl/steun/doneer/anbi-informatie	anbi logo	new tab	Add '(opens in new tab)' to text

62 links and buttons have descriptive text

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

/nl/footer/cookiebeleid; /nl/steun/doneer/anbi-informatie

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

Favicon & Branding

27 icon(s) detected

PASS

27 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Rijksmuseum

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Rijksmuseum ✓192×192 icon ✓512×512 icon ✓Start URL https://www.rijksmuseum.nl ✓Display Mode standalone ✓

Name Rijksmuseum Display Mode standalone Theme Color #000000 Background Color #000000 Icons 2 icon(s)

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 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.

○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

●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

●Uses ARIA roles only on compatible elements

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

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

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