Skip to content
https://chalmers.se

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 REVIEW 3 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
4 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 4 <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.
C
Form Accessibility
Action
4 of 9 controls have issues
REVIEW
4 of 9 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">
Info::
5 control(s) properly labeled
9 controls
5 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxExternal servicesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatisticsfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxExternal mediafor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

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

C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Chalmers
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Chalmers ✓192×192 icon ✗512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name Chalmers Display Mode standalone Theme Color #003050 Background Color #003050 Icons 1 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #003050 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 Forskning och utbildning för en bättre…
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Ny gemensam visuell identitet
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Chalmers tekniska högskola
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Starta din Chalmersresa
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 För en bättre framtid
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nätverk och samarbete
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Aktuellt
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nyheter
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Kalender
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Chalmers i siffror (2025)
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Utbildning
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tillsammans utvecklar vi framtiden
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Kontakta Chalmers
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Utbildning
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Utbildning
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Genvägar
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Genvägar
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Om webbplatsen
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Om webbplatsen
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Kontakta Chalmers
1.82:1
#000000
on
#393939
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Forskning och utbild…1.82:13.0:1
#000000
#393939
Fail
h1 Ny gemensam visuell …1.82:13.0:1
#000000
#393939
Fail
h2 Chalmers tekniska h…1.82:13.0:1
#000000
#393939
Fail
h2 Starta din Chalmersr…1.82:13.0:1
#000000
#393939
Fail
h2 För en bättre fram…1.82:13.0:1
#000000
#393939
Fail
h2 Nätverk och samarbe…1.82:13.0:1
#000000
#393939
Fail
h2 Aktuellt1.82:13.0:1
#000000
#393939
Fail
h2 Nyheter1.82:13.0:1
#000000
#393939
Fail
h2 Kalender1.82:13.0:1
#000000
#393939
Fail
h2 Chalmers i siffror (…1.82:13.0:1
#000000
#393939
Fail
h2 Utbildning1.82:13.0:1
#000000
#393939
Fail
h2 Tillsammans utveckla…1.82:13.0:1
#000000
#393939
Fail
h2 Kontakta Chalmers1.82:13.0:1
#000000
#393939
Fail
h2 Utbildning1.82:13.0:1
#000000
#393939
Fail
h2 Utbildning1.82:13.0:1
#000000
#393939
Fail
h2 Genvägar1.82:13.0:1
#000000
#393939
Fail
h2 Genvägar1.82:13.0:1
#000000
#393939
Fail
h2 Om webbplatsen1.82:13.0:1
#000000
#393939
Fail
h2 Om webbplatsen1.82:13.0:1
#000000
#393939
Fail
h2 Kontakta Chalmers1.82:13.0:1
#000000
#393939
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
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
4 <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 "Top navigation" 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
22 headings
PASS
22 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Forskning och utbildning för en bättre värld
  • H2 Chalmers tekniska högskola
  • H2 Starta din Chalmersresa
  • H2 För en bättre framtid
  • H2 Nätverk och samarbete
  • H1 Ny gemensam visuell identitet duplicate H1
  • H2 Aktuellt
  • H2 Nyheter
  • H2 Kalender
  • H2 Chalmers i siffror (2025)
  • H2 Utbildning
  • H2 Tillsammans utvecklar vi framtiden
  • H2 Kontakta Chalmers
  • H2 Utbildning
  • H2 Utbildning
  • H2 Genvägar
  • H2 Genvägar
  • H2 Om webbplatsen
  • H2 Om webbplatsen
  • H2 Kontakta Chalmers
  • H2 Sociala medier
  • H2 Sociala medier

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
1 of 30 images have issues
PASS
1 of 30 images have issues
Warning::
1 image(s) with generic alt text
Info::
17 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
30 images 12 good alt text 17 decorative 1 generic
IssueCount
generic1 image(s)
A
Favicon & Branding
7 icon(s) detected
PASS
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 30 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.

○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
●Buttons have an accessible name
●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 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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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 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
○Links are distinguishable without relying on color.
○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.
○`<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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback