Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 5 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Alt Text Quality

Action

11 of 21 images have issues

FIX

11 of 21 images have issues

11 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 image-in-link without alt text

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

5 decorative image(s) correctly marked

5 image(s) with good alt text

21 images 5 good alt text 5 decorative 11 missing

Issue	Count
missing	11 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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Heading Hierarchy

3 headings, 1 skip(s)

REVIEW

3 headings, 1 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Your platform for sales funnels email marketing online courses selling online blogging sales funnels
H1 Your platform for sales funnels email marketing online courses selling online blogging sales funnels duplicate H1
H3 Create your free account skipped

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Form Accessibility

3 of 3 controls have issues

REVIEW

3 of 3 controls have issues

3 control(s) rely on placeholder only

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

Got: <input type="email" name="email" id="field-272619ad">; <input type="email" name="email" id="field-5ab0ec9c">; <input type="email" name="email" id="field-e5f1751e">

3 controls

0 labeled

3 placeholder only

0 unlabeled

Control	Type	Label	Method
#field-272619ad	email	(Enter your email address)	placeholder only
#field-5ab0ec9c	email	(Enter your email address)	placeholder only
#field-e5f1751e	email	(Enter your email address...)	placeholder only

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

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

Link & Button Quality

Action

8 issue(s) across 54 links and 7 buttons

REVIEW

8 issue(s) across 54 links and 7 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://systeme.io/; https://systeme.io/; https://systeme.io/; https://www.facebook.com/groups/251145835476950; https://www.linkedin.com/company/getsystemeio/; https://www.instagram.com/get.systeme.io/; https://x.com/systeme_io

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button[data-testid="popup-close-icon"]

47 link(s) with descriptive text

54 links

7 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://systeme.io/	(empty)	empty	Add link text or aria-label
https://systeme.io/	(empty)	empty	Add link text or aria-label
https://systeme.io/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/groups/25114583…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/getsyst…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/get.systeme.io…	(empty)	empty	Add link text or aria-label
https://x.com/systeme_io	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

53 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://systeme.io/; https://systeme.io/; https://systeme.io/; https://www.facebook.com/groups/251145835476950; https://www.linkedin.com/company/getsystemeio/; https://www.instagram.com/get.systeme.io/; https://x.com/systeme_io

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Icon-only buttons need an aria-label so screen readers can announce them.

button[data-testid="popup-close-icon"]

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 error page ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Lighthouse Accessibility Audits

Score 80/100 — 3 failing, 13 passed

REVIEW

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
Click here `div.sc-etlCFw > div.sc-gEvEes > button#button-6ef9febf > div.sc-fiCwlb`
Get started for free `div.sc-etlCFw > div.sc-gEvEes > button#button-a36ae30e > div.sc-fiCwlb`

These are opportunities to improve the legibility of your content.

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.sc-jMakVn > a > picture.sc-iMTnTM > img#image-c9a8d236 `div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-c9a8d236`
div.sc-gEvEes > div.sc-jMakVn > picture.sc-iMTnTM > img#image-a6baa169 `div.sc-gEvEes > div.sc-jMakVn > picture.sc-iMTnTM > img#image-a6baa169`
div.sc-gEvEes > div.sc-jMakVn > picture.sc-iMTnTM > img#image-e8e078d1 `div.sc-gEvEes > div.sc-jMakVn > picture.sc-iMTnTM > img#image-e8e078d1`
div.sc-gEvEes > div.sc-jMakVn > picture.sc-iMTnTM > img#image-22485ea2 `div.sc-gEvEes > div.sc-jMakVn > picture.sc-iMTnTM > img#image-22485ea2`
div.sc-gEvEes > div.sc-jMakVn > picture.sc-iMTnTM > img#image-91877773 `div.sc-gEvEes > div.sc-jMakVn > picture.sc-iMTnTM > img#image-91877773`
div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-29b532d5 `div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-29b532d5`
div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-b0ac2b53 `div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-b0ac2b53`
div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-470546ad `div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-470546ad`
div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-e7ae3195 `div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-e7ae3195`
div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-503decf1 `div.sc-jMakVn > a > picture.sc-iMTnTM > img#image-503decf1`

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-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a `div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a`
div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a `div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a`
div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a `div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a`
div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a `div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a`
div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a `div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a`
div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > a `div.sc-etlCFw > div.sc-gEvEes > div.sc-jMakVn > 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-hidden="true"]` is not present on the document `<body>`

●Buttons have an accessible name

●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-hidden="true"]` elements do not contain focusable descendents

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Document has a main landmark.

○`[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

○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

○Elements use only permitted ARIA attributes

○`[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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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 buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○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.

○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

○`<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.

○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+

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)

Element	Ratio	Required	FG	BG	Result
h1 Your platform for	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Your platform for	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Systeme.io - The onl…	19.47:1	4.5:1	#000000	#F6F6F9	Pass
span ⌄	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Why Systeme.io?	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Features	19.47:1	4.5:1	#000000	#F6F6F9	Pass
button Resources	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Pricing	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Sign in	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Why Systeme.io?	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Features	19.47:1	4.5:1	#000000	#F6F6F9	Pass
span Resources	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Tutorials	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Testimonials	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Podcast	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Blog	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Pricing	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Sign in	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Why systeme.io?	19.47:1	4.5:1	#000000	#F6F6F9	Pass
a Features	19.96:1	4.5:1	#000000	#F9F9FA	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.