Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 4 REVIEW 4 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

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.

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (3 below threshold)

3 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <button> 11.4px ("Contrast verhogen"); <button> 11.4px ("Tekst vergroten"); <button> 0.0px ("Zoeken").

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 Toegankelijkheid ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: Gemeente Harlingen

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name Gemeente Harlingen ✓192×192 icon ✗512×512 icon ✗Start URL / ✓Display Mode standalone ✓

Name Gemeente Harlingen Display Mode standalone Theme Color #0076A8 Background Color #000000

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

title Home | Gemeente Harlingen

3.26:1

#000000

#575F6C

needs 4.5:1 (normal text)

16px · top of page (header area)

p De inhoud is geladen.

3.26:1

#000000

#575F6C

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Home	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cookie-instellingen …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Gemeente Harlingen m…	20.82:1	3.0:1	#000000	#FEFEFE	Pass
h2 Of bent u op zoek na…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Nieuws	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Contactgegevens	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Over deze website	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Volg ons op:	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Toegankelijkheidsins…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Inwonersparticipatie	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Voorbeeld:	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Home \| Gemeente Harl…	3.26:1	4.5:1	#000000	#575F6C	Fail
p De inhoud is geladen…	3.26:1	4.5:1	#000000	#575F6C	Fail
span Sluit cookie-instell…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
legend Functionele cookies	10.02:1	4.5:1	#000000	#94B9C7	Pass
label SIManalytics Tag Man…	10.98:1	4.5:1	#000000	#AAC0BC	Pass
label (niet aanpasbaar)	10.31:1	4.5:1	#000000	#B5B7A9	Pass
p Gemeente Harlingen g…	9.02:1	4.5:1	#000000	#B9A794	Pass
label Tolkie Leeshulp	8.03:1	4.5:1	#000000	#B89B7F	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.

Landmark Structure

7 landmarks

PASS

7 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

13 headings

PASS

13 headings

Single H1 present

H2 Cookie-instellingen beheren
H2 Gemeente Harlingen maakt gebruik van cookies
H1 Home
H2 Of bent u op zoek naar...
H2 Nieuws
H3 Inwonersparticipatie
H2 Contactgegevens
H2 Over deze website
H2 Volg ons op:
H2 Menu
H2 Toegankelijkheidsinstellingen beheren
H3 Voorbeeld:
H4 Titelweergave

A+

Heading Text Quality

All 13 heading(s) have substantive, well-formed text

PASS

All 13 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

11 decorative image(s) correctly marked

11 images 11 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 10 controls labeled

PASS

All 10 controls labeled

10 control(s) properly labeled

10 controls

10 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#matomo	checkbox	SIManalytics Tag Manager (niet aanpasbaar)	for/id
#tolkie	checkbox	Tolkie Leeshulp (niet aanpasbaar)	for/id
#sim_analytics	checkbox	SIManalytics (niet aanpasbaar)	for/id
#external_media	checkbox	Externe media	for/id
#maps	checkbox	Kaarten	for/id
#spotler_engage	checkbox	Spotler Engage	for/id
#search-bar-_R_pirp6d6_	search	Zoeken	aria-label
#high_contrast	checkbox	Contrast verhogen	for/id
#large_font	checkbox	Tekst vergroten	for/id
#dyslexic_font	checkbox	Dyslexie-lettertype	for/id

Link & Button Quality

91 links, 25 buttons — all OK

PASS

91 links, 25 buttons — all OK

1 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="/"]

90 link(s) with descriptive text

91 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	Ga naar de homepage	img no alt	Add alt attribute to the image

115 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="/"]

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

A+

Form Input Types

10 form control(s) checked, no type mismatches

PASS

10 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

10 form control(s) checked, no input-semantic issues

PASS

10 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "nl"

PASS

Lang attribute set to "nl"

<html lang="nl"> is set and valid

Got: nl

A+

Tabindex Anti-Patterns

8 explicit tabindex attribute(s) checked, no anti-patterns

PASS

8 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 28 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
11-11-2026 `li.item > div.KKM5IG_itemContent > p.KKM5IG_publishedDate > time`
10-11-2026 `li.item > div.KKM5IG_itemContent > p.KKM5IG_publishedDate > time`
10-11-2026 `li.item > div.KKM5IG_itemContent > p.KKM5IG_publishedDate > time`

These are opportunities to improve the legibility of your content.

○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

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

●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

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

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

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

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