Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 5 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

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: #0293b0

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

4 landmarks

REVIEW

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

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

No banner (header) landmark

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

Mobile-Readable Font Sizes

98% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (1 below threshold)

1 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: <span> 11.0px ("Vertalen").

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA 1 pass AA only

h2 Cookies & Privacy

2.05:1

#212121

#00519E

needs 3.0:1 (large text)

24px · top of page (header area)

title Home | Gemeente Pijnacker-Nootdorp

2.67:1

#000000

#00519E

needs 4.5:1 (normal text)

16px · top of page (header area)

p Wij gebruiken cookies om de gebruikerser…

2.67:1

#000000

#00519E

needs 4.5:1 (normal text)

16px · top of page (header area)

a privacyverklaring

1.94:1

#1863DC

#B59661

needs 4.5:1 (normal text)

16px · top of page (header area)

button Instellingen

2.79:1

#1863DC

#D9B477

needs 4.5:1 (normal text)

16px · above the fold

button Alles afwijzen

2.10:1

#1863DC

#C99854

needs 4.5:1 (normal text)

16px · above the fold

button Alles accepteren

3.62:1

#FFFFFF

#AC7E3E

needs 4.5:1 (normal text)

16px · above the fold

p Wij maken gebruik van cookies. Lees meer…

1.09:1

#000000

#120E0A

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a privacybeleid.

3.78:1

#1863DC

#050302

needs 4.5:1 (normal text)

16px · above the fold

1 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
h1 Gemeente Pijnacker-N…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cookies & Privacy	2.05:1	3.0:1	#212121	#00519E	Fail
h2 Cookies & Privacy	4.27:1	3.0:1	#212121	#A47D37	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 Uitgelicht	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Overige websites	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Contact	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Snel naar	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Over deze website	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Home \| Gemeente Pijn…	2.67:1	4.5:1	#000000	#00519E	Fail
p Wij gebruiken cookie…	2.67:1	4.5:1	#000000	#00519E	Fail
a privacyverklaring	1.94:1	4.5:1	#1863DC	#B59661	Fail
button Instellingen	2.79:1	4.5:1	#1863DC	#D9B477	Fail
button Alles afwijzen	2.10:1	4.5:1	#1863DC	#C99854	Fail
button Alles accepteren	3.62:1	4.5:1	#FFFFFF	#AC7E3E	Fail
p Wij maken gebruik va…	1.09:1	4.5:1	#000000	#120E0A	Fail
a privacybeleid.	3.78:1	4.5:1	#1863DC	#050302	Fail
p We respecteren uw pr…	8.72:1	4.5:1	#000000	#A9A79F	Pass
button Noodzakelijk	15.06:1	4.5:1	#212121	#EFF9FD	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

24 headings

PASS

24 headings

Single H1 present

H2 Cookies & Privacy
H2 Cookies & Privacy
H3 Noodzakelijk
H3 Functioneel
H3 Analytics
H3 Prestatie
H3 Marketing
H1 Gemeente Pijnacker-Nootdorp
H2 Of bent u op zoek naar
H2 Nieuws
H3 Pijnacker-Nootdorp maakt afspraken over opvang en huisvesting in de regio
H3 Kom Demi Vollering toejuichen langs de ereroute op vrijdag 20 november!
H3 Imany is onze nieuwe kinderburgemeester!
H2 Uitgelicht
H3 ‘Pijnacker-Nootdorp denkt mee!’
H3 Vacatures
H3 Ontdek Pijnacker-Nootdorp
H2 Overige websites
H3 In Cijfers
H3 Raadsinformatie
H3 Altijd als eerste op de hoogte over het nieuws in uw gemeente!
H2 Contact
H2 Snel naar
H2 Over deze website

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

13 decorative image(s) correctly marked

2 image(s) with good alt text

15 images 2 good alt text 13 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#ckySwitchfunctional	checkbox	Functioneel uitgeschakeld, zet functioneel aan	aria-label
#ckySwitchanalytics	checkbox	Analytics uitgeschakeld, zet analytics aan	aria-label
#searchfieldautosuggest-downshift-input	search	Waar bent u naar op zoek?	aria-label
#zoeken-downshift-input	search	Waar bent u naar op zoek?	aria-label

Link & Button Quality

69 links, 27 buttons — all OK

PASS

69 links, 27 buttons — all OK

5 link(s) open in new tab without warning

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

Got: /privacyverklaring; /privacyverklaring; https://www.twitter.com/pijnackernootdp; https://www.facebook.com/gemeentepijnackernootdorp; https://www.linkedin.com/company/gemeente-pijnacker-nootdorp/

64 link(s) with descriptive text

69 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/privacyverklaring	privacyverklaring	new tab	Add '(opens in new tab)' to text
/privacyverklaring	privacybeleid.	new tab	Add '(opens in new tab)' to text
https://www.twitter.com/pijnackernootdp	Pijnacker-Nootdorp op Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/gemeentepijnack…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/gemeent…	LinkedIn Pijnacker-Nootdorp,	new tab	Add '(opens in new tab)' to text

91 links and buttons have descriptive text

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

/privacyverklaring; /privacyverklaring; https://www.twitter.com/pijnackernootdp; https://www.facebook.com/gemeentepijnackernootdorp; https://www.linkedin.com/company/gemeente-pijnacker-nootdorp/

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

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

4 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-NL"

PASS

Lang attribute set to "nl-NL"

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

Got: nl-NL

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

tabindex="-1" on naturally-focusable <button id="tolkie-separate-summary">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

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

No PWA depth issues detected

PASS

No PWA depth issues detected

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 100/100 — 0 failing, 29 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

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

●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

●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

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

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

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