Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.D404 Error PageActionHTTP 410, custom pageFIX
FFavicon & BrandingAction2 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure5 landmarksREVIEW
Multiple navigations need aria-label to distinguish them for screen readers.
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.
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
BHeading Hierarchy14 headingsREVIEW
- H2 Primaire navigatie
- H2 Main navigation
- H2 Berichten over uw Buurt
- H2 Dienstverlening
- H2 Beleid & regelgeving
- H2 Contactgegevens overheden
- H2 Vind snel de juiste overheidsinformatie.
- H2 Diensten van de overheid
- H2 Berichten over uw Buurt
- H2 Beleid en regelgeving
- H2 Levensgebeurtenissen
- H2 Contactgegevens
- H2 Wat doet Overheid.nl?
- H2 Uitgelichte onderwerpen
Every page should have one H1 that describes the page content.
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
A+Alt Text QualityAll 1 images OKPASS
AForm Accessibility1 of 1 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #edit-submit | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" name="op" id="edit-submit">
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Source: WCAG 2.1 SC 3.3.2
ALink & Button Quality43 links, 2 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| / | Overheid.nl | img no alt | Add alt attribute to the image |
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
a[href="/"]
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+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Primaire navigatie | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Main navigation | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Berichten over uw Bu… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Dienstverlening | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Beleid & regelgeving | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Contactgegevens over… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Vind snel de juiste … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Wat doet Overheid.nl… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Uitgelichte onderwer… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Homepage | Overheid.… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Direct naar content | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| button Menu | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span wegwijzer naar infor… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a MijnOverheid | 17.87:1 | 4.5:1 | #000000 | #E0EFF8 | Pass |
| span Andere sites binnen | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Overheid.nl | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Andere sites binnen | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Overheid.nl | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p Zoals vergunningen, … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Rondom uw woonadres | 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.
A+Lighthouse Accessibility AuditsScore 97/100 — 1 failing, 27 passedPASS
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.
ARIA
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
form#suggester-search-form > div.js-form-item > tags.tagify > span.tagify__input form#suggester-search-form > div.js-form-item > tags.tagify > span.tagify__input |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.