Skip to content
https://aau.dk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓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: #ffffff
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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
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.
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Du bestemmer over dine data
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · top of page (header area)
h2 Cookiepolitik
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hvad er en cookie?
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hjemmesidens brug af cookies
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hvor længe bliver cookies gemt?
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sådan afviser eller sletter du cookies
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hvordan sletter man cookies?
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ændring af dit samtykke
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Har du spørgsmål?
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hvad vil du læse?
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nyheder fra AAU
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Science Café
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Udsathed og omsorg i realitydokumentaren…
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Invitation for PhD defence by Mads Juul …
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Science Café
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Invitation for PhD defence by Mads Juul …
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Udsathed og omsorg i realitydokumentaren…
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Nødvendige
1.09:1
#000000
on
#170C08
needs 3.0:1 (large text)
19px · above the fold
h3 Funktionelle
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Statistiske
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Du bestemmer over di…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Cookiepolitik2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Hvad er en cookie?2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Hjemmesidens brug af…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Hvor længe bliver c…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Sådan afviser eller…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Hvordan sletter man …2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Ændring af dit samt…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Har du spørgsmål?2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Hvad vil du læse?2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Nyheder fra AAU2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Science Café2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Udsathed og omsorg i…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Invitation for PhD d…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Science Café2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Invitation for PhD d…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Udsathed og omsorg i…2.45:13.0:1
#000000
#4C4C4C
Fail
h3 Nødvendige1.09:13.0:1
#000000
#170C08
Fail
h3 Funktionelle2.45:13.0:1
#000000
#4C4C4C
Fail
h3 Statistiske2.45:13.0:1
#000000
#4C4C4C
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
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "menu" MAIN CONTENTINFO footer

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
Heading Hierarchy
28 headings, 1 skip(s)
PASS
28 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Du bestemmer over dine data
  • H3 Nødvendige
  • H3 Funktionelle
  • H3 Statistiske
  • H3 Marketing
  • H3 Uklassificerede
  • H2 Cookiepolitik
  • H2 Hvad er en cookie?
  • H2 Hjemmesidens brug af cookies
  • H2 Hvor længe bliver cookies gemt?
  • H2 Sådan afviser eller sletter du cookies
  • H2 Hvordan sletter man cookies?
  • H2 Ændring af dit samtykke
  • H2 Har du spørgsmål?
  • H1 Er du nys­ger­rig?
  • H2 Hvad vil du læse?
  • H2 Nyheder fra AAU
  • H3 Tema: Børn og unges trivsel
  • H2 Science Café
  • H2 Udsathed og omsorg i realitydokumentaren og samtidspoesien
  • H2 Invitation for PhD defence by Mads Juul Christensen
  • H2 Science Café
  • H2 Invitation for PhD defence by Mads Juul Christensen
  • H2 Udsathed og omsorg i realitydokumentaren og samtidspoesien
  • H6 Kontakt skipped
  • H6 Om AAU
  • H6 Genveje
  • H6 Service

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
23 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
24 images 1 good alt text 23 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cookie_cat_functionalcheckboxnone
#cookie_cat_statisticcheckboxnone
#cookie_cat_marketingcheckboxnone
A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 26 passed
PASS
91

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.Header_Header_wrapper___224D > div.Container_Container__zqqcB > div.Header_Header_inner__pqcOe > button.MobileNavigation_MobileNavigation_toggle__MLaxX div.Header_Header_wrapper___224D > div.Container_Container__zqqcB > div.Header_Header_inner__pqcOe > button.MobileNavigation_MobileNavigation_toggle__MLaxX

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.Header_Header_inner__pqcOe > div.MobileNavigation_MobileNavigation_wrapper__z9Z3W > div.MobileNavigation_MobileNavigation_toolsDrawer__O8q4q > a.Link_Link__GD7Gp div.Header_Header_inner__pqcOe > div.MobileNavigation_MobileNavigation_wrapper__z9Z3W > div.MobileNavigation_MobileNavigation_toolsDrawer__O8q4q > a.Link_Link__GD7Gp

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Kontakt div.Accordion_Accordion__0PHKB > div.AccordionItem_isDark__vvIWK > button#trigger-globalFooterAddress-92deca84-b050-4864-8551-ecb3ac5ec148 > h6.Heading_Heading__7szv_

These are opportunities to improve keyboard navigation in your application.

○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
●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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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 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.
○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.
○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.
○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