Skip to content
https://mikecrm.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 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>.
Warning::
No <nav> landmark found
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 header 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
Alt Text Quality
Action
41 of 75 images have issues
FIX
41 of 75 images have issues
Critical::
39 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
13 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
2 image(s) with generic alt text
Info::
34 image(s) with good alt text
75 images 34 good alt text 2 generic 39 missing
IssueCount
missing39 image(s)
generic2 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #263c59
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 ModePartial Dark Mode
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Favicon & Branding
15 icon(s) detected
REVIEW
15 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
title MikeCRM - Ein führender Dienst für Dat…
1.87:1
#000000
on
#263C59
needs 4.5:1 (normal text)
16px · top of page (header area)
p Scroll down to start your journey with M…
1.87:1
#000000
on
#263C59
needs 4.5:1 (normal text)
16px · top of page (header area)
p Scroll up to view Real-time Statistics
1.87:1
#000000
on
#263C59
needs 4.5:1 (normal text)
16px · top of page (header area)
span Capabilities
1.87:1
#000000
on
#263C59
needs 4.5:1 (normal text)
16px · top of page (header area)
i
1.87:1
#000000
on
#263C59
needs 4.5:1 (normal text)
16px · above the fold
div Products & Capabilities
1.87:1
#000000
on
#263C59
needs 4.5:1 (normal text)
16px · above the fold
span Create Forms
1.88:1
#000000
on
#273C59
needs 4.5:1 (normal text)
16px · above the fold
a Unlock the gate to informatization
1.88:1
#000000
on
#273C59
needs 4.5:1 (normal text)
16px · above the fold
span Manage Customers
1.88:1
#000000
on
#273C59
needs 4.5:1 (normal text)
16px · above the fold
a Expore Contacts
1.88:1
#000000
on
#273C59
needs 4.5:1 (normal text)
16px · above the fold
a How to continually develop the value of …
1.88:1
#000000
on
#273C59
needs 4.5:1 (normal text)
16px · above the fold
span Build a Membership System
1.88:1
#000000
on
#273C59
needs 4.5:1 (normal text)
16px · above the fold
a Explore Membership Management Platform
1.88:1
#000000
on
#273C59
needs 4.5:1 (normal text)
16px · above the fold
span Open an Online Store
1.47:1
#000000
on
#1E2B3E
needs 4.5:1 (normal text)
16px · mid-page
a Explore MikeCRM integrated payment solut…
1.47:1
#000000
on
#1E2B3E
needs 4.5:1 (normal text)
16px · mid-page
span Send Emails and Text Messages
1.47:1
#000000
on
#1E2B3E
needs 4.5:1 (normal text)
16px · mid-page
a What can I do with Mails?
1.47:1
#000000
on
#1E2B3E
needs 4.5:1 (normal text)
16px · mid-page
a Explore the benefits of MikeCRM Messages
1.47:1
#000000
on
#1E2B3E
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title MikeCRM - Ein führe…1.87:14.5:1
#000000
#263C59
Fail
p Scroll down to start…1.87:14.5:1
#000000
#263C59
Fail
p Scroll up to view Re…1.87:14.5:1
#000000
#263C59
Fail
span Capabilities1.87:14.5:1
#000000
#263C59
Fail
i 1.87:14.5:1
#000000
#263C59
Fail
div Products & Capabilit…1.87:14.5:1
#000000
#263C59
Fail
span Create Forms1.88:14.5:1
#000000
#273C59
Fail
a Unlock the gate to i…1.88:14.5:1
#000000
#273C59
Fail
span Manage Customers1.88:14.5:1
#000000
#273C59
Fail
a Expore Contacts1.88:14.5:1
#000000
#273C59
Fail
a How to continually d…1.88:14.5:1
#000000
#273C59
Fail
span Build a Membership S…1.88:14.5:1
#000000
#273C59
Fail
a Explore Membership M…1.88:14.5:1
#000000
#273C59
Fail
span Open an Online Store1.47:14.5:1
#000000
#1E2B3E
Fail
a Explore MikeCRM inte…1.47:14.5:1
#000000
#1E2B3E
Fail
span Send Emails and Text…1.47:14.5:1
#000000
#1E2B3E
Fail
a What can I do with M…1.47:14.5:1
#000000
#1E2B3E
Fail
a Explore the benefits…1.47:14.5:1
#000000
#1E2B3E
Fail
div Solutions by scenari…20.48:14.5:1
#000000
#FCFCFD
Pass
span Reservation Manageme…20.48:14.5:1
#000000
#FCFCFD
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.

C
Lighthouse Accessibility Audits
Action
Score 76/100 — 3 failing, 16 passed
REVIEW
76

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
logo div.idx_main > div.idx_content_wrapper > header.idx_header > nav.idx_content

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.idx_mpcInfo > div.idx_mpcDetail > div.idx_mpcdFeatures > img.imx_featureIcon div.idx_mpcInfo > div.idx_mpcDetail > div.idx_mpcdFeatures > img.imx_featureIcon
div.idx_mpcInfo > div.idx_mpcDetail > div.idx_mpcdFeatures > img.imx_featureIcon div.idx_mpcInfo > div.idx_mpcDetail > div.idx_mpcdFeatures > img.imx_featureIcon
div.idx_mpcInfo > div.idx_mpcDetail > div.idx_mpcdFeatures > img.imx_featureIcon div.idx_mpcInfo > div.idx_mpcDetail > div.idx_mpcdFeatures > img.imx_featureIcon
div.idx_securityContent > div.idx_techContent > div.idx_techInfo > img.idx_tiLogo div.idx_securityContent > div.idx_techContent > div.idx_techInfo > img.idx_tiLogo
div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon
div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon
div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon
div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon
div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon
div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon div.idx_psContent > div.idx_psFeatures > div.idx_psfItem > img.idx_psfiIcon
div.mg-scroll-field > div.idx_screen > div.idx_globalMap > img.idx_global_map div.mg-scroll-field > div.idx_screen > div.idx_globalMap > img.idx_global_map
div.idx_footer > div.idx_content > div.if_brand > img.if_logo div.idx_footer > div.idx_content > div.if_brand > img.if_logo
div.if_productMatrix > div.if_productItem > a.if_piBrand > img.if_piLogo div.if_productMatrix > div.if_productItem > a.if_piBrand > img.if_piLogo
div.if_productMatrix > div.if_productItem > a.if_piBrand > img.if_piLogo div.if_productMatrix > div.if_productItem > a.if_piBrand > img.if_piLogo
div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo
div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo
div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo
div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo
div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo div.if_safe > div.if_certificates > div.if_certItem > img.if_ciLogo
div.if_certificates > div.if_certItem > div.if_ciInfo > img.if_ciOrg div.if_certificates > div.if_certItem > div.if_ciInfo > img.if_ciOrg
div.idx_footer > div.idx_content > div.if_copyright > img.if_sloganR div.idx_footer > div.idx_content > div.if_copyright > img.if_sloganR

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.

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#viewport head > meta#viewport

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●Background and foreground colors have a sufficient contrast ratio
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●The page contains a heading, skip link, or landmark region
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○`<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
○Heading elements appear in a sequentially-descending order
○`<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
○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.
○`[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.
○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.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback