Skip to content
https://gu.se

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
3
REVIEW
5
PASS
5
INFO
0
Checks
13
5 PASS 5 REVIEW 3 FIX
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
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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
8 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 8 <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
14 landmarks
REVIEW
14 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
1 of 8 <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 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
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 - Sidan kunde inte hittas | Göteborgs universitet Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 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::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA
span Gå direkt till
3.15:1
#000000
on
#5B5C62
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Meny
3.32:1
#000000
on
#635E64
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Enter
3.88:1
#000000
on
#587311
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Gå direkt till
1.19:1
#000000
on
#121B07
needs 4.5:1 (normal text)
16px · above the fold
a Sidfoten
1.40:1
#000000
on
#1C2B01
needs 4.5:1 (normal text)
16px · above the fold
span Enter
1.43:1
#000000
on
#222B16
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span Gå direkt till
1.05:1
#000000
on
#050A00
needs 4.5:1 (normal text)
16px · mid-page

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Göteborgs universit…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nyheter21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Evenemang21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Användning av cooki…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Genvägar21.00:13.0:1
#000000
#FFFFFF
Pass
title Hem | Göteborgs uni…21.00:14.5:1
#000000
#FFFFFF
Pass
button Stäng21.00:14.5:1
#000000
#FFFFFF
Pass
span Gå direkt till21.00:14.5:1
#000000
#FFFFFF
Pass
a Huvudinnehåll21.00:14.5:1
#000000
#FFFFFF
Pass
span Enter21.00:14.5:1
#000000
#FFFFFF
Pass
span Gå direkt till3.15:14.5:1
#000000
#5B5C62
Fail
a Meny3.32:14.5:1
#000000
#635E64
Fail
span Enter9.11:14.5:1
#000000
#C5A39E
Pass
span Gå direkt till14.04:14.5:1
#000000
#D4D3D1
Pass
a Sökfunktionen13.45:14.5:1
#000000
#CBD1C3
Pass
span Enter3.88:14.5:1
#000000
#587311
Fail
span Gå direkt till1.19:14.5:1
#000000
#121B07
Fail
a Sidfoten1.40:14.5:1
#000000
#1C2B01
Fail
span Enter1.43:14.5:1
#000000
#222B16
Fail
span Gå direkt till1.05:14.5:1
#000000
#050A00
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+
Heading Hierarchy
11 headings
PASS
11 headings
Info::
Single H1 present
  • H1 Göteborgs universitet
  • H2 Studera
  • H2 Forskning
  • H2 Universitetet
  • H2 Nyheter
  • H2 Evenemang
  • H3 Bli en av oss
  • H3 Samverkan och innovation
  • H3 En gång student, alltid alumn
  • H2 Användning av cookies
  • H2 Genvägar
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
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#header-togglecheckboxOpen main menuaria-label
#global_search_block-inputtextSökfor/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_KCPDQvTMXfxOKaKJ0R2pJKT-DMLW2eEEPSZBDjXL9zo.css?delta=2&language=sv&theme=gu_ruby&include=eJxtyEEOwyAMBMAPkfIk5JgVcuvgyJik_L499tDTSMPmyNXnSfqgJ70T_0QVUmsJs7DZS_DlOFWoM_K_LDs5UpvF574ycciFbcRS6S0pLZtRqgy2C76ydbBpGhK4paKQwiNLl_gABto6qg
Print Stylesheet Print Optimized
Print stylesheet /sites/default/files/css/css_KCPDQvTMXfxOKaKJ0R2pJKT-DMLW2eEEPSZBDjXL9zo.css?delta=2&language=sv&theme=gu_ruby&include=eJxtyEEOwyAMBMAPkfIk5JgVcuvgyJik_L499tDTSMPmyNXnSfqgJ70T_0QVUmsJs7DZS_DlOFWoM_K_LDs5UpvF574ycciFbcRS6S0pLZtRqgy2C76ydbBpGhK4paKQwiNLl_gABto6qg Inline @media print Not detected
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 29 passed
PASS
100

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.

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
Göteborgs universitet div.top-bar > div.top-bar__top > div.top-bar__column > a.brand
Utställning Examen 2026: Wish Me Luck Startdatum 17 Apr 2026 Till - Slutdatum 3… div.row > div.columns > div.layout__component > a.blurb
Föreläsning Praktiknära prestationsforskning Startdatum 22 Apr 2026 div.row > div.columns > div.layout__component > a.blurb
Webinar Digitalt välmående på jobbet – varför insatser inte får effekt Startdat… div.row > div.columns > div.layout__component > a.blurb
Seminarium När känslor och prislappar styr: vad experiment lär om våra val Star… div.row > div.columns > div.layout__component > a.blurb
Seminarium Pressfrihetens dag 2026 Startdatum 28 Apr 2026 div.row > div.columns > div.layout__component > a.blurb
Föreläsning Ett HUM om: Vi tänker på romarriket IV Startdatum 28 Apr 2026 div.row > div.columns > div.layout__component > a.blurb
Akademisk högtid Valborg med Göteborgs universitets studentkårer Startdatum 30 … div.row > div.columns > div.layout__component > a.blurb
Föreläsning Vad vet vi om: återgång till arbete efter sjukskrivning Startdatum … div.row > div.columns > div.layout__component > a.blurb
Seminarium Mediebarometern 2025 Startdatum 5 Maj 2026 div.row > div.columns > div.layout__component > a.blurb
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
`[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.
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
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[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
Form elements have associated labels
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.
Image elements do not have `[alt]` attributes that are redundant text.
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