Skip to content
https://mn.co

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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
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.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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!) MAIN CONTENTINFO (missing!)

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

B
Heading Hierarchy
1 headings
REVIEW
1 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 (empty)

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Mighty Networks ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 5 failing, 20 passed
REVIEW
75

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#header > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div#header > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > button.sc-1gwlxsv-3

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.sc-fqt784-1 > div.sc-fqt784-2 > div.sc-fqt784-3 > input div.sc-fqt784-1 > div.sc-fqt784-2 > div.sc-fqt784-3 > input
div.sc-fqt784-1 > div.sc-fqt784-2 > div.sc-fqt784-3 > input div.sc-fqt784-1 > div.sc-fqt784-2 > div.sc-fqt784-3 > input
div.sc-fqt784-1 > div.sc-fqt784-2 > div.sc-fqt784-3 > input div.sc-fqt784-1 > div.sc-fqt784-2 > div.sc-fqt784-3 > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Launch Plan Scale Plan Growth Plan div.sc-fqt784-1 > div.sc-fqt784-2 > div.sc-fqt784-3 > select

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.sc-njky1n-0 > div#header > div.sc-1jwbzwh-0 > a.sc-j93fj5-1 div.sc-njky1n-0 > div#header > div.sc-1jwbzwh-0 > a.sc-j93fj5-1
div.sc-1cg52jg-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2 div.sc-1cg52jg-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2
div.sc-1cg52jg-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2 div.sc-1cg52jg-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2
div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > a.sc-j93fj5-2

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.

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
$500M div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
$48 div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
84% div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
60% div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
offer 2 months free div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
What's Selling Right Now div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
It's the Phones div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
Mighty Pro div.sc-1jwbzwh-0 > p.sc-2c48m4-0 > a.sc-1gwlxsv-1 > span
Strategy Meets Software div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
People Magic div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
Get your first 10 members in 30 days. a.sc-j93fj5-1 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
Migrate your business or add a new revenue stream. a.sc-j93fj5-1 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
Dedicated support to grow faster. a.sc-j93fj5-1 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
Getting Started div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
Your Time div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0
Making the Switch div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > div.sc-1jwbzwh-0 > p.sc-2c48m4-0

These are opportunities to improve the legibility of your content.

○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
●`[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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Identical links have the same purpose.
○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+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
3 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.

3 pass
Show all checked elements (3)
ElementRatioRequiredFGBGResult
title Just a moment...21.00:14.5:1
#000000
#FFFFFF
Pass
p Let's confirm you're…21.00:14.5:1
#000000
#FFFFFF
Pass
div Verification success…21.00:14.5: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.

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

Send Feedback