Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 1 pass AA only

title Umeå universitet

2.19:1

#000000

#2A4765

needs 4.5:1 (normal text)

16px · top of page (header area)

span "False"

2.19:1

#000000

#2A4765

needs 4.5:1 (normal text)

16px · top of page (header area)

a Hoppa direkt till innehållet

2.95:1

#000000

#385B7A

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

1 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)

Element	Ratio	Required	FG	BG	Result
h1 Umeå universitet	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 STUDENT	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Aktuellt	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Evenemang	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 I fokus: Forskning o…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Umeå universitet	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Cookie-samtycke	20.12:1	3.0:1	#000000	#FAFAFA	Pass
title Umeå universitet	2.19:1	4.5:1	#000000	#2A4765	Fail
span "False"	2.19:1	4.5:1	#000000	#2A4765	Fail
a Hoppa direkt till in…	2.95:1	4.5:1	#000000	#385B7A	Fail
span umu.se	4.79:1	4.5:1	#000000	#537D9D	Pass
a För studenter	7.49:1	4.5:1	#000000	#7F9EB8	Pass
a För forskare	8.07:1	4.5:1	#000000	#88A4BA	Pass
a Bibliotek	9.14:1	4.5:1	#000000	#90AFC7	Pass
a För medarbetare	12.05:1	4.5:1	#000000	#B1C7DA	Pass
span Logga in	14.72:1	4.5:1	#000000	#CBDAE7	Pass
span Student	15.78:1	4.5:1	#000000	#D4E1EC	Pass
p Logga in på student…	14.29:1	4.5:1	#000000	#C9D7E1	Pass
span Redigera	14.67:1	4.5:1	#000000	#CADAE5	Pass
p Redigera innehåll p…	13.82:1	4.5:1	#000000	#C4D4DE	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.

A+

Heading Hierarchy

15 headings

PASS

15 headings

Single H1 present

H1 Umeå universitet
H2 Banbrytande forskning för ett hållbart samhälle
H2 Banbrytande forskning för ett hållbart samhälle
H2 Kom närmare din framtid
H2 Kom närmare din framtid
H2 Nordens mest hälsosamma campus
H2 Nordens mest hälsosamma campus
H2 Gensaxen CRISPR-Cas9 revolutionerar gentekniken
H2 Gensaxen CRISPR-Cas9 revolutionerar gentekniken
H2 STUDENT
H2 Aktuellt
H2 Evenemang
H2 I fokus: Forskning om skolan
H2 Umeå universitet
H2 Cookie-samtycke

A+

Alt Text Quality

1 of 43 images have issues

PASS

1 of 43 images have issues

1 image(s) with filename as alt text

23 decorative image(s) correctly marked

19 image(s) with good alt text

43 images 19 good alt text 23 decorative 1 generic

Issue	Count
filename	1 image(s)

A+

Form Accessibility

All 8 controls labeled

PASS

All 8 controls labeled

8 control(s) properly labeled

8 controls

8 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#headerSearchField	text	Sökfält	aria-label
#headerSearchClear	reset	X Ta bort text i sökfält	aria-label
#/sok/Allt	radio	Allt	for/id
#/sok/Utbildning	radio	Utbildning	for/id
#/sok/Forskning	radio	Forskning	for/id
#/sok/Personal	radio	Personal	for/id
#/sok/Studentwebb	radio	Studentwebb	for/id
#/sok/Nyheter	radio	Nyheter	for/id

A+

Link & Button Quality

59 links, 15 buttons — all OK

PASS

59 links, 15 buttons — all OK

59 link(s) with descriptive text

59 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

74 links and buttons have descriptive text

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 26 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

●`[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 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

○`[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

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

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