Skip to content
https://bodonu.no

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
82
GRADE
B
FIX
3
REVIEW
6
PASS
15
INFO
0
Checks
24
15 PASS 6 REVIEW 3 FIX
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: #dd1c1a
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.

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::
1 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 1 <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.
B
Heading Hierarchy
66 headings
REVIEW
66 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Aktuelle temaer
  • H3 Papiravisen
  • H2 Abonnement
  • H2 UNG 15-20
  • H2 Tips oss!
  • H2 Kundeservice
  • H2 Annonsering
  • H2 Del med oss
  • H2 Følg oss
  • H2 A til Å
  • H3 Utvider besøket i Bodø
  • H3 Ble frastjålet sykkelen - kommer seg ikke på ferie
  • H3 Elsparkesyklist i ulykke
  • H3 Tvunget til å flytte seg: – Trakassert i 45 minutter
  • H3 Bodø kommune til Statsforvalteren: – Sterkt beklagelig
  • H3 Rampen satser skjorta: – Bodø er rett og slett Norge i miniatyr
  • H3 Tiltalt for grov mishandling i nære relasjoner
  • H3 Reduserer straffen for overgrepsdømt: Frikjent for voldtekt av samboer
  • H3 Nå har du muligheten til å overnatte på toppen av Bodø
  • H3 – Min mor sier det så fint
  • H2 Utvider besøket i Bodø
  • H3 Kunstgress-avsløringen:
  • H2 Bodø kommune erkjenner: –⁠ Sterkt beklagelig
  • H2 Ble frastjålet sykkelen - kommer seg ikke på ferie
  • H2 Elsparkesyklist i ulykke
  • H2 Tvunget til å flytte seg: –⁠ Trakassert i 45 minutter
  • H2 Rampen satser skjorta: –⁠ Bodø er rett og slett Norge i miniatyr
  • H2 Se de siste dødsannonsene
  • H2 Tiltalt for grov mishandling i nære relasjoner
  • H2 Reduserer straffen for overgrepsdømt: Frikjent for voldtekt av samboer
  • H2 Nå har du muligheten til å overnatte på toppen av Bodø
  • H2 HRS-avsløringene
  • H2 Historisk 17. mai-smell for nordmenn
  • H2 Ordfører om spionpågripelsen i Bodø: –⁠ Bekymringsverdig, men ikke overraskende
  • H3 Bekrefter til Bodø Nu:
  • H2 Spionsiktet kineser skal ha hatt tilhold i bunker i Bodø
  • H2 Svarer om SAR Queen-striden
  • H2 Bjørn Erik Lian blir ny konsernsjef
  • H2 30 vil ha jobbene i NRK Nordland
  • H2 Avgjørende dager for Glimt – kan få gavepakke i ny Champions League-jakt
  • H2 Forsvaret ønsker tettere samarbeid med Øvelse Nord
  • H2 Kunstgress-skandalen:
  • H3 Bodøs hemmelige underverden:
  • H2 –⁠ Hit ned slipper nesten ingen inn
  • H2 Kommer til Bodø
  • H2 Slik snur Glimt-akademiet på flisa: Henter engelske toppklubber til Bodø
  • H2 Asfaltering i Bodø kan gi ventetid og støy
  • H3 Byttet ut storbyen med barndomshjemmet i Bodø, men én ting overrasker henne:
  • H2 –⁠ Føles ofte litt internt
  • H2 Ansatt som ny rektor
  • H3 Industri og produksjon
  • H3 Forandring fryder!
  • H4 Se alle ledige stillinger her
  • H2 Mon Ami om suksessen: –⁠ Egentlig et resultat av at man har jobbet hardt og disiplinert
  • H2 Havnet midt i kaoset: –⁠ Langt over grensa
  • H2 Knutsen beklager dytt
  • H2 17. mai i Bodø
  • H3 Bodø-ambassadør Alexander Skadberg 33 år
  • H2 –⁠ Ikke gitt opp håpet om at det finnes muligheter der ute for absolutt alle
  • H2 Se bildene fra borgertoget
  • H2 Her hylles Bodø/Glimt
  • H2 Halvdan Sivertsen og Terje Nohr
  • H2 Skoletog og show
  • H2 Se bildene fra barnehagetoget
  • H2 Sang, dans og drill
  • H2 Gratulerer med dagen!

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Iframe Accessibility
Action
4/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
4/4 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="javascript:window[\"contents\"]")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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 Bodø Nu Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Aktuelle temaer3.00:13.0:1
#000000
#595959
Pass
h2 Abonnement3.00:13.0:1
#000000
#595959
Pass
h2 UNG 15-203.00:13.0:1
#000000
#595959
Pass
h2 Tips oss!3.00:13.0:1
#000000
#595959
Pass
h2 Kundeservice3.00:13.0:1
#000000
#595959
Pass
h2 Annonsering3.00:13.0:1
#000000
#595959
Pass
h2 Del med oss3.00:13.0:1
#000000
#595959
Pass
h2 Følg oss3.00:13.0:1
#000000
#595959
Pass
h2 A til Å3.00:13.0:1
#000000
#595959
Pass
h2 HRS-avsløringene3.00:13.0:1
#000000
#595959
Pass
h2 Kunstgress-skandalen…3.00:13.0:1
#000000
#595959
Pass
h2 17. mai i Bodø3.00:13.0:1
#000000
#595959
Pass
h3 Papiravisen3.00:13.0:1
#000000
#595959
Pass
h3 Utvider besøket i B…3.00:13.0:1
#000000
#595959
Pass
h3 Ble frastjålet sykk…3.00:13.0:1
#000000
#595959
Pass
h3 Elsparkesyklist i ul…3.00:13.0:1
#000000
#595959
Pass
h3 Tvunget til å flytt…3.00:13.0:1
#000000
#595959
Pass
h3 Bodø kommune til St…3.00:13.0:1
#000000
#595959
Pass
h3 Rampen satser skjort…3.00:13.0:1
#000000
#595959
Pass
h3 Tiltalt for grov mis…3.00:13.0:1
#000000
#595959
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
Landmark Structure
20 landmarks
PASS
20 landmarks
Info::
<main> landmark present
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.
Page Structure — as a screen reader sees it
BANNER header NAV "Hovedmeny" 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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
All 50 images OK
PASS
All 50 images OK
Info::
46 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
50 images 4 good alt text 46 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 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::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#globalSearchFieldsearchSøk i hele avisenfor/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+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "no"
PASS
Lang attribute set to "no"
Info::
<html lang="no"> is set and valid
Got: no
A+
Tabindex Anti-Patterns
38 explicit tabindex attribute(s) checked, no anti-patterns
PASS
38 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Mobile-Readable Font Sizes
All 68 visible text node(s) render at >= 12 CSS pixels
PASS
All 68 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Bodø Nu
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name Bodø Nu 192×192 icon 512×512 icon Start URL https://www.bodonu.no/?src=pwa Display Mode standalone
Name Bodø Nu Display Mode standalone Background Color #ffffff Icons 7 icon(s)
A
PWA Depth
3 PWA signal(s) surfaced
PASS
3 PWA signal(s) surfaced
Info::
Service worker registration detected
The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
A+
Mobile UX Depth
3 mobile-depth signal(s) detected
PASS
3 mobile-depth signal(s) detected
Info::
iOS smart-banner opt-in present (`apple-itunes-app`)
The page declares a companion iOS app via `<meta name="apple-itunes-app" content="app-id=...">`. iOS Safari shows a smart banner offering to open the page in the app, with an unobtrusive 'X' to dismiss. Recommended when you have a published companion app.
Info::
Android smart-banner opt-in present (`google-play-app`)
The page declares a companion Android app via `<meta name="google-play-app" content="app-id=...">` (or `google-play-id`). Combined with Chrome's intent: protocol or App Links, this lets supporting browsers offer to open the page in the app.
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 26 passed
PASS
93

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

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
optimus-element#art-3f22236e-2eaf-444b-8395-8c6f89b20444 > div > tivoli-realestatecarousel#EAad87 > iframe#eaframe optimus-element#art-3f22236e-2eaf-444b-8395-8c6f89b20444 > div > tivoli-realestatecarousel#EAad87 > iframe#eaframe

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.

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
Redaktørplakaten footer.brandheader-footer > ul > li > a
Personvernerklæring footer.brandheader-footer > ul > li > a

These items highlight common accessibility best practices.

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
Se ledige stillinger (425) div > tivoli-jobcarousel > div.ad-container > a.totalt_antall-a
Industri og produksjon Elektrikere Glomfjord 29.05.2026 div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.swiper-slide-a
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
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[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
`<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.
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
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