Skip to content
https://wur.nl

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title Welcome to wur ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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.
Got: #f3ecd3
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::
9 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 9 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
24 landmarks
REVIEW
24 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
9 of 9 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header NAV MAIN CONTENTINFO footer

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

B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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+
Heading Hierarchy
50 headings
PASS
50 headings
Info::
Single H1 present
  • H2 Bachelor
  • H2 Master
  • H2 toegepast onderzoek
  • H1 Shape responsible change
  • H2 Nog studiekeuzetwijfels? Hak 4 juni de knoop door.
  • H2 Wageningen University & Research
  • H2 Studeren bij WUR
  • H2 Samenwerken met WUR
  • H2 Volg de laatste ontwikkelingen
  • H2 Wageningse CRISPR-variant knipt selectief tumor-DNA
  • H2 Stijgende voedselprijzen door oorlog in Iran: dit zijn de oorzaken en gevolgen
  • H2 Van uitstoot naar kansen: hoe klimaatfinanciering duurzaamheid in de zuivelsector kan stimuleren
  • H2 WUR ontwikkelt gesimuleerde kasomgeving voor snellere robotontwikkeling
  • H2 Wageningse keuzehulp biedt industrie houvast bij duurzame verpakkingskeuzes
  • H2 Ontdek onze thema's
  • H3 Duurzame voedselsystemen
  • H3 Biodiversiteit en veerkrachtige ecosystemen
  • H3 Gezondheid voor alles wat leeft
  • H3 Klimaatbestendige toekomst
  • H3 Biobased en circulaire samenleving
  • H3 Duurzaam water- en landgebruik
  • H3 Duurzame voedselsystemen
  • H2 Duurzame voedselsystemen
  • H3 Biodiversiteit en veerkrachtige ecosystemen
  • H2 Biodiversiteit en veerkrachtige ecosystemen
  • H3 Gezondheid voor alles wat leeft
  • H2 Gezondheid voor alles wat leeft
  • H3 Klimaatbestendige toekomst
  • H2 Klimaatbestendige toekomst
  • H3 Biobased en circulaire samenleving
  • H2 Biobased en circulaire samenleving
  • H3 Duurzaam water- en landgebruik
  • H2 Duurzaam water- en landgebruik
  • H2 Ervaar studeren in Wageningen
  • H2 Over WUR
  • H3 Wat brengt de toekomst als de natuur leidend is bij de inrichting van steden en landschappen? Als vervolg op NL2120 schetsten wetenschappers en Wageningse studenten een hoopvolle toekomst voor heel Eu
  • H2 Ontdek meer
  • H3 Ontdek onze verhalen en nieuws
  • H3 Ga naar de agenda, promoties en inauguraties
  • H3 Bekijk de leerstoelgroepen
  • H3 Lees meer over WUR
  • H3 Neem contact op
  • H2 Studeren bij WUR
  • H2 Samenwerken met WUR
  • H2 Over ons
  • H2 Social Links
  • H2 Studeren bij WUR
  • H2 Samenwerken met WUR
  • H2 Over ons
  • H2 Social Links
A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
6 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
10 images 4 good alt text 6 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-inputsearchZoek of vraag...aria-label
A
Web Manifest
Valid manifest
PASS
Valid manifest
Info::
Name present: Wageningen University & Research
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Wageningen University & Research ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode browser ✗
Name Wageningen University & Research Display Mode browser Theme Color #ffffff Background Color #ffffff Icons 2 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
h1 Shape responsible ch…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Bachelor19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Master19.42:13.0:1
#000000
#FBF6E5
Pass
h2 toegepast onderzoek19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Nog studiekeuzetwijf…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Wageningen Universit…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Studeren bij WUR19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Samenwerken met WUR19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Volg de laatste ontw…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Wageningse CRISPR-va…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Stijgende voedselpri…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Van uitstoot naar ka…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 WUR ontwikkelt gesim…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Wageningse keuzehulp…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Ontdek onze thema's19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Duurzame voedselsyst…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Biodiversiteit en ve…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Gezondheid voor alle…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Klimaatbestendige to…19.42:13.0:1
#000000
#FBF6E5
Pass
h2 Biobased en circulai…19.42:13.0:1
#000000
#FBF6E5
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 93/100 — 3 failing, 27 passed
PASS
93

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

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._1stm0fs4 > div.nczjrn0 > button._15nv45ab > a div._1stm0fs4 > div.nczjrn0 > button._15nv45ab > 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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Statistiek 1 div._1femi570 > div.nczjrn0 > div.nczjrncp > button._4qa3lrf
Statistiek 2 div._1femi570 > div.nczjrn0 > div.nczjrncp > button._4qa3lrf

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
“Het leukste aan WUR vind ik de mooie campus, de persoonlijke begeleiding en ho… section#over-ons-17733 > div._1b0rtru0 > div.hm0psm0 > a._1ak1j5b0
○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.
●`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
●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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[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
○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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback