Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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.

Got: #0c8066

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

7 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 7 <nav> element(s)

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.

Landmark Structure

23 landmarks

REVIEW

23 landmarks

<main> landmark present

7 <nav> landmark(s) found

1 of 7 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Link & Button Quality

1 issue(s) across 116 links and 29 buttons

REVIEW

1 issue(s) across 116 links and 29 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

10 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://business.safety.google/privacy/; https://www.linkedin.com/legal/privacy-policy; https://www.hotjar.com/legal/policies/privacy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://www.linkedin.com/legal/privacy-policy; https://www.facebook.com/about/privacy/; https://issuu.com/legal/privacy

105 link(s) with descriptive text

116 links

1 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://business.safety.google/privacy/	Privacy: Google (opent in nieu…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/legal/privacy-p…	Privacy: LinkedIn (opent in ni…	new tab	Add '(opens in new tab)' to text
https://www.hotjar.com/legal/policies/pr…	Privacy: Hotjar (opent in nieu…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Privacy: Google Analytics (ope…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Privacy: Google Analytics (ope…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Privacy: Google (opent in nieu…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Privacy: Google Ads (opent in …	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/legal/privacy-p…	Privacy: LinkedIn (opent in ni…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/about/privacy/	Privacy: Facebook (opent in ni…	new tab	Add '(opens in new tab)' to text
https://issuu.com/legal/privacy	Privacy: Issuu (opent in nieuw…	new tab	Add '(opens in new tab)' to text

134 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://business.safety.google/privacy/; https://www.linkedin.com/legal/privacy-policy; https://www.hotjar.com/legal/policies/privacy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://www.linkedin.com/legal/privacy-policy; https://www.facebook.com/about/privacy/; https://issuu.com/legal/privacy

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

title Erasmus University Rotterdam

3.37:1

#000000

#4C6568

needs 4.5:1 (normal text)

16px · top of page (header area)

span Overslaan en naar de inhoud gaan

3.37:1

#000000

#4C6568

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Erasmus Universiteit…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Uitgelicht	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Meest populaire tref…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Suggested content	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Primair	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Wissel naar taal	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Erasmus Extra: weten…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vind jouw bachelor i…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Hoe Rotterdam helpt …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vind jouw master in …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Nieuws	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Evenementen	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vergelijk 0 opleidin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Direct naar	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Informatie	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Onze kanalen	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Onze website gebruik…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Eur.nl	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Erasmus University R…	3.37:1	4.5:1	#000000	#4C6568	Fail
span Overslaan en naar de…	3.37:1	4.5:1	#000000	#4C6568	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+

Heading Hierarchy

31 headings

PASS

31 headings

Single H1 present

H2 Uitgelicht
H2 Meest populaire trefwoorden
H2 Suggested content
H2 Primair
H2 Wissel naar taal
H1 Erasmus Universiteit Rotterdam
H2 Onderwijs
H2 Onderzoek
H2 Over de EUR
H2 Erasmus Extra: wetenschapsverhalen op z’n Rotterdams
H2 Vind jouw bachelor in vijf stappen
H2 Hoe Rotterdam helpt dementie wereldwijd op te lossen
H2 Vind jouw master in vier stappen
H2 Nieuws
H3 WODC-rapport: meer ruimte nodig voor vernieuwende praktijkstructuren in de advocatuur om toegang tot recht te verbeteren
H3 Mathematisch modelleren om de wetenschap over schistosomiasis vooruit te helpen
H3 Op weg naar inclusief geschiedenisonderwijs?
H2 Evenementen
H3 Rotterdamlezing 2026
H3 Dialoog Academische Vrijheid 18 mei
H3 A UNIC Experience: Dagtrip naar Bochum, Duitsland
H2 Vergelijk 0 opleidingen
H3 @title
H2 Direct naar
H2 Informatie
H2 Direct naar
H2 Informatie
H2 Onze kanalen
H2 Making Minds Matter
H2 Onze website gebruikt cookies
H2 Eur.nl

A+

Alt Text Quality

1 of 12 images have issues

PASS

1 of 12 images have issues

1 image(s) with generic alt text

1 decorative image(s) correctly marked

10 image(s) with good alt text

12 images 10 good alt text 1 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-s--2	search	Zoeken	for/id

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Pagina niet gevonden | Erasmus University Rotterdam ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 31 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

●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

●ARIA toggle fields have accessible names

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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 `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

○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

○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.

○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>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

○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.