Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 6 REVIEW 3 FIX

Link & Button Quality

Action

10 issue(s) across 136 links and 20 buttons

FIX

10 issue(s) across 136 links and 20 buttons

2 link(s) with no accessible text

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

Got: #; #

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://payment.schibsted.no/profile-pages?client_id=4ef1cfb0e962dd2e0d8d0000…; https://payment.schibsted.no/about/terms?locale=nb_NO; https://info.privacy.schibsted.com/no/schibsted-norge-personvernerklaering/

8 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button._button_6bkpv_2 (#320 on page); button._button_6bkpv_2 (#341 on page); button._button_6bkpv_2 (#383 on page); button._button_6bkpv_2 (#410 on page); button._button_6bkpv_2 (#443 on page); button._chevron_du0dc_24 (#856 on page); button._chevron_du0dc_24 (#859 on page); button._button_lgi46_1 (#1545 on page)

131 link(s) with descriptive text

136 links

2 empty

0 generic text

3 new tab

8 empty buttons

Element	Text	Issue	Suggested Fix
https://payment.schibsted.no/profile-pag…	Schibsted-konto	new tab	Add '(opens in new tab)' to text
https://payment.schibsted.no/about/terms…	Brukervilkår	new tab	Add '(opens in new tab)' to text
https://info.privacy.schibsted.com/no/sc…	Personvernerklæring	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://www.vg.no/nyheter/i/j03dg0/lambo…	Siste: Førerkortog bil beslag…	img no alt	Add alt attribute to the image
https://www.vg.no/nyheter/i/j0v62w/sveri…	Sverige: Normal anklagesfor å…	img no alt	Add alt attribute to the image
https://www.vg.no/nyheter/i/V6xRjr/kampe…	«Like alvorligsom 1973 og2022…	img no alt	Add alt attribute to the image
https://www.vg.no/sport/i/pBM67j/erling-…	Skjøt City tiltopps	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

143 links and buttons have descriptive text

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

#; #

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

Add '(opens in new tab)' to link text or aria-label.

https://payment.schibsted.no/profile-pages?client_id=4ef1cfb0e962dd2e0d8d0000…; https://payment.schibsted.no/about/terms?locale=nb_NO; https://info.privacy.schibsted.com/no/schibsted-norge-personvernerklaering/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button._button_6bkpv_2 (#320 on page); button._button_6bkpv_2 (#341 on page); button._button_6bkpv_2 (#383 on page); button._button_6bkpv_2 (#410 on page); button._button_6bkpv_2 (#443 on page); button._chevron_du0dc_24 (#856 on page); button._chevron_du0dc_24 (#859 on page); button._button_lgi46_1 (#1545 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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

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

12 landmarks

REVIEW

12 landmarks

<main> landmark present

7 <nav> landmark(s) found

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

Heading Hierarchy

Action

30 headings, 1 skip(s)

REVIEW

30 headings, 1 skip(s)

No H1 heading found

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

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Siste: Førerkortog bil beslaglagt
H2 Normal anklagesfor å utnytteunge ansatte
H2 «Like alvorligsom 1973 og2022 til sammen»
H2 Skjøt City tiltopps
H2 Korte videoer
H2 Siste nytt
H3 Frigir dødsårsaken til tenåringen funnet i D4vds bil
H3 Lamborghini-smell ved Tusenfryd: Kjørte rett i tunnelveggen
H3 Sverige: Normal anklages for å utnytte unge ansatte
H3 Mormonerkvinnene starter opp igjen – uten Taylor Frankie Paul
H3 Fotballfest krasjer med løpefest i Oslo
H3 Cup-exit for Rekdals Aalesund: – Elendig og svak omgang
H3 Darrell Sheets kjent fra «Lagerkrigen» er død
H3 Ellevilt semifinaledrama: Helmersen ble Glimt-helt etter 118 minutter
H3 Britisk røykforbud vekker sterke reaksjoner
H3 Datainnbrudd hos Rituals: Norge og Europa rammet
H3 Mann alvorlig skadet under oppussingsarbeid i Oslo
H3 Gjert Ingebrigtsen etter Slokvik-vraking: – Vi var litt, for å si det mildt, overrasket
H3 Alvorlig skadet i Pakistan – gjenkjent via nettet
H3 Stakk av fra politikontroll på Grünerløkka i Oslo
H3 Bekreftet: Chelsea sparker Liam Rosenior
H3 Influencer Camilla Lorentzen har født
H3 Reese Witherspoon forsvarer seg etter AI-storm
H3 Norsk 20-åring ble pågrepet i Nederland – nå er siktelsen utvidet
H3 Tre middager med torsk
H3 Branns europabakrus: – En stor mental belastning
H2 Les dagens Lunch
H2 Les dagens Pondus
H2 Les dagens Hjalmar
H4 Neste skipped

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Redaktøransvar ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Favicon & Branding

11 icon(s) detected

REVIEW

11 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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)

Element	Ratio	Required	FG	BG	Result
h2 Korte videoer	3.00:1	3.0:1	#000000	#595959	Pass
h2 Siste nytt	3.00:1	3.0:1	#000000	#595959	Pass
h2 Les dagens Lunch	3.00:1	3.0:1	#000000	#595959	Pass
h2 Les dagens Pondus	3.00:1	3.0:1	#000000	#595959	Pass
h2 Les dagens Hjalmar	3.00:1	3.0:1	#000000	#595959	Pass
h3 Frigir dødsårsaken…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Lamborghini-smell ve…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Sverige: Normal ankl…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Mormonerkvinnene sta…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Fotballfest krasjer …	3.00:1	3.0:1	#000000	#595959	Pass
h3 Cup-exit for Rekdals…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Darrell Sheets kjent…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Ellevilt semifinaled…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Britisk røykforbu…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Datainnbrudd hos Rit…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Mann alvorlig skadet…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Gjert Ingebrigtsen e…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Alvorlig skadet i Pa…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Stakk av fra politik…	3.00:1	3.0:1	#000000	#595959	Pass
h3 Bekreftet: Chelsea s…	3.00:1	3.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+

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

5 decorative image(s) correctly marked

3 image(s) with good alt text

8 images 3 good alt text 5 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	search	Søk	aria-label
q	search	Søk	aria-label

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: VG

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name VG ✓192×192 icon ✓512×512 icon ✓Start URL https://www.vg.no/?utm_source=pwa ✓Display Mode standalone ✓

Name VG Display Mode standalone Theme Color #dd0000 Background Color #ffffff Icons 5 icon(s)

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
Torsdag Rask Tradisjonell blomkålsuppe Tilberedningstid: 30 min. Lagret av 2.4K `ol._dishList_1chga_83 > li._listItemWrapper_1chga_118 > track-element > a._listItem_1chga_118`

○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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●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

○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

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

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

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