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

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✗ 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

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

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: Denne siden finnes ikke / 404: this page does not exist ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 12 pass AA only

title Forsiden - Universitetet i Oslo

1.16:1

#000000

#101528

needs 4.5:1 (normal text)

16px · top of page (header area)

a Hopp til hovedinnhold

1.16:1

#000000

#101528

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Dette nettstedet bru…	5.92:1	3.0:1	#000000	#888888	Pass
h1 Forsiden	5.92:1	3.0:1	#000000	#888888	Pass
h2 UiO i sosiale medier	5.92:1	3.0:1	#000000	#888888	Pass
h2 Kontakt	5.92:1	3.0:1	#000000	#888888	Pass
h2 Om nettstedet	5.92:1	3.0:1	#000000	#888888	Pass
h2 Ansvarlig for denne …	5.92:1	3.0:1	#000000	#888888	Pass
title Forsiden - Universit…	1.16:1	4.5:1	#000000	#101528	Fail
a Hopp til hovedinnhol…	1.16:1	4.5:1	#000000	#101528	Fail
a English	5.92:1	4.5:1	#000000	#888888	Pass
p Noen informasjonskap…	5.92:1	4.5:1	#000000	#888888	Pass
button Godta	5.92:1	4.5:1	#000000	#888888	Pass
button Avslå	5.92:1	4.5:1	#000000	#888888	Pass
a Detaljer for informa…	5.92:1	4.5:1	#000000	#888888	Pass
a UiO	5.92:1	4.5:1	#000000	#888888	Pass
a Universitetet i Oslo	5.92:1	4.5:1	#000000	#888888	Pass
span Meny	5.92:1	4.5:1	#000000	#888888	Pass
a For ansatte	5.92:1	4.5:1	#000000	#888888	Pass
a Mine studier	5.92:1	4.5:1	#000000	#888888	Pass
label Søk i nettsidene ti…	5.92:1	4.5:1	#000000	#888888	Pass
button Søk	5.92:1	4.5:1	#000000	#888888	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.

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

Heading Hierarchy

12 headings

PASS

12 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Dette nettstedet bruker informasjonskapsler
H1 Forsiden duplicate H1
H2 Forskningsnytt
H2 Arrangementer
H2 Aktuelt om UiO
H2 UiOs podkaster
H2 Klima miljø og bærekraft
H2 Våre allianser
H2 UiO i sosiale medier
H2 Kontakt
H2 Om nettstedet
H2 Ansvarlig for denne siden

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

All 13 images OK

PASS

All 13 images OK

1 decorative image(s) correctly marked

12 image(s) with good alt text

13 images 12 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

1 issue(s) across 74 links and 4 buttons

PASS

1 issue(s) across 74 links and 4 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.uio.no/om/aktuelt/universitetsplassen/aulaen/arrangementer/konser…

73 link(s) with descriptive text

74 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.uio.no/om/aktuelt/universite…	(empty)	empty	Add link text or aria-label

77 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.uio.no/om/aktuelt/universitetsplassen/aulaen/arrangementer/konser…

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

A+

Lighthouse Accessibility Audits

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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

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

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