Skip to content
https://nos.nl

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
3
REVIEW
5
PASS
5
INFO
0
Checks
13
5 PASS 5 REVIEW 3 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
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 ModePartial Dark Mode
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::
1 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 1 <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
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) 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 (missing!) NAV "Hoofdnavigatie" MAIN 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

B
Heading Hierarchy
44 headings
REVIEW
44 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Trump verlengt bestand met Iran, maar voor hoelang blijft vaag
  • H2 Ov-kortingskaart in beeld als maatregel tegen energiecrisis
  • H2 Meerderheid Kamer wil beheer DigiD bij Solvinity weghalen bij Amerikaanse overname
  • H2 Stroomnet Utrecht nu echt vol, helemaal geen nieuwe of zwaardere aansluitingen meer
  • H2 Opnieuw onrustig anti-azc-protest Loosdrecht, twee aanhoudingen
  • H2 Letschert onder vuur om aanpak pro-Palestinaprotest op universiteit Maastricht
  • H2 Zelensky meldt reparatie van pijpleiding waar Oekraïne en Hongarije over ruzieden
  • H2 Terreur Joodse kolonisten neemt nog verder toe: 'Ze doen wat ze willen'
  • H2 Lufthansa schrapt 20.000 vluchten vanwege brandstofprijzen
  • H2 Partijen teleurgesteld over sneuvelen asielwet: 'een blamage' en 'diep triest'
  • H2 Nederlanders in Istanbul stierven net als Duits gezin door bestrijdingsmiddel
  • H2 Opnieuw maatregelen om Groningse 'Mario Kart-bocht' veiliger te maken
  • H2 Proef met onderzoek naar verwurging levert veel meer aanvragen op dan verwacht
  • H2 'Meer hulp nodig voor mensen met ernstige psychische aandoeningen'
  • H2 Nieuwe film over Michael Jackson laat beschuldigingen kindermisbruik onbenoemd
  • H2 Sport
  • H2 Leicester City degradeert tien jaar na Premier League-titel naar derde niveau
  • H2 Duizenden fans juichen en joelen voor bekerwinnaar AZ bij huldiging
  • H2 Twijfels weg bij Schulting: 'Langebaan en shorttrack gaan echt goed samen'
  • H2 Uit jouw regio
  • H2 Bestelbus belandt op zijkant, bestuurder gewond
  • H2 Stop op elektriciteitsaansluitingen in Flevoland voorlopig van de baan
  • H2 Metershoge vlammen bij grote brand in kringloopwinkel in Sevenum: NL-Alert verstuurd
  • H2 Kijken
  • H2 Live bij de NOS
  • H2 Kijk hier naar het NOS Journaal van 20.00 uur
  • H2 Verdiepen
  • H2 Nederlandse werkenden meest productief in 20 jaar, hoe kan dat?
  • H2 Tim Cook stopt als CEO Apple: vernieuwde op andere manier dan Steve Jobs
  • H2 Nederland wil koploper blijven in duurzamer textiel, 'rest van wereld zit niet stil'
  • H2 Podcast De Dag: DigiD-gate ontleed
  • H2 Landelijk crisisplan olie van kracht, wat betekent dat?
  • H2 Podcast De Dag: de kerosine-crisis en hoe de oorlog het vliegverkeer treft
  • H2 Hoe het christendom een steeds grotere rol speelt in de Amerikaanse politiek
  • H2 Prefab bouwen tegen de woningnood: de vraag is hoe snel dat kan
  • H2 Oorlog in Midden-Oosten brengt voedselzekerheid in delen van wereld in gevaar
  • H2 In de strijd tegen Trump willen ook Democraten 'valsspelen' bij midterms
  • H2 Hoe Israël de oorlogstactiek uit Gaza gebruikt in Zuid-Libanon
  • H2 Geluiden achter de schermen: 'NAVO-crisis grootste tot nu toe'
  • H2 Uitgelegd
  • H2 Laatste nieuws
  • H2 NOS informatie
  • H2 Nieuws
  • H2 Sport

Every page should have one H1 that describes the page content.

Why this matters

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

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title NOS.nl - De pagina kan helaas niet worden gevonden ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 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 Present
✓ Multiple Sizes Present
A+
Alt Text Quality
All 69 images OK
PASS
All 69 images OK
Info::
69 decorative image(s) correctly marked
69 images 69 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: NOS.nl
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name NOS.nl ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name NOS.nl Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 3 icon(s)
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 Trump verlengt besta…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ov-kortingskaart in …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meerderheid Kamer wi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Stroomnet Utrecht nu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Opnieuw onrustig ant…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Letschert onder vuur…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Zelensky meldt repar…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Terreur Joodse kolon…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Lufthansa schrapt 20…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Partijen teleurgeste…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nederlanders in Ista…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Opnieuw maatregelen …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Proef met onderzoek …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 'Meer hulp nodig voo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nieuwe film over Mic…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sport21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Leicester City degra…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Duizenden fans juich…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Twijfels weg bij Sch…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Uit jouw regio21.00:13.0: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 Audits
Score 100/100 — 0 failing, 26 passed
PASS
100

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.

○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
●`[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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○Form elements have associated labels
○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.
○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