Skip to content
https://Svennouwen.nl

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
85
GRADE
B
FIX
4
REVIEW
3
PASS
17
INFO
0
Checks
24
17 PASS 3 REVIEW 4 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – Sven Nouwen ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Sven builds thoughtful tools for real pr…
1.06:1
#000000
on
#050A13
needs 3.0:1 (large text)
32px · above the fold
h2 Getting Ephemora ready for early access …
1.06:1
#000000
on
#050A13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Two products, each with its own audience…
1.06:1
#000000
on
#050A13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Questions about Pinned, early access to …
1.06:1
#000000
on
#050A13
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Calm
1.06:1
#000000
on
#050A13
needs 3.0:1 (large text)
19px · mid-page
h3 Crafted
1.06:1
#000000
on
#050A13
needs 3.0:1 (large text)
19px · mid-page
h3 Trustworthy
1.06:1
#000000
on
#050A13
needs 3.0:1 (large text)
19px · mid-page
h3 Ephemora
1.06:1
#000000
on
#050A13
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Pinned
1.06:1
#000000
on
#050A13
needs 3.0:1 (large text)
19px · bottom of viewport
title Sven Nouwen – Independent product desi…
1.06:1
#000000
on
#040A12
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.06:1
#000000
on
#040A12
needs 4.5:1 (normal text)
16px · top of page (header area)
a Apps
1.06:1
#000000
on
#050A13
needs 4.5:1 (normal text)
16px · top of page (header area)
a Ephemora
1.06:1
#000000
on
#050A13
needs 4.5:1 (normal text)
16px · top of page (header area)
a Pinned
1.06:1
#000000
on
#050A13
needs 4.5:1 (normal text)
16px · above the fold
a About
1.06:1
#000000
on
#050A13
needs 4.5:1 (normal text)
16px · above the fold
a Contact
1.06:1
#000000
on
#050A13
needs 4.5:1 (normal text)
16px · above the fold
p Independent product design and iOS devel…
1.06:1
#000000
on
#050A13
needs 4.5:1 (normal text)
16px · above the fold
span See the work
1.06:1
#000000
on
#050A13
needs 4.5:1 (normal text)
16px · above the fold
span Get in touch
1.06:1
#000000
on
#050A13
needs 4.5:1 (normal text)
16px · above the fold
p The studio
1.06:1
#000000
on
#050A13
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Sven builds thoughtf…1.06:13.0:1
#000000
#050A13
Fail
h2 Getting Ephemora rea…1.06:13.0:1
#000000
#050A13
Fail
h2 Two products, each w…1.06:13.0:1
#000000
#050A13
Fail
h2 Questions about Pinn…1.06:13.0:1
#000000
#050A13
Fail
h3 Calm1.06:13.0:1
#000000
#050A13
Fail
h3 Crafted1.06:13.0:1
#000000
#050A13
Fail
h3 Trustworthy1.06:13.0:1
#000000
#050A13
Fail
h3 Ephemora1.06:13.0:1
#000000
#050A13
Fail
h3 Pinned1.06:13.0:1
#000000
#050A13
Fail
title Sven Nouwen – Inde…1.06:14.5:1
#000000
#040A12
Fail
a Skip to content1.06:14.5:1
#000000
#040A12
Fail
a Apps1.06:14.5:1
#000000
#050A13
Fail
a Ephemora1.06:14.5:1
#000000
#050A13
Fail
a Pinned1.06:14.5:1
#000000
#050A13
Fail
a About1.06:14.5:1
#000000
#050A13
Fail
a Contact1.06:14.5:1
#000000
#050A13
Fail
p Independent product …1.06:14.5:1
#000000
#050A13
Fail
span See the work1.06:14.5:1
#000000
#050A13
Fail
span Get in touch1.06:14.5:1
#000000
#050A13
Fail
p The studio1.06:14.5:1
#000000
#050A13
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.

A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main" MAIN CONTENTINFO (missing!)

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

A
Heading Hierarchy
9 headings, 1 skip(s)
PASS
9 headings, 1 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.
  • H1 Sven builds thoughtful tools for real problems
  • H3 Calm skipped
  • H3 Crafted
  • H3 Trustworthy
  • H2 Getting Ephemora ready for early access around the Orionids in October.
  • H2 Two products, each with its own audience, accent and pace.
  • H3 Ephemora
  • H3 Pinned
  • H2 Questions about Pinned, early access to Ephemora, or something else entirely — this reaches me directly.

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

A+
Heading Text Quality
All 9 heading(s) have substantive, well-formed text
PASS
All 9 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
2 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
5 images 3 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#form-field-1wgoywhemailEmail addressfor/id
#form-field-a1pf3n9textNamefor/id
#form-field-bx6ydf3emailEmailfor/id
#form-field-z6ygb9fselectSubjectfor/id
#form-field-gymilvwtextareaMessagefor/id
A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 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 "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
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 57 visible text node(s) render at >= 12 CSS pixels
PASS
All 57 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.
A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 25 passed
PASS
98

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
Calm div.elementor-element > div.elementor-element > div.elementor-element > h3.elementor-heading-title

These are opportunities to improve keyboard navigation in your application.

○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.
●Select elements have associated label elements.
●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
●Touch targets have sufficient size and spacing.
●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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback