Skip to content
https://vu.nl

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
F
Alt Text Quality
Action
4 of 5 images have issues
FIX
4 of 5 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
4 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with good alt text
5 images 1 good alt text 4 missing
IssueCount
missing4 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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
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.
D
Lighthouse Accessibility Audits
Action
Score 66/100 — 7 failing, 16 passed
FIX
66

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > button div > button
div > button div > button

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.grid-x > div.cell > div.vuw-ratio-4-3 > img.vuw-image-coverfit div.grid-x > div.cell > div.vuw-ratio-4-3 > img.vuw-image-coverfit
div.grid-x > div.cell > div.vuw-ratio-4-3 > img.vuw-image-coverfit div.grid-x > div.cell > div.vuw-ratio-4-3 > img.vuw-image-coverfit
div.grid-x > div.cell > div.vuw-ratio-4-3 > img.vuw-image-coverfit div.grid-x > div.cell > div.vuw-ratio-4-3 > img.vuw-image-coverfit
div.grid-x > div.cell > div.vuw-ratio-4-3 > img.vuw-image-coverfit div.grid-x > div.cell > div.vuw-ratio-4-3 > img.vuw-image-coverfit

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Alle categorieën Promoties Voorlichting & informatiesessies Cursussen Workshop … div.cell > div.grid-x > div.cell > select#category-filter-b69a785e-1004-447b-848a-caf6759efdcd
Datum April 2026 Mei 2026 Juni 2026 Juli 2026 Augustus 2026 September 2026 Okto… div.cell > div.grid-x > div.cell > select#date-filter-b69a785e-1004-447b-848a-caf6759efdcd

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 > a div > a

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.

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
Leven in de wereld die we delen div.grid-x > a.vuw-card-hover > div.vuw-text-left > h3.vuw-h2-light

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section > ul section > ul
section > ul section > ul
section > ul section > ul
section > ul section > ul
nav > ul nav > ul

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li
li li

These are opportunities to improve the experience of reading tabular or list data using 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
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Identical links have the same purpose.
○`[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
○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
○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.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 landmarks
Info::
<main> landmark present
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.
Page Structure — as a screen reader sees it
BANNER (missing!) MAIN CONTENTINFO (missing!)

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
Form Accessibility
2 of 7 controls have issues
REVIEW
2 of 7 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="category-filter-9fbaf98e-dfed-4137-8d4a-cb242589c84f">; <select id="date-filter-9fbaf98e-dfed-4137-8d4a-cb242589c84f">
Info::
5 control(s) properly labeled
7 controls
5 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#cookie-59386504checkboxnone
#cookie-65807007checkboxnone
#cookie-54804469checkboxnone
#cookie-54738280checkboxnone
#cookie-50700783checkboxnone
#date-filter-9fbaf98e-dfed-4137-8d4a-cb242589c84fselect(none)none
#category-filter-9fbaf98e-dfed-4137-8d4a-cb242589c84fselect(none)none

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

<select id="category-filter-9fbaf98e-dfed-4137-8d4a-cb242589c84f">; <select id="date-filter-9fbaf98e-dfed-4137-8d4a-cb242589c84f">

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Pagina niet gevonden - Vrije Universiteit Amsterdam ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 2 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Vrije Universiteit A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Onderwijs21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Onderzoek21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Over de VU21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nieuws21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Agenda21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Samen voor een beter…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Direct naar21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Studie21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Uitgelicht21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Over de VU21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hoop door solidarite…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bewegen naar een vit…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Leven in de wereld d…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hoop door solidarite…21.00:13.0:1
#000000
#FFFFFF
Pass
title Vrije Universiteit A…21.00:14.5:1
#000000
#FFFFFF
Pass
vu-header-item Onderwijs21.00:14.5:1
#000000
#FFFFFF
Pass
vu-header-item Onderzoek9.61:14.5:1
#000000
#8FB4D0
Pass
vu-header-item Actueel5.46:14.5:1
#000000
#4888B5
Pass
vu-header-item Over de VU5.76:14.5:1
#000000
#4D8CB8
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+
Heading Hierarchy
15 headings
PASS
15 headings
Info::
Single H1 present
  • H1 Vrije Universiteit Amsterdam
  • H2 Onderwijs
  • H2 Onderzoek
  • H2 Over de VU
  • H2 Nieuws
  • H2 Agenda
  • H2 Samen voor een betere wereld
  • H3 Hoop door solidariteit
  • H3 Bewegen naar een vitale toekomst
  • H3 Leven in de wereld die we delen
  • H3 Hoop door solidariteit
  • H2 Direct naar
  • H2 Studie
  • H2 Uitgelicht
  • H2 Over de VU
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback