Skip to content
https://mobirise.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 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
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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.
A+
Heading Hierarchy
32 headings
PASS
32 headings
Info::
Single H1 present
  • H1 FREE WEBSITE BUILDER SOFTWARE
  • H2 It's easier with AI: Generate your website
  • H2 Make a website without coding
  • H2 Customize your site visually
  • H2 Edit locally and publish wherever
  • H2 Download Free Website Builder Software
  • H2 Multiple website templates
  • H2 Start selling online
  • H2 Get social
  • H2 Build a mobile-friendly site
  • H2 View and edit website code
  • H2 More features
  • H3 Custom domain
  • H3 Galleries
  • H3 Image sliders
  • H3 Shop blocks
  • H3 Blog features
  • H3 Popup builder
  • H3 Social feed
  • H3 Image editor
  • H3 Popup Chat
  • H3 Shopping Cart
  • H3 Bootstrap builder
  • H3 Form builder
  • H2 Create your website with Mobirise
  • H2 What experts say
  • H2 Made with Mobirise No Code
  • H2 Join 2,500,000+ happy users!
  • H2 Download free Mobirise now
  • H2 View in Action
  • H2 Got questions?
  • H2 Follow us
A
Alt Text Quality
2 of 57 images have issues
PASS
2 of 57 images have issues
Warning::
2 image(s) with generic alt text
Info::
5 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
57 images 50 good alt text 5 decorative 2 generic
IssueCount
generic2 image(s)
A
Form Accessibility
1 of 12 controls have issues
PASS
1 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="checkbox" id="menu-toggle">
Info::
11 control(s) properly labeled
12 controls
11 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#rd1radioHow to make a website?for/id
#rd2radioHow do I publish a site online?for/id
#rd3radioCan I download a website made in Mobirise?for/id
#rd4radioIs Mobirise free?for/id
#rd5radioCan I edit my existing site in Mobirise?for/id
#rd6radioIs Mobirise easy if I don't know how to code?for/id
#rd7radioCan I use Mobirise offline without internet?for/id
#rd8radioCan I create and edit websites online without downloading the app?for/id
#rd9radioWhat is Mobirise AI?for/id
#rd10radioHow to generate websites with Mobirise AI?for/id
#rd11radioCan I export the code of a website?for/id
#menu-togglecheckbox(none)none

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

<input type="checkbox" id="menu-toggle">

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+
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 FREE WEBSITE BUILDER…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 It's easier with AI:…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Make a website witho…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Customize your site …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Edit locally and pub…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Download Free Websit…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Multiple website tem…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Start selling online21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get social21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Build a mobile-frien…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 View and edit websit…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 More features21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Create your website …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What experts say21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Made with Mobirise N…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join 2,500,000+ happ…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Download free Mobiri…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 View in Action21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Got questions?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Follow us21.00:13.0:1
#000000
#FFFFFF
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, 22 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
Try AI website builder software div.col-12 > div > div.mbr-section-btn > a.btn
For Win div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
For Mac div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
For Win div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
For Mac div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
For Win div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
For Mac 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
premium div.row > div.title > p.mbr-section-subtitle > a
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
For Win div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
For Mac div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
Learn how div.col-12 > div.text-wrapper > div.mbr-section-btn > a.btn
Download for Win 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

These are opportunities to improve the legibility of your content.

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 html

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
●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
●`<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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[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
○Buttons have an accessible name
○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
○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
○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