Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Alt Text Quality

Action

2 of 16 images have issues

FIX

2 of 16 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

1 image(s) with alt text over 125 characters

4 decorative image(s) correctly marked

9 image(s) with good alt text

16 images 9 good alt text 4 decorative 2 missing

Issue	Count
missing	2 image(s)
too long	1 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

Link & Button Quality

Action

12 issue(s) across 150 links and 5 buttons

FIX

12 issue(s) across 150 links and 5 buttons

10 link(s) with no accessible text

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

Got: #; #; #; #; #; #; a#lpctanchor_pHhJelT5h_5XSFxdRJKd7w; a#newsstoriesandmore71304066; a.widget-newsevents__item__link (#446 on page); a.widget-newsevents__item__link (#512 on page)

4 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.utwente.nl/en/events/2026/4/736244/getting-pumped-up-for-the-bata"]; a[href="https://www.utwente.nl/en/events/2026/4/830648/robotics-day-2026"]; a[href="https://www.utwente.nl/en/events/2026/4/712963/joint-research-day-tampere-uni…"]; a[href="https://www.utwente.nl/en/events/2026/5/736260/how-can-we-break-the-power-of-…"]

1 link(s) open in new tab without warning

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

Got: https://youtu.be/jjstlAZLXgI

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.contentpart__topmenuitem (#73 on page); button.contentpart__topmenuitem (#141 on page)

135 link(s) with descriptive text

150 links

10 empty

0 generic text

1 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.utwente.nl/en/events/2026/4/…	Studium GeneraleGetting pumped…	img no alt	Add alt attribute to the image
https://www.utwente.nl/en/events/2026/4/…	Conference / symposiumRobotics…	img no alt	Add alt attribute to the image
https://www.utwente.nl/en/events/2026/4/…	Conference / symposiumJoint re…	img no alt	Add alt attribute to the image
https://www.utwente.nl/en/events/2026/5/…	Studium GeneraleHow can we bre…	img no alt	Add alt attribute to the image
	(empty)	empty	Add link text or aria-label
https://youtu.be/jjstlAZLXgI	the YouTube website.	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

138 links and buttons have descriptive text

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

#; #; #; #; #; #; a#lpctanchor_pHhJelT5h_5XSFxdRJKd7w; a#newsstoriesandmore71304066; a.widget-newsevents__item__link (#446 on page); a.widget-newsevents__item__link (#512 on page)

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.utwente.nl/en/events/2026/4/736244/getting-pumped-up-for-the-bata"]; a[href="https://www.utwente.nl/en/events/2026/4/830648/robotics-day-2026"]; a[href="https://www.utwente.nl/en/events/2026/4/712963/joint-research-day-tampere-uni…"]; a[href="https://www.utwente.nl/en/events/2026/5/736260/how-can-we-break-the-power-of-…"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://youtu.be/jjstlAZLXgI

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.contentpart__topmenuitem (#73 on page); button.contentpart__topmenuitem (#141 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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: #ffffff

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 ✗

Heading Hierarchy

5 headings

REVIEW

5 headings

No H1 heading found

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

H2 Choose a study programme
H2 Latest news & stories
H2 Latest news & stories
H2 UPCOMING EVENTS
H2 Cookies

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: Deze pagina bestaat niet (meer) / Page does not exist ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: University of Twente.

192x192 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name University of Twente. ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓

Name University of Twente. Display Mode standalone Theme Color #ffffff Icons 1 icon(s)

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 1 pass AA only

title University of Twente (UT) | Research Uni…

1.26:1

#000000

#1A1F23

needs 4.5:1 (normal text)

16px · top of page (header area)

button Skip to main content

1.26:1

#000000

#1A1F23

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Choose a study progr…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 Latest news & storie…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 Latest news & storie…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 UPCOMING EVENTS	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 Cookies	16.67:1	3.0:1	#000000	#E5E5E5	Pass
title University of Twente…	1.26:1	4.5:1	#000000	#1A1F23	Fail
button Skip to main content	1.26:1	4.5:1	#000000	#1A1F23	Fail
div Menu	7.62:1	4.5:1	#000000	#7FA0B8	Pass
a UT Login	8.63:1	4.5:1	#000000	#8CAAC0	Pass
a Nederlands	9.54:1	4.5:1	#000000	#95B3C6	Pass
a English	11.42:1	4.5:1	#000000	#B0C2CA	Pass
a LatAm website	5.68:1	4.5:1	#000000	#838774	Pass
a Italian website	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a German website	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Education	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Research	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Business	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Organisation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Campus	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span News & events	21.00:1	4.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.

Lighthouse Accessibility Audits

Score 82/100 — 4 failing, 22 passed

REVIEW

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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Students at the entrance of the University of Twente `div.contentpart > header.contentpart__header > div.contentpart__header-videos > div.contentpart__header-videomobile`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Students at the entrance of the University of Twente `div.contentpart > header.contentpart__header > div.contentpart__header-videos > div.contentpart__header-videomobile`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.menupart > div.menupart__menu-container > div.menupart__topmenu > button.contentpart__topmenuitem `div.menupart > div.menupart__menu-container > div.menupart__topmenu > button.contentpart__topmenuitem`

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.searchsheet > div.searchsheet__content > div.searchsheet__header > a.searchsheet__close `div.searchsheet > div.searchsheet__content > div.searchsheet__header > a.searchsheet__close`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

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

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

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
q	text	Search in site	aria-label

Favicon & Branding

6 icon(s) detected

PASS

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.