Skip to content
https://uva.nl

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: University of Amsterdam
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name University of Amsterdam ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name University of Amsterdam Icons 6 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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
7 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 7 <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
26 landmarks
REVIEW
26 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
1 of 7 <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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "skiplinks" SEARCH 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
22 icon(s) detected
REVIEW
22 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
title Universiteit van Amsterdam
1.08:1
#000000
on
#0D0C0C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Naar de hoofdcontent
1.08:1
#000000
on
#0D0C0C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Naar het zoekveld
1.08:1
#000000
on
#0D0C0C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Naar de footer
1.09:1
#000000
on
#100E10
needs 4.5:1 (normal text)
16px · top of page (header area)
div Voor de beste ervaring schakelt u JavaSc…
1.11:1
#000000
on
#140F10
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Kies een minor bij d…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Een gezond microbioo…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Oorlog en weerbaarhe…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Waarom de eerste pre…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Onderzoek21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Over de UvA21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Cookie Consent21.00:13.0:1
#000000
#FFFFFF
Pass
title Universiteit van Ams…1.08:14.5:1
#000000
#0D0C0C
Fail
a Naar de hoofdcontent1.08:14.5:1
#000000
#0D0C0C
Fail
a Naar het zoekveld1.08:14.5:1
#000000
#0D0C0C
Fail
a Naar de footer1.09:14.5:1
#000000
#100E10
Fail
div Voor de beste ervari…1.11:14.5:1
#000000
#140F10
Fail
div Je gebruikt een niet…8.02:14.5:1
#000000
#A39FA0
Pass
span Zoek...21.00:14.5:1
#000000
#FFFFFF
Pass
span Vergelijk21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
span Onderwijs21.00:14.5:1
#000000
#FFFFFF
Pass
span Bachelor21.00:14.5:1
#000000
#FFFFFF
Pass
span Master21.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.

A
Heading Hierarchy
22 headings
PASS
22 headings
Warning::
Multiple H1 headings (7 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Kies een minor bij de UvA
  • H1 Een gezond microbioom duplicate H1
  • H1 Oorlog en weerbaarheid duplicate H1
  • H1 Waarom de eerste premier van Nederland werd vergeten duplicate H1
  • H1 Onderzoek duplicate H1
  • H2 Klimaatinstituut SEVEN
  • H2 Kunnen we voorkomen dat ChatGPT vooroordelen verspreidt?
  • H2 Bezoek Prinses van Oranje aan Amsterdam Science Park
  • H2 Meet the professor: Amsterdamse wetenschappers geven gastles op Amsterdamse basisscholen
  • H2 70 jaar Nederlandse kindertelevisie: meer illustratie dan animatie
  • H2 Informatierecht en technologiebestuur in een tijdperk van ontwrichting
  • H2 Where to Belong? Emotie, de natie en de sociologie
  • H2 Verweven Vrijheid
  • H2 Carrièrefestival
  • H2 Israël/Gaza
  • H2 Samenwerking met derden
  • H2 Werken in de ICT
  • H2 Werken als managementassistent
  • H2 Werken in de facilitaire dienstverlening
  • H2 Werken bij de Universiteit van Amsterdam
  • H1 Over de UvA duplicate H1
  • H1 Cookie Consent duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Alt Text Quality
All 14 images OK
PASS
All 14 images OK
Info::
14 decorative image(s) correctly marked
14 images 14 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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Pagina niet gevonden - 404 - Universiteit van Amsterdam ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /webfiles/1765960941537/css/print.min.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /webfiles/1765960941537/css/print.min.css ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 30 passed
PASS
96

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.c-mainmenu__innerrow > nav.c-mainmenu > div.c-mainmenu__statusbar > button#btnMenuClose div.c-mainmenu__innerrow > nav.c-mainmenu > div.c-mainmenu__statusbar > button#btnMenuClose
div.c-mainmenu__menu > ul > li.c-mainmenu__item > button.chevron div.c-mainmenu__menu > ul > li.c-mainmenu__item > button.chevron
div.c-mainmenu__menu > ul > li.c-mainmenu__item > button.chevron div.c-mainmenu__menu > ul > li.c-mainmenu__item > button.chevron
div.c-mainmenu__menu > ul > li.c-mainmenu__item > button.chevron div.c-mainmenu__menu > ul > li.c-mainmenu__item > button.chevron
div.c-mainmenu__menu > ul > li.c-mainmenu__item > button.chevron div.c-mainmenu__menu > ul > li.c-mainmenu__item > button.chevron

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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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.
●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
●Skip links are focusable.
●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 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 type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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