Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 5 REVIEW 4 FIX

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

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

Form Accessibility

Action

4 of 10 controls have issues

REVIEW

4 of 10 controls have issues

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

6 control(s) properly labeled

10 controls

6 labeled

0 placeholder only

4 unlabeled

Control	Type	Label	Method
#CybotCookiebotDialogBodyLevelButtonNecessary	checkbox	Nödvändig	for/id
#CybotCookiebotDialogBodyLevelButtonPreferences	checkbox	Inställningar	for/id
#CybotCookiebotDialogBodyLevelButtonStatistics	checkbox	Statistik	for/id
#CybotCookiebotDialogBodyLevelButtonMarketing	checkbox	Marknadsföring	for/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformation	checkbox	Sälj eller dela inte mina personuppgifter	for/id
#s	text	Search	aria-label
#CybotCookiebotDialogBodyLevelButtonStatisticsInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonMarketingInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonNecessaryInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonPreferencesInline	checkbox	(none)	none

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

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

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogPoweredbyCybot">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavDetails">

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAdSettings">

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAbout">

Mobile-Readable Font Sizes

Action

70% of visible text renders at >= 12 CSS px (18 below threshold)

REVIEW

70% of visible text renders at >= 12 CSS px (18 below threshold)

18 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 11.5px ("Google Meet | 10:00"); <span> 11.5px ("Gå med"); <p> 11.5px ("Google Meet | 13.00 – 13.30"); <span> 11.5px ("Gå med"); <span> 11.5px ("Live").

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 Sidan finns inte - Sitea ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Landmark Structure

14 landmarks

PASS

14 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Heading Hierarchy

22 headings

PASS

22 headings

Single H1 present

H1 Marknadsföring och webbsom driver fler kunder till dig
H2 Allt vi gör för att dinmarknadsföring ska funka
H3 Synlighet på Google och i AI
H3 Annonser som betalar sig
H3 Ny hemsida som skapar kunder
H3 Rätt budskap till rätt person
H3 Vi blir ditt marknadsteam
H2 Så skapar vi resultat
H3 Analysera nuläge
H3 Identifiera framgångsfaktorer
H3 Optimera annonsering och webb
H3 Utvärdera och förfina
H2 En hemsida till fast pris, byggd för att öka din konvertering
H2 Spetskompetens inom marknadsföring som driver kunder till ditt företag
H2 Så arbetar vitillsammans med dig
H2 Hemsida tillfast pris
H3 Hemsida Basic
H3 Hemsida Pro
H3 Hemsida Growth
H2 Guider som ger dig verktyg
H2 Boosta er digitalanärvaro idag.
H3 Översikt

A+

Heading Text Quality

All 22 heading(s) have substantive, well-formed text

PASS

All 22 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 113 images OK

PASS

All 113 images OK

113 image(s) with good alt text

113 images 113 good alt text

All images have appropriate alt text.

Link & Button Quality

253 links, 15 buttons — all OK

PASS

253 links, 15 buttons — all OK

12 link(s) open in new tab without warning

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

Got: https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.cookiebot.com/goto/privacy-policy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://www.cookiebot.com; https://www.sitea.se/; https://www.sitea.se/; https://www.sitea.se/; https://www.sitea.se/ (+2 more)

241 link(s) with descriptive text

253 links

0 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cookiebot.com/en/what-is-beh…	Cookiebot av Usercentrics - ö…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com/goto/privacy-p…	Läs mer om den här leverant�…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Läs mer om den här leverant�…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Läs mer om den här leverant�…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Läs mer om den här leverant�…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com	Cookiebot	new tab	Add '(opens in new tab)' to text
https://www.sitea.se/	Promexa	new tab	Add '(opens in new tab)' to text
https://www.sitea.se/	ShapeBy	new tab	Add '(opens in new tab)' to text
https://www.sitea.se/	Promexa	new tab	Add '(opens in new tab)' to text
https://www.sitea.se/	ShapeBy	new tab	Add '(opens in new tab)' to text
https://www.google.com/maps/search/?api=…	Sitea	new tab	Add '(opens in new tab)' to text
https://www.trustindex.io/?a=sys&c=wp-ve…	Läs mer	new tab	Add '(opens in new tab)' to text

256 links and buttons have descriptive text

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

https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.cookiebot.com/goto/privacy-policy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://business.safety.google/privacy/; https://www.cookiebot.com; https://www.sitea.se/; https://www.sitea.se/; https://www.sitea.se/; https://www.sitea.se/ (+2 more)

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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "s" should use type="search" (currently type="text")

Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

10 form control(s) checked, no input-semantic issues

PASS

10 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "sv-SE"

PASS

Lang attribute set to "sv-SE"

<html lang="sv-SE"> is set and valid

Got: sv-SE

A+

Iframe Accessibility

All 2 iframe(s) have descriptive titles

PASS

All 2 iframe(s) have descriptive titles

All 2 iframe(s) have title attributes

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Marknadsföring och …	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h1 som driver fler kund…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 Allt vi gör för at…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 marknadsföring ska …	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 Så skapar vi result…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 En hemsida till fast…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 Spetskompetens inom …	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 Så arbetar vi	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 tillsammans med dig	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 Hemsida till	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 Guider som ger dig v…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 Boosta er digitala	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h2 närvaro idag.	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h3 Synlighet på Google…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h3 Annonser som betalar…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h3 Ny hemsida som skapa…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h3 Rätt budskap till r…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h3 Vi blir ditt marknad…	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h3 Analysera nuläge	17.05:1	3.0:1	#000000	#E8E7EA	Pass
h3 Identifiera framgån…	17.05:1	3.0:1	#000000	#E8E7EA	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.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 29 passed

PASS

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
4,7/5 Betyg på Google `div.sfp-hf-mockup > div.sfp-hf-left-col > div.sfp-hf-rating-badge > span.sfp-hf-rating-text`
Kundtillväxt `div.sfp-hf-chart-card > div.sfp-hf-chart-top > div > span.sfp-hf-chart-label`
Live `div.sfp-hf-chart > div.sfp-hf-chart-card > div.sfp-hf-chart-top > span.sfp-hf-chart-badge`
Mar `div.sfp-hf-chart > div.sfp-hf-chart-card > div.sfp-hf-chart-months > span`
Apr `div.sfp-hf-chart > div.sfp-hf-chart-card > div.sfp-hf-chart-months > span`
Maj `div.sfp-hf-chart > div.sfp-hf-chart-card > div.sfp-hf-chart-months > span`
Jun `div.sfp-hf-chart > div.sfp-hf-chart-card > div.sfp-hf-chart-months > span`
Jul `div.sfp-hf-chart > div.sfp-hf-chart-card > div.sfp-hf-chart-months > span`
Aug `div.sfp-hf-chart > div.sfp-hf-chart-card > div.sfp-hf-chart-months > span`
Besökare `div.sfp-hf-chart-card > div.sfp-hf-chart-legend > div.sfp-hf-chart-legend-item > span`
Konverteringar `div.sfp-hf-chart-card > div.sfp-hf-chart-legend > div.sfp-hf-chart-legend-item > span`
Leads/månad `div.sfp-hf-chart-card > div.sfp-hf-chart-legend > div.sfp-hf-chart-legend-item > span`
Vi sköter det tekniska och krångliga, så att du kan fokusera på din verksamhet.… `section.sfp-hf-features-section > div.sfp-hf-features-panel > div.sfp-hf-features-header > p.sfp-hf-features-sub`
Vi testar oss fram och justerar budgeten löpande i Google och Meta, så pengarna… `div.sfp-hf-features-panel > div.sfp-hf-features-scroll > a.sfp-hf-feature-card > p.sfp-hf-feature-desc`
Fyra steg som säkerställer att varje krona och varje timme går till det som fak… `div.wpb_wrapper > section.sfp-hf-process-section > div.sfp-hf-process-header > p.sfp-hf-process-sub`
Vi kartlägger nuvarande trafik, annonser, konvertering och konkurrenter för att… `section.sfp-hf-process-section > div.sfp-hf-process-timeline > div.sfp-hf-process-step > p.sfp-hf-process-step-desc`
Vi pekar ut vilka kanaler, budskap och sidor som faktiskt driver resultat för j… `section.sfp-hf-process-section > div.sfp-hf-process-timeline > div.sfp-hf-process-step > p.sfp-hf-process-step-desc`
Vi finjusterar kampanjer, landningssidor och sajtstruktur löpande utifrån vad s… `section.sfp-hf-process-section > div.sfp-hf-process-timeline > div.sfp-hf-process-step > p.sfp-hf-process-step-desc`
Vi följer upp resultatet, drar lärdomar och justerar strategin för fortsatt til… `section.sfp-hf-process-section > div.sfp-hf-process-timeline > div.sfp-hf-process-step > p.sfp-hf-process-step-desc`
Ingen gissningslek på slutnotan. Du får en modern, snabb hemsida med design, st… `section.sfp-web-section > div.sfp-web-grid > div.sfp-web-text > p.sfp-web-desc`
Pris från `div.sfp-web-text > div.sfp-web-price-row > div.sfp-web-price > span.sfp-web-price-label`
Vi kombinerar SEO, Google Ads och sociala medier med djup branschkunskap för at… `section.sfp-web-section > div.sfp-web-grid > div.sfp-web-text > p.sfp-web-desc`
Pris från `div.sfp-web-text > div.sfp-web-price-row > div.sfp-web-price > span.sfp-web-price-label`
Lär dig mer om SEO, Google Ads och digital marknadsföring. Kostnadsfria guider … `section.sfp-section > div.sfp-section-header > div > p.sfp-section-sub`
Förstå hur sökmotoroptimering fungerar och vad du behöver göra för att synas hö… `div.sfp-guides-scroll > a.sfp-guide-card > div.sfp-guide-body > p.sfp-guide-desc`
GOOGLE ADS `div.sfp-guides-scroll > a.sfp-guide-card > div.sfp-guide-img > span.sfp-guide-cat-badge`
Lär dig grunderna i betald sökning och hur du når rätt kunder i rätt ögonblick. `div.sfp-guides-scroll > a.sfp-guide-card > div.sfp-guide-body > p.sfp-guide-desc`
Swipa för att läsa fler guider `div.wpb_raw_code > div.wpb_wrapper > section.sfp-section > div.sfp-scroll-hint`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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.

○Image elements do not have `[alt]` attributes that are redundant text.

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