Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 2 REVIEW 5 FIX

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 403 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

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.

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 11 pass AA only

span Diensten en informatie

3.88:1

#000000

#756858

needs 4.5:1 (normal text)

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

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 Goedendag, waarmee k…	4.45:1	3.0:1	#000000	#378159	Pass
h2 Vertalen	4.45:1	3.0:1	#000000	#378159	Pass
h2 Uitgelicht	4.45:1	3.0:1	#000000	#378159	Pass
h2 Diensten & informati…	4.45:1	3.0:1	#000000	#378159	Pass
h2 Laatste nieuws	4.45:1	3.0:1	#000000	#378159	Pass
h2 Contact	4.45:1	3.0:1	#000000	#378159	Pass
h2 Openingstijden van v…	4.45:1	3.0:1	#000000	#378159	Pass
h3 Nieuwe speeltuin Emm…	4.45:1	3.0:1	#000000	#378159	Pass
h3 Nieuwe planten voor …	4.45:1	3.0:1	#000000	#378159	Pass
h3 Avond en nachtafslui…	4.45:1	3.0:1	#000000	#378159	Pass
title Homepage - Hillegom	18.51:1	4.5:1	#000000	#E8F3F0	Pass
a Ga direct naar inhou…	19.96:1	4.5:1	#000000	#F6FAF9	Pass
t Hoog contrast	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Vertalen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Open vertaalopties	16.66:1	4.5:1	#000000	#E0E6E9	Pass
span Logo Gemeente Hilleg…	11.02:1	4.5:1	#000000	#B0BEC5	Pass
span Toon	9.97:1	4.5:1	#000000	#ACB5AD	Pass
t submenu voor	15.32:1	4.5:1	#000000	#D3DEE2	Pass
span Diensten en informat…	3.88:1	4.5:1	#000000	#756858	Fail
t Terug naar	4.83:1	4.5:1	#000000	#7A7C52	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

4 landmarks

PASS

4 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

16 headings

PASS

16 headings

Single H1 present

H2 Bevolking Burgerzaken
H2 Huis Bouwen, wonen en mobiliteit
H2 Bomen Energie, milieu en duurzaamheid
H2 Cultuur Kunst, cultuur en sport
H2 Ondernemen Ondernemers
H2 Kind en familie Zorg en ondersteuning
H2 Vertalen
H1 Goedendag, waarmee kunnen wij u helpen?
H2 Uitgelicht
H2 Diensten & informatie
H2 Laatste nieuws
H3 Nieuwe speeltuin Emmastraat
H3 Nieuwe planten voor plantvakken
H3 Avond en nachtafsluiting N208
H2 Contact
H2 Openingstijden van vandaag

A+

Heading Text Quality

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

PASS

All 16 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

9 decorative image(s) correctly marked

6 image(s) with good alt text

15 images 6 good alt text 9 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#a11y-toolbar__translate-select	select	Selecteer taal	for/id
#s	text	Vul uw zoekterm in:	for/id

Link & Button Quality

69 links, 8 buttons — all OK

PASS

69 links, 8 buttons — all OK

7 link(s) open in new tab without warning

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

Got: tel://140252; https://www.burgerberichten.nl/HLT/formulieren/1510bc37-f4fb-4e57-9552-038d6c…; https://www.facebook.com/gemeentehillegom/?locale=nl_NL; https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8…; https://nl.linkedin.com/company/gemeente-hillegom; /rss.xml; /atom.xml

62 link(s) with descriptive text

69 links

0 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
tel://140252	14 0252	new tab	Add '(opens in new tab)' to text
tel://+31252783300	+31 252 783 300	img no alt	Add alt attribute to the image
https://hillegom.nl/contact/	Locaties en openingstijden	img no alt	Add alt attribute to the image
https://www.burgerberichten.nl/HLT/formu…	Stel uw vraag	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/gemeentehillego…	Volg ons op facebook	new tab	Add '(opens in new tab)' to text
https://www.google.com/url?sa=t&rct=j&q=…	Volg ons op instagram	new tab	Add '(opens in new tab)' to text
https://nl.linkedin.com/company/gemeente…	Volg ons op linkedin	new tab	Add '(opens in new tab)' to text
/rss.xml	Volg ons op rss	new tab	Add '(opens in new tab)' to text
/atom.xml	Volg ons op atom	new tab	Add '(opens in new tab)' to text

70 links and buttons have descriptive text

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

tel://140252; https://www.burgerberichten.nl/HLT/formulieren/1510bc37-f4fb-4e57-9552-038d6c…; https://www.facebook.com/gemeentehillegom/?locale=nl_NL; https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8…; https://nl.linkedin.com/company/gemeente-hillegom; /rss.xml; /atom.xml

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

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

2 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

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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 57 visible text node(s) render at >= 12 CSS pixels

PASS

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

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

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

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.

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
div.container > div.header__wrap > div.header__search > a.header__search-page `div.container > div.header__wrap > div.header__search > a.header__search-page`

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

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

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

●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

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

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

○Uses ARIA roles only on compatible elements

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