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

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
F
Alt Text Quality
Action
8 of 9 images have issues
FIX
8 of 9 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 decorative image(s) correctly marked
9 images 1 decorative 8 missing
IssueCount
missing8 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
404 Error Page
Action
HTTP 404, custom page
FIX
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 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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::
2 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 2 <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.
C
Heading Hierarchy
Action
16 headings, 2 skip(s)
REVIEW
16 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 ICT moet voor je werken!
  • H4 Praktische ICT oplossingen voor kleine bedrijven in de Liemers.Wij helpen u verder. Van Microsoft 365 en cloudwerkplekken tot systeembeheer, telefonie en beveiliging. Ik zorg dat je ICT goed geregeld skipped
  • H1 Heb jij een klein bedrijf en wil je zorgeloos kunnen werken? Ontdek hieronder hoe Truecloud je daarbij ondersteunt. duplicate H1
  • H4 Moderne Werkplek"Ik wil dat mijn medewerkers overal veilig kunnen werken" skipped
  • H4 Microsoft 365"Ik wil overal bij mijn bestanden, mail en agenda kunnen"
  • H4 Zakelijk telefonie"Ik wil professioneel en overal bereikbaar zijn"
  • H4 Internet en Netwerk"Ik wil internet dat veilig, snel en stabiel is, zodat ik zorgeloos kan werken"
  • H4 Beveiliging"Ik wil zeker weten dat mijn bedrijfs gegevens goed beschermd zijn"
  • H4 Systeembeheer"Ik wil dat mijn ict goed geregeld is, zonder dat ik mij hoef druk te maken"
  • H2 Meer weten?
  • H2 ICT moet voor je werken
  • H2 Zorgeloos werken met goed geregelde ICT
  • H2 Even sparren?
  • H3 Contact
  • H3 Diensten
  • H3 Bereikbaar

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="menuToggleTrigger">; <input type="checkbox" id="page-toggler">
Info::
1 control(s) properly labeled
3 controls
1 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#privacy-settings-functionalcheckboxnone
#page-togglercheckbox(none)none
#menuToggleTriggercheckbox(none)none

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

<input type="checkbox" id="menuToggleTrigger">; <input type="checkbox" id="page-toggler">

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

C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h2 Zorgeloos werken met goed geregelde ICT
1.16:1
#000000
on
#09152F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Even sparren?
1.16:1
#000000
on
#09152F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Contact
1.16:1
#000000
on
#09152F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Diensten
1.16:1
#000000
on
#09152F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bereikbaar
1.16:1
#000000
on
#09152F
needs 3.0:1 (large text)
19px · bottom of viewport
a Ga naar navigatie
1.23:1
#000000
on
#171D18
needs 4.5:1 (normal text)
16px · top of page (header area)
span Home
1.22:1
#000000
on
#131D19
needs 4.5:1 (normal text)
16px · above the fold
span Diensten
1.22:1
#000000
on
#0E1B31
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Over ons
1.23:1
#000000
on
#081845
needs 4.5:1 (normal text)
16px · above the fold
span Contact
1.25:1
#000000
on
#081A47
needs 4.5:1 (normal text)
16px · above the fold
span Diensten
1.17:1
#000000
on
#081538
needs 4.5:1 (normal text)
16px · above the fold
span Moderne werkplek
1.08:1
#000000
on
#080B20
needs 4.5:1 (normal text)
16px · above the fold
span Microsoft 365
1.25:1
#000000
on
#08194B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Zakelijk telefonie
1.19:1
#000000
on
#08173A
needs 4.5:1 (normal text)
16px · above the fold
span Internet en Netwerk
1.15:1
#000000
on
#101329
needs 4.5:1 (normal text)
16px · above the fold
span IT beveiliging
1.17:1
#000000
on
#12152C
needs 4.5:1 (normal text)
16px · mid-page
span Systeembeheer
1.07:1
#000000
on
#100A13
needs 4.5:1 (normal text)
16px · mid-page

2 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)
ElementRatioRequiredFGBGResult
h2 Zorgeloos werken met…1.16:13.0:1
#000000
#09152F
Fail
h2 Even sparren?1.16:13.0:1
#000000
#09152F
Fail
h3 Contact1.16:13.0:1
#000000
#09152F
Fail
h3 Diensten1.16:13.0:1
#000000
#09152F
Fail
h3 Bereikbaar1.16:13.0:1
#000000
#09152F
Fail
title True Cloud - Profes…20.12:14.5:1
#000000
#FAFAFA
Pass
a Ga naar hoofdinhoud20.12:14.5:1
#000000
#FAFAFA
Pass
a Ga naar voettekst20.12:14.5:1
#000000
#FAFAFA
Pass
a Ga naar navigatie1.23:14.5:1
#000000
#171D18
Fail
span Home1.22:14.5:1
#000000
#131D19
Fail
span Diensten1.22:14.5:1
#000000
#0E1B31
Fail
span Over ons1.23:14.5:1
#000000
#081845
Fail
span Contact1.25:14.5:1
#000000
#081A47
Fail
span Diensten1.17:14.5:1
#000000
#081538
Fail
span Moderne werkplek1.08:14.5:1
#000000
#080B20
Fail
span Microsoft 3651.25:14.5:1
#000000
#08194B
Fail
span Zakelijk telefonie1.19:14.5:1
#000000
#08173A
Fail
span Internet en Netwerk1.15:14.5:1
#000000
#101329
Fail
span IT beveiliging1.17:14.5:1
#000000
#12152C
Fail
span Systeembeheer1.07:14.5:1
#000000
#100A13
Fail

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.

B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 19 passed
REVIEW
88

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.

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
Praktische ICT oplossingen voor kleine bedrijven in de Liemers. Wij helpen u ve… div.module-container-custom > div.heading-module-0269252a-21c9-4221-b432-e320509bba7a > div > h4
Moderne Werkplek "Ik wil dat mijn medewerkers overal veilig kunnen werken"   div.module-container-custom > div.heading-module-7a376c34-954d-4ab2-9fcb-cda40309d828 > div > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.image-container > div.image-wrapper > a.image-link > img.image-img div.image-container > div.image-wrapper > a.image-link > img.image-img
div.image-container > div.image-wrapper > a.image-link > img.image-img div.image-container > div.image-wrapper > a.image-link > img.image-img
div.image-container > div.image-wrapper > a.image-link > img.image-img div.image-container > div.image-wrapper > a.image-link > img.image-img
div.image-container > div.image-wrapper > a.image-link > img.image-img div.image-container > div.image-wrapper > a.image-link > img.image-img
div.image-container > div.image-wrapper > a.image-link > img.image-img div.image-container > div.image-wrapper > a.image-link > img.image-img
div.image-container > div.image-wrapper > a.image-link > img.image-img div.image-container > div.image-wrapper > a.image-link > img.image-img
div.module-container-custom > div.image-container > div.image-wrapper > img.image-img div.module-container-custom > div.image-container > div.image-wrapper > img.image-img
div.module-container-custom > div.image-container > div.image-wrapper > img.image-img div.module-container-custom > div.image-container > div.image-wrapper > img.image-img

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.module-container-custom > div.image-container > div.image-wrapper > a.image-link div.module-container-custom > div.image-container > div.image-wrapper > a.image-link
div.module-container-custom > div.image-container > div.image-wrapper > a.image-link div.module-container-custom > div.image-container > div.image-wrapper > a.image-link
div.module-container-custom > div.image-container > div.image-wrapper > a.image-link div.module-container-custom > div.image-container > div.image-wrapper > a.image-link
div.module-container-custom > div.image-container > div.image-wrapper > a.image-link div.module-container-custom > div.image-container > div.image-wrapper > a.image-link
div.module-container-custom > div.image-container > div.image-wrapper > a.image-link div.module-container-custom > div.image-container > div.image-wrapper > a.image-link
div.module-container-custom > div.image-container > div.image-wrapper > a.image-link div.module-container-custom > div.image-container > div.image-wrapper > a.image-link

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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.
●Skip links are focusable.
●Document has a main landmark.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○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
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Headernavigatie" MAIN ASIDE CONTENTINFO footer

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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H4: 199 chars
Got: 1 >120-char heading(s)
A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<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
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 45 visible text node(s) render at >= 12 CSS pixels
PASS
All 45 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback