Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

18 PASS 1 REVIEW 5 FIX

Favicon & Branding

Action

6 icon(s) detected

FIX

6 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

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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 ✗

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 5 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Gemeente	4.09:1	3.0:1	#000000	#0171BC	Pass
h2 Afval	4.09:1	3.0:1	#000000	#0171BC	Pass
h2 Paspoort/ Identiteit…	4.09:1	3.0:1	#000000	#0171BC	Pass
h2 Rijbewijs	4.09:1	3.0:1	#000000	#0171BC	Pass
h2 Wegwerkzaamheden	4.09:1	3.0:1	#000000	#0171BC	Pass
h2 Verhuizen	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h2 Melding doen openbar…	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h2 Doe mee met de isola…	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h2 Nieuws	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h2 Trouwen in de gemeen…	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h2 Over de gemeente Sti…	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h2 Bekijk onze andere w…	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h2 Gemeente Stichtse Ve…	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h2 Volg ons	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h2 Meer informatie	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h3 Mobiel Media Lab maa…	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h3 Gemeente Stichtse Ve…	4.86:1	3.0:1	#000000	#1A7FC2	Pass
h3 Groep 8-leerlingen o…	4.86:1	3.0:1	#000000	#1A7FC2	Pass
title Gemeente \| Gemeente …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Naar hoofdinhoud	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.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

28 headings

PASS

28 headings

Single H1 present

H1 Gemeente
H2 Afval
H2 Paspoort/ Identiteitskaart
H2 Rijbewijs
H2 Wegwerkzaamheden
H2 Verhuizen
H2 Melding doen openbare ruimte
H2 Doe mee met de isolatie-actie
H2 Afval
H2 Inwonerszaken
H2 Hulp en ondersteuning
H2 Wonen en leefomgeving
H2 Duurzaamheid en klimaat
H2 Belastingen, vergunningen en subsidies
H2 Ondernemen
H2 Sport en recreatie
H2 Info over de gemeente
H2 Veiligheid
H2 Nieuws
H3 Mobiel Media Lab maakt indruk op schoolleerlingen en buurtbewoners
H3 Gemeente Stichtse Vecht vervangt meer dan 27.000 tegels door groen tijdens NK Tegelwippen
H3 Groep 8-leerlingen ontdekken de lokale democratie in de raadzaal
H2 Trouwen in de gemeente Stichtse Vecht
H2 Over de gemeente Stichtse Vecht
H2 Bekijk onze andere websites
H2 Gemeente Stichtse Vecht
H2 Volg ons
H2 Meer informatie

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

10 decorative image(s) correctly marked

2 image(s) with good alt text

12 images 2 good alt text 10 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
#page-header__search__input	search	Zoeken	for/id

A+

Link & Button Quality

101 links, 17 buttons — all OK

PASS

101 links, 17 buttons — all OK

101 link(s) with descriptive text

101 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

118 links and buttons have descriptive text

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

1 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

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

PASS

6 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+

Mobile-Readable Font Sizes

All 89 visible text node(s) render at >= 12 CSS pixels

PASS

All 89 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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 Pagina niet gevonden (404) | Gemeente Stichtse Vecht ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

A+

Lighthouse Accessibility Audits

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

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
/gemeente.stichtsevecht (Verwijst naar een externe website) `div.footer-social-media-links__container > ul.socials > li.socials__item > a.link`
gemeentestichtsevecht (Verwijst naar een externe website) `div.footer-social-media-links__container > ul.socials > li.socials__item > a.link`
gemeentestichtsevecht (Verwijst naar een externe website) `div.footer-social-media-links__container > ul.socials > li.socials__item > a.link`
@StichtseVecht (Verwijst naar een externe website) `div.footer-social-media-links__container > ul.socials > li.socials__item > a.link`

○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

●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

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

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

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