Skip to content
https://www.coloriet.nl

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
8
REVIEW
6
PASS
10
INFO
0
Checks
24
10 PASS 6 REVIEW 8 FIX
F
Form Accessibility
Action
5 of 13 controls have issues
FIX
5 of 13 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">; <input type="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="query" id="search">; <input type="email" name="email" id="email">
Info::
8 control(s) properly labeled
13 controls
8 labeled
2 placeholder only
3 unlabeled
ControlTypeLabelMethod
#NaamtextVoornaamfor/id
#E-mailadresemailE-mailadresfor/id
#TelefoonnummertelTelefoonnummerfor/id
#Type-zorgselectOver welke zorg wilt u meer weten?for/id
#OmschrijvingtextareaOmschrijf hieronder waarover u advies wil hebben of waar u hulp bij nodig hebt:for/id
#id-1eBA7VHN44emailE-mailadres *for/id
#id-I0GCwuEU61textVoornaamfor/id
#id-umIBhBM0EQtextAchternaamfor/id
#searchsearch(Waar bent u naar op zoek?)placeholder only
#emailemail(Your e-mail here)placeholder only
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit">; <input type="submit">; <input type="submit">

Why this matters

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

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="query" id="search">; <input type="email" name="email" id="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Mobile Keyboard & Autofill
Action
5/6 eligible field(s) missing autocomplete or inputmode
FIX
5/6 eligible field(s) missing autocomplete or inputmode
Warning::
5 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email, tel.
Got: <input type="search" name="query" id="search">, <input type="email" name="E-mailadres" id="E-mailadres">, <input type="tel" name="Telefoonnummer" id="Telefoonnummer">, <input type="email" name="1eBA7VHN44" id="id-1eBA7VHN44">, <input type="email" name="email" id="email">
D
Tap Target Adequacy
Action
11 tap target(s) too small or too close together
FIX
11 tap target(s) too small or too close together
Warning::
11 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) landmark
Warning::
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
BANNER header NAV "w-dropdown-toggle-0" MAIN CONTENTINFO (missing!)

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

C
Heading Hierarchy
Action
71 headings, 3 skip(s)
REVIEW
71 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Coloriet: wij zorgen mét mensen in de ouderenzorg
  • H3 Samen met u, uw naasten, vrijwilligers en professionals skipped
  • H3 Dagbesteding
  • H4 H4 title
  • H3 Thuiszorg
  • H4 H4 title
  • H3 Hospice
  • H4 H4 title
  • H3 Revalidatie
  • H4 H4 title
  • H3 Tijdelijk verblijf
  • H4 H4 title
  • H3 Wonen
  • H4 H4 title
  • H3 Dagbesteding
  • H4 H4 title
  • H3 Thuiszorg
  • H4 H4 title
  • H3 Hospice
  • H4 H4 title
  • H3 Revalidatie
  • H4 H4 title
  • H3 Tijdelijk verblijf
  • H4 H4 title
  • H3 Wonen
  • H4 H4 title
  • H2 Dit is Janny: "Het is heel gezellig"
  • H2 Dit is Anke: "Van betekenis zijn"
  • H2 Dit is Mylène: "De tijd vliegt voorbij"
  • H2 Dit is Toos: "Vrijwilligerswerk houdt je gezond"
  • H2 Dit is Ruud: "Daar doe ik het voor"
  • H2 Over Coloriet in de ouderenzorg
  • H5 Dit mag u van ons verwachten skipped
  • H5 Wat kan Coloriet betekenen voor u als mantelzorger?
  • H5 Voor wie werkt Coloriet?
  • H5 Ouderen met een zorgvraag
  • H5 Familieleden en mantelzorgers
  • H5 Zorgverwijzers
  • H2 Het laatste nieuws bij Coloriet
  • H3 H3 title
  • H4 Denk mee over een nieuwe naam voor Hospice ‘t Hofje
  • H3 H3 title
  • H4 Samenwerking Coloriet, Triade Vitree en Firda levert eerste gediplomeerden op!
  • H3 H3 title
  • H4 Samen sterk in privacy en gegevensbescherming op de Noord-Veluwe
  • H3 H3 title
  • H4 Coloriet en Sensara starten samenwerking: leefpatroonmonitoring in de wijkzorg
  • H3 H3 title
  • H4 Lichtpuntjes in november: kinderen zingen voor ouderen met dementie bij Coloriet
  • H3 H3 title
  • H4 Aeres Hogeschool ontwerpt nieuwe beleeftuin bij Coloriet de Regenboog
  • H2 Werken bij Coloriet
  • H2 Veelgestelde vragen over ouderenzorg bij Coloriet
  • H5 In welke plaatsen is Coloriet actief? skipped
  • H5 Is er een wachtlijst voor wonen bij Coloriet?
  • H5 Vergoedt de zorgverzekeraar of gemeente de zorg?
  • H5 Wat is het verschil tussen thuiszorg en dagbesteding?
  • H5 Hoe ondersteunt Coloriet mensen met dementie?
  • H3 Vraag hier de juiste zorg aan
  • H3 Liever even bellen? We denken graag met u mee
  • H3 Samen kijken wat past
  • H4 Zorgaanbod
  • H4 Doelgroepen
  • H4 Over ons
  • H4 Overig
  • H5 Zorgaanbod
  • H5 Doelgroepen
  • H5 Over ons
  • H5 Overig
  • H4 Contact
  • H4 Blijf op de hoogte

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
PWA Depth
3 PWA signal(s) surfaced
REVIEW
3 PWA signal(s) surfaced
Warning::
Manifest is missing `display` -- defaults to browser, no PWA UX
When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).
Info::
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).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 23 passed
REVIEW
84

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ervaringsverhaal Dit is Janny: "Het is heel gezellig" Iedere donderdagmiddag … div.testimonial-wrapper > div.swiper-group > div.swiper > div#swiper-wrapper-486665d29f61e834
Denk mee over een nieuwe naam voor Hospice ‘t Hofje Samenwerking Coloriet, Tria… div.news-wrapper > div.swiper-group > div.swiper > div#swiper-wrapper-c91fd2a57157ceaa

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.

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
Aanpassen div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn
Alles afwijzen div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn
Accepteer alles div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn
0320 290 508 div.cta-card-content-wrapper > div.cta-card-button-wrapper > a.cta-button > p.cta-button-text

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Samen met u, uw naasten, vrijwilligers en professionals div.hero-content > div.slot > div.rich-text-block > h3
Dit mag u van ons verwachten div.accordion-item > div.accordion-question-wrapper > div.accordion-question > h5
Denk mee over een nieuwe naam voor Hospice ‘t Hofje div.swiper-slide > a.base-card > div.card-content-wrapper > h4.heading-3
In welke plaatsen is Coloriet actief? div.accordion-item > div.accordion-question-wrapper > div.accordion-question > h5
Zorgaanbod div.accordion-item > div.accordion-question-wrapper > div.accordion-question > h5

These are opportunities to improve keyboard navigation in your application.

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.navbar_container > div.navbar_top > div.navbar_cta-wrapper > a.icon-button div.navbar_container > div.navbar_top > div.navbar_cta-wrapper > a.icon-button
div.navbar_container > div.search-bar_wrapper > div.search-bar_inner > a.search-bar_close div.navbar_container > div.search-bar_wrapper > div.search-bar_inner > a.search-bar_close
div.footer-top-wrapper > div.w-layout-blockcontainer > div.footer-top > a#w-node-_957cc253-2447-e99c-c107-de16566c0d9d-566c0d0a div.footer-top-wrapper > div.w-layout-blockcontainer > div.footer-top > a#w-node-_957cc253-2447-e99c-c107-de16566c0d9d-566c0d0a
div.footer-bottom > div.footer-social-links-wrapper > div.footer-social-links > a.footer-social-link-wrapper div.footer-bottom > div.footer-social-links-wrapper > div.footer-social-links > a.footer-social-link-wrapper
div.footer-bottom > div.footer-social-links-wrapper > div.footer-social-links > a.footer-social-link-wrapper div.footer-bottom > div.footer-social-links-wrapper > div.footer-social-links > a.footer-social-link-wrapper
div.footer-bottom > div.footer-social-links-wrapper > div.footer-social-links > a.footer-social-link-wrapper div.footer-bottom > div.footer-social-links-wrapper > div.footer-social-links > a.footer-social-link-wrapper

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div.swiper-navigation-wrapper > div.swiper-navigation > div.swiper-pagination > span.swiper-pagination-bullet

These items highlight common accessibility best practices.

○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]`s are contained by their required parent element
●`[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
●Input buttons have discernible text.
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 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 type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○`[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
○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.
A+
Heading Text Quality
All 71 heading(s) have substantive, well-formed text
PASS
All 71 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 68 images OK
PASS
All 68 images OK
Info::
68 decorative image(s) correctly marked
68 images 68 decorative
All images have appropriate alt text.
A+
Form Input Types
13 form control(s) checked, no type mismatches
PASS
13 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
13 form control(s) checked, no input-semantic issues
PASS
13 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "nl-NL"
PASS
Lang attribute set to "nl-NL"
Info::
<html lang="nl-NL"> is set and valid
Got: nl-NL
A
Tabindex Anti-Patterns
0 positive, 2 -1-on-focusable
PASS
0 positive, 2 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 114 visible text node(s) render at >= 12 CSS pixels
PASS
All 114 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Dit is Janny: "Het i…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Dit is Anke: "Van be…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Dit is Mylène: "De …19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Dit is Toos: "Vrijwi…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Dit is Ruud: "Daar d…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Over Coloriet in de …19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Het laatste nieuws b…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Werken bij Coloriet19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Veelgestelde vragen …19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Samen met u, uw naas…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Dagbesteding19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Thuiszorg19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Hospice19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Revalidatie19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Tijdelijk verblijf19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Wonen19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Dagbesteding19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Thuiszorg19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Hospice19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Revalidatie19.09:13.0:1
#000000
#F4F4F4
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback