Skip to content
https://loopia.se

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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
Alt Text Quality
3 of 46 images have issues
REVIEW
3 of 46 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
42 image(s) with good alt text
46 images 42 good alt text 1 decorative 1 generic 2 missing
IssueCount
missing2 image(s)
generic1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Form Accessibility
2 of 12 controls have issues
REVIEW
2 of 12 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">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="domainnames" id="c_domainnames">
Info::
10 control(s) properly labeled
12 controls
10 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#usernametextAnvändarnamnfor/id
#passwordpasswordLösenordfor/id
inputsubmitSök domänaria-label
#pbox-toggle--355484844checkboxVisa merfor/id
#pbox-toggle--355484845checkboxVisa merfor/id
#pbox-toggle--355484846checkboxVisa merfor/id
#iub-toggle-id-1checkboxNödvändigafor/id
#iub-toggle-id-3checkboxUpplevelsefor/id
#iub-toggle-id-4checkboxMätningfor/id
#iub-toggle-id-mktcheckboxMarknadsföringfor/id
#c_domainnamestext(Sök önskad domän)placeholder only
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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="domainnames" id="c_domainnames">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Ajdå, sidan finns inte ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
8 icon(s) detected
REVIEW
8 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
5 landmarks
PASS
5 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 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 Hierarchy
34 headings
PASS
34 headings
Info::
Single H1 present
  • H1 Din egen plats på nätet för bara 911,25 kr
  • H2 Bygg din hemsida hos Loopia snabbt och enkelt
  • H3 Hitta ditt unika domännamn
  • H3 Välj det webbhotellspaket som passar dig
  • H3 Skapa hemsida enkelt med WordPress
  • H2 Vilket webbhotellspaket passar dig bäst?
  • H3 Företagspaketet
  • H3 Privatpaketet
  • H3 Företagspaketet Plus
  • H2 AI-verktygen du behöver för din hemsida
  • H3 800 000 +
  • H3 4 000 +
  • H3 300 000 +
  • H3 290 000 +
  • H2 Allt du behöver för attnå ut med din idé
  • H3 E-handel
  • H3 E-post
  • H3 Sitebuilder
  • H3 Flytta till Loopia
  • H3 WordPress
  • H2 Vanliga frågor
  • H3 Vad är en domän och hur registrerar jag en?
  • H3 Varför behöver jag ett webbhotell?
  • H3 Hur skapar jag en egen e-postadress?
  • H3 Hemsida med WordPress eller Sitebuilder, vilket ska jag välja?
  • H3 Hur skapar jag en egen hemsida?
  • H3 Hur skapar jag en egen webbutik?
  • H2 Vi finns här för dig!
  • H3 Om
  • H3 Kontakt/Support
  • H3 Återförsäljare
  • H3 Alla tjänster
  • H3 Språk
  • H3 Följ oss
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)
ElementRatioRequiredFGBGResult
h1 Din egen plats på n…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 snabbt och enkelt20.47:13.0:1
#000000
#FCFCFC
Pass
h2 passar dig bäst?20.47:13.0:1
#000000
#FCFCFC
Pass
h2 AI-verktygen du beh…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 nå ut med din idé20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Vanliga frågor20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Vi finns här för d…20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Hitta ditt unika dom…20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Välj det webbhotell…20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Skapa hemsida enkelt…20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Företagspaketet20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Privatpaketet20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Företagspaketet Plu…20.47:13.0:1
#000000
#FCFCFC
Pass
h3 800 000 +20.47:13.0:1
#000000
#FCFCFC
Pass
h3 4 000 +20.47:13.0:1
#000000
#FCFCFC
Pass
h3 300 000 +20.47:13.0:1
#000000
#FCFCFC
Pass
h3 290 000 +20.47:13.0:1
#000000
#FCFCFC
Pass
h3 E-handel20.47:13.0:1
#000000
#FCFCFC
Pass
h3 E-post20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Sitebuilder20.47:13.0:1
#000000
#FCFCFC
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
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 31 passed
PASS
94

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
29 KR div.col-12 > span.domain-price > button.collapsed > span.regular-price-strikethrough
29 span.domain-price > button.collapsed > span.regular-price-strikethrough > span.without_tax

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Webbmail div#login_box > ul.nav > li > a
Logga in div#login_box > ul.nav > li > a

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.

○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
●Input buttons have discernible text.
●Form elements have associated labels
●`[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
●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.
●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
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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 type="image">` elements have `[alt]` text
○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.
○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