Skip to content
https://mobiri.se

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-ljtufz
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://mobiri.se/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://mobiri.se/manifest.json

Manifest contains invalid JSON.

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::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <textarea id="aiPromt">; <textarea id="aiPromt">; <textarea id="aiPromt">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
#aiPromttextarea(What your site will be about? Write in any language.)placeholder only
#aiPromttextarea(What your site will be about? Write in any language.)placeholder only
#aiPromttextarea(What your site will be about? Write in any language.)placeholder only

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

<textarea id="aiPromt">; <textarea id="aiPromt">; <textarea id="aiPromt">

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

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 7 failing, 19 passed
REVIEW
77

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
Download for Windows div.row > div.content-wrap > div.mbr-section-btn > a.btn
Download for Mac div.row > div.content-wrap > div.mbr-section-btn > a.btn
✨✨Desigh with AI! div.modal-body > form > div.mbr-section-btn > a.btn
✨Build website with AI! div.col-12 > div.items-wrapper > div.mbr-section-btn > a.btn
View demo div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
View extensions div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
✨Generate website with AI! div.modal-body > form > div.mbr-section-btn > a.btn
Learn how div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
Download for Windows div.row > div.content-wrap > div.mbr-section-btn > a.btn
Download for Mac div.row > div.content-wrap > div.mbr-section-btn > a.btn
Download for Windows div.row > div.col-md-12 > div.mbr-section-btn > a.btn
Download for Mac div.row > div.col-md-12 > div.mbr-section-btn > a.btn
For Windows (XP+) div.row > div.content-wrap > div.mbr-section-btn > a.btn
For Mac (OS X 10.7+) div.row > div.content-wrap > div.mbr-section-btn > a.btn
Download for Windows div.row > div.content-wrap > div.mbr-section-btn > a.btn
Download for Mac div.row > div.content-wrap > div.mbr-section-btn > a.btn

These are opportunities to improve the legibility of your content.

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
div.row > div.col-12 > div.video-wrapper > iframe.mbr-embedded-video div.row > div.col-12 > div.video-wrapper > iframe.mbr-embedded-video

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
div.container-fluid > div.navbar-brand > span.navbar-logo > a div.container-fluid > div.navbar-brand > span.navbar-logo > 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
View in Action div.container-fluid > div.row > div.mbr-section-head > h4.mbr-section-title

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.mobile html.mobile

These are opportunities to improve the interpretation of your content by users in different locales.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mobirise AI This software employs advanced AI to create highly engaging website… div.row > div.col-md-10 > div.text-box > ul

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.mobile html.mobile

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>`
●`[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
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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 a valid value for its `[lang]` attribute
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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.
○Elements with visible text labels have matching accessible names.
A
Heading Hierarchy
21 headings, 1 skip(s)
PASS
21 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Website design software
  • H2 Create websites on PC or Mac. Publish anywhere.
  • H2 Made with Website design software. No Code
  • H2 Key Website design software features
  • H2 Create your website now
  • H2 User Reviews
  • H2 Download free app now
  • H4 View in Action skipped
  • H5 Watch the video below to gain insights into creating an appealing website with the app. This guide offers practical tips and techniques to effectively use design elements, ensuring your site captures
  • H3 FAQ
  • H3 What is website design software?
  • H3 How to use website design software?
  • H3 Can I create an online store with website design software?
  • H3 Is it easy to customize websites with design software?
  • H3 How can I optimize my website for search engines?
  • H3 Can I integrate AI tools with website design software?
  • H3 What are the benefits of using Mobirise AI for website design?
  • H3 Does website design software provide hosting services?
  • H3 What is the best website design software available?
  • H3 Choosing the right Website design software
  • H2 Create website now!

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

A+
Alt Text Quality
All 34 images OK
PASS
All 34 images OK
Info::
1 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
34 images 33 good alt text 1 decorative
All images have appropriate alt text.
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 Website design softw…15.13:13.0:1
#000000
#F5D0ED
Pass
h2 Create websites on P…15.13:13.0:1
#000000
#F5D0ED
Pass
h2 Made with Website de…15.13:13.0:1
#000000
#F5D0ED
Pass
h2 Key Website design s…8.19:13.0:1
#3A3A3A
#F5D0ED
Pass
h2 Create your website …15.13:13.0:1
#000000
#F5D0ED
Pass
h2 User Reviews8.19:13.0:1
#3A3A3A
#F5D0ED
Pass
h2 Download free app no…8.19:13.0:1
#3A3A3A
#F5D0ED
Pass
h2 Create website now!15.13:13.0:1
#000000
#F5D0ED
Pass
title Website design softw…14.24:14.5:1
#000000
#DFCDF9
Pass
a Ai Business Website …14.46:14.5:1
#000000
#E7CDF6
Pass
a Ai For Websites14.71:14.5:1
#000000
#EDCEF2
Pass
a Free Ai Website Gene…14.95:14.5:1
#000000
#F2CFEF
Pass
a Ai Html Generator15.12:14.5:1
#000000
#F5D0EC
Pass
a Web Design Software15.35:14.5:1
#000000
#F7D2E9
Pass
a Ai Website Editor15.60:14.5:1
#000000
#F9D4E7
Pass
a Web Development Soft…15.95:14.5:1
#000000
#FAD7E8
Pass
a Ai Website Software16.28:14.5:1
#000000
#FADAEA
Pass
a Real Time Html Edito…16.50:14.5:1
#000000
#FADCEB
Pass
a Ai Website Design Bu…16.84:14.5:1
#000000
#FADFED
Pass
a Easy Ai Website Buil…17.07:14.5:1
#000000
#FAE1EE
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback