Skip to content
https://telegraaf.nl

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 3 icon(s)
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 28 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.

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
23:00 a.ListTeaser_list-teaser__link__WmbvV > div.ListTeaser_list-teaser__content__uxl1H > div.ListTeaser_list-teaser__date-time-wrapper__O1anU > time.DateTime_date-time__5Jy0G
23:00 a.ListTeaser_list-teaser__link__WmbvV > div.ListTeaser_list-teaser__content__uxl1H > div.ListTeaser_list-teaser__date-time-wrapper__O1anU > time.DateTime_date-time__5Jy0G
BUITENLAND div.DefaultTeaser_default-teaser__content-wrapper__l1M2T > div.DefaultTeaser_default-teaser__taxonomy__yOuxv > div.TeaserTaxonomy_teaser-taxonomy__X_0Ki > span.TeaserTaxonomy_teaser-taxonomy__label__RSFrP
21:01 div.DefaultTeaser_default-teaser__content-wrapper__l1M2T > div.DefaultTeaser_default-teaser__taxonomy__yOuxv > div.TeaserTaxonomy_teaser-taxonomy__X_0Ki > time.DateTime_date-time__5Jy0G
MEDIA div.DefaultTeaser_default-teaser__content-wrapper__l1M2T > div.DefaultTeaser_default-teaser__taxonomy__yOuxv > div.TeaserTaxonomy_teaser-taxonomy__X_0Ki > span.TeaserTaxonomy_teaser-taxonomy__label__RSFrP
22:00 div.DefaultTeaser_default-teaser__content-wrapper__l1M2T > div.DefaultTeaser_default-teaser__taxonomy__yOuxv > div.TeaserTaxonomy_teaser-taxonomy__X_0Ki > time.DateTime_date-time__5Jy0G

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
PSG boekt belangrijke zege in strijd om Franse landstitel, Bayern München berei… a.ListTeaser_list-teaser__link__WmbvV > div.ListTeaser_list-teaser__content__uxl1H > div > h5.ListTeaser_list-teaser__heading__Dt6Ne
Hoort de Italiaanse Songfestival-zanger niet gewoon in een casino thuis? div.DefaultTeaser_default-teaser__content__CEXA7 > div.TeaserContent_teaser-content__G_aGK > div.TeaserContent_teaser-content__title-wrapper__TvlXs > h5.Heading_heading__E4_Ob
PSG boekt belangrijke zege in strijd om Franse landstitel, Bayern München berei… a.ListTeaser_list-teaser__link__WmbvV > div.ListTeaser_list-teaser__content__uxl1H > div > h5.ListTeaser_list-teaser__heading__Dt6Ne

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._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img
div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img
div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img
div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img
div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img
div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img
div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img
div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img
div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img
div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 > img

Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more about alt text for `object` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20
a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20 a._root_y7mvt_1 > div._content_1uixn_10 > div._root_93pne_1 > object._logo_93pne_20

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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●Links are distinguishable without relying on color.
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○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 Hierarchy
4 headings
PASS
4 headings
Info::
Single H1 present
  • H1 Sorry, you have been blocked
  • H2 You are unable to access telegraaf.nl
  • H2 Why have I been blocked?
  • H2 What can I do to resolve this?
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
18 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.

18 pass
Show all checked elements (18)
ElementRatioRequiredFGBGResult
h1 Sorry, you have been…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 telegraaf.nl21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why have I been bloc…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 What can I do to res…17.62:13.0:1
#000000
#EBEBEB
Pass
title Attention Required! …21.00:14.5:1
#000000
#FFFFFF
Pass
div Please enable cookie…21.00:14.5:1
#000000
#FFFFFF
Pass
span You are unable to ac…21.00:14.5:1
#000000
#FFFFFF
Pass
p This website is usin…17.62:14.5:1
#000000
#EBEBEB
Pass
p You can email the si…17.62:14.5:1
#000000
#EBEBEB
Pass
span Cloudflare Ray ID:17.62:14.5:1
#000000
#EBEBEB
Pass
strong 9f07a62c5c24aa9f17.62:13.0:1
#000000
#EBEBEB
Pass
span •18.76:14.5:1
#000000
#F2F2F2
Pass
span Your IP:21.00:14.5:1
#000000
#FFFFFF
Pass
button Click to reveal21.00:14.5:1
#000000
#FFFFFF
Pass
span 5.45.185.2421.00:14.5:1
#000000
#FFFFFF
Pass
span •21.00:14.5:1
#000000
#FFFFFF
Pass
span Performance & securi…21.00:14.5:1
#000000
#FFFFFF
Pass
a Cloudflare21.00:14.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.

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

Send Feedback