Skip to content
https://au.dk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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 Missing
✓ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 1 <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.
C
Landmark Structure
Action
6 landmarks
REVIEW
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 SEARCH MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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
Heading Hierarchy
57 headings, 1 skip(s)
REVIEW
57 headings, 1 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Fælles sider for ph.d.-studerende
  • H2 Ph.d.-portaler
  • H2 Fælles sider for medarbejdere på AU
  • H2 Medarbejderportaler
  • H2 Fakulteter og institutter
  • H5 Find uddannelse skipped
  • H5 Studievejledning
  • H5 Besøg AU
  • H5 Kvalitet
  • H5 Find
  • H5 Aktuel forskning
  • H5 Talent
  • H5 Samarbejde med forskere
  • H5 Samarbejde med studerende
  • H5 Gymnasier
  • H5 Myndigheder
  • H5 Organisation
  • H5 Kontakt
  • H5 Profil
  • H5 Job
  • H3 Forskningens Døgn d. 22. april
  • H2 Forskningens døgn d. 22. april
  • H2 Vil du læse på AU?
  • H2 Information til
  • H1 Til gymnasielærere
  • H1 Vejledning på AU duplicate H1
  • H2 Gymnasieportalen
  • H2 Kompetenceudvikling
  • H2 Det rullende Universitet
  • H1 Til pressen duplicate H1
  • H2 Pressekontakt
  • H2 Om AU
  • H2 Pressefotos
  • H1 Til jobsøgende duplicate H1
  • H2 Ledige jobs
  • H1 Til besøgende duplicate H1
  • H2 Find vej
  • H2 Museer
  • H2 Guidede rundvisninger
  • H1 Til Alumner duplicate H1
  • H2 Alumneportalen
  • H2 Efter- og videreuddannelse
  • H3 AKTUELT
  • H4 ≥ Flere arrangementer
  • H4 ≥ Flere nyheder
  • H2 Et bæredygtigt universitet
  • H2 Ekspertliste: Krig i Mellemøsten
  • H2 Ekspertliste: Folketingsvalg 2026
  • H2 Diversitet og ligestilling
  • H3 Aarhus Universitet
  • H3 Om os
  • H3 Uddannelser på AU
  • H3 Genveje
  • H2 Cookies giver dig en bedre brugeroplevelse
  • H2 Hvad er en cookie?
  • H2 Hvilke data indsamles via cookies?
  • H2 Slet cookies

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

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - siden ikke fundet / page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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
h1 Til gymnasielærere
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Vejledning på AU
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Til pressen
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Til jobsøgende
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Til besøgende
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Til Alumner
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Fælles sider for ph.d.-studerende
1.29:1
#000000
on
#002141
needs 3.0:1 (large text)
24px · above the fold
h2 Fælles sider for medarbejdere på AU
1.24:1
#000000
on
#26143A
needs 3.0:1 (large text)
24px · mid-page
h2 Medarbejderportaler
1.23:1
#000000
on
#251339
needs 3.0:1 (large text)
24px · mid-page
h2 Fakulteter og institutter
1.23:1
#000000
on
#251339
needs 3.0:1 (large text)
24px · mid-page
h2 Forskningens døgn d. 22. april
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Vil du læse på AU?
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Information til
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Gymnasieportalen
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Kompetenceudvikling
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Det rullende Universitet
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pressekontakt
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Om AU
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pressefotos
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ledige jobs
1.23:1
#000000
on
#261339
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Til gymnasielærere1.23:13.0:1
#000000
#261339
Fail
h1 Vejledning på AU1.23:13.0:1
#000000
#261339
Fail
h1 Til pressen1.23:13.0:1
#000000
#261339
Fail
h1 Til jobsøgende1.23:13.0:1
#000000
#261339
Fail
h1 Til besøgende1.23:13.0:1
#000000
#261339
Fail
h1 Til Alumner1.23:13.0:1
#000000
#261339
Fail
h2 Fælles sider for ph…1.29:13.0:1
#000000
#002141
Fail
h2 Fælles sider for me…1.24:13.0:1
#000000
#26143A
Fail
h2 Medarbejderportaler1.23:13.0:1
#000000
#251339
Fail
h2 Fakulteter og instit…1.23:13.0:1
#000000
#251339
Fail
h2 Forskningens døgn d…1.23:13.0:1
#000000
#261339
Fail
h2 Vil du læse på AU?1.23:13.0:1
#000000
#261339
Fail
h2 Information til1.23:13.0:1
#000000
#261339
Fail
h2 Gymnasieportalen1.23:13.0:1
#000000
#261339
Fail
h2 Kompetenceudvikling1.23:13.0:1
#000000
#261339
Fail
h2 Det rullende Univers…1.23:13.0:1
#000000
#261339
Fail
h2 Pressekontakt1.23:13.0:1
#000000
#261339
Fail
h2 Om AU1.23:13.0:1
#000000
#261339
Fail
h2 Pressefotos1.23:13.0:1
#000000
#261339
Fail
h2 Ledige jobs1.23:13.0:1
#000000
#261339
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+
Alt Text Quality
All 18 images OK
PASS
All 18 images OK
Info::
15 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
18 images 3 good alt text 15 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 7 controls have issues
PASS
1 of 7 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
6 control(s) properly labeled
7 controls
6 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#cludo-search-form-inputsearchIndtast søgekriteriumaria-label
#cookiescript_category_strictcheckboxNødvendigefor/id
#cookiescript_category_performancecheckboxStatistiskefor/id
#cookiescript_category_targetingcheckboxMarketingfor/id
#cookiescript_category_functionalitycheckboxFunktionellefor/id
#cookiescript_category_unclassifiedcheckboxUklassificeredefor/id
inputsubmit(none)none

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

<input type="submit">

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

A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 33 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.columns > div.title-bar > div.mobile-nav > button.menu-icon div.columns > div.title-bar > div.mobile-nav > button.menu-icon

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
Cookies på au.dk div.row > div.small-12 > p.muted > a
Privatlivspolitik div.row > div.small-12 > p.muted > a
Tilgængelighedserklæring div.row > div.small-12 > p.muted > a
239037 / i40 body.general > footer > div.page-id

These are opportunities to improve the legibility of your content.

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
Privatlivspolitik div.row > div.small-12 > p.muted > a
Tilgængelighedserklæring div.row > div.small-12 > p.muted > a

These items highlight common accessibility best practices.

○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
●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.
●`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
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●`<object>` elements have alternate text
●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.
●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.
●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.
○`[accesskey]` values are unique
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○Select elements have associated label elements.
○Skip links are focusable.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback