Skip to content
https://mystrikingly.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
37
GRADE
F
FIX
10
REVIEW
3
PASS
0
INFO
0
Checks
13
3 REVIEW 10 FIX
D
Landmark Structure
Action
No landmarks
FIX
No 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 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.

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

F
Form Accessibility
Action
18 of 18 controls have issues
FIX
18 of 18 controls have issues
Critical::
12 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="password" name="user[password_dummy]" id="user_password_dummy">; <input type="submit" name="commit">; <input type="checkbox" name="user[gdpr_accepted]" id="user_gdpr_accepted">; <input type="password" name="user[password_dummy]" id="user_password_dummy">; <input type="submit" name="commit">; <input type="checkbox" name="user[gdpr_accepted]" id="user_gdpr_accepted">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox"> (+2 more)
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="user[profile_attributes][first_name]" id="user_profile_attributes_first_name">; <input type="text" name="user[email]" id="user_email">; <input type="password" name="user[password]" id="user_password">; <input type="text" name="user[profile_attributes][first_name]" id="user_profile_attributes_first_name">; <input type="text" name="user[email]" id="user_email">; <input type="password" name="user[password]" id="user_password">
18 controls
0 labeled
6 placeholder only
12 unlabeled
ControlTypeLabelMethod
#user_profile_attributes_first_nametext(First Name)placeholder only
#user_emailtext(Email)placeholder only
#user_passwordpassword(Create Password)placeholder only
#user_profile_attributes_first_nametext(First Name)placeholder only
#user_emailtext(Email)placeholder only
#user_passwordpassword(Create Password)placeholder only
#user_password_dummypassword(none)none
commitsubmit(none)none
#user_password_dummypassword(none)none
#user_gdpr_acceptedcheckbox(none)none
commitsubmit(none)none
#user_gdpr_acceptedcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none

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

<input type="password" name="user[password_dummy]" id="user_password_dummy">; <input type="submit" name="commit">; <input type="checkbox" name="user[gdpr_accepted]" id="user_gdpr_accepted">; <input type="password" name="user[password_dummy]" id="user_password_dummy">; <input type="submit" name="commit">; <input type="checkbox" name="user[gdpr_accepted]" id="user_gdpr_accepted">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox"> (+2 more)

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

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

<input type="text" name="user[profile_attributes][first_name]" id="user_profile_attributes_first_name">; <input type="text" name="user[email]" id="user_email">; <input type="password" name="user[password]" id="user_password">; <input type="text" name="user[profile_attributes][first_name]" id="user_profile_attributes_first_name">; <input type="text" name="user[email]" id="user_email">; <input type="password" name="user[password]" id="user_password">

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

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-d1e1e5
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://mystrikingly.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://mystrikingly.com/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::
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.
D
Lighthouse Accessibility Audits
Action
Score 58/100 — 6 failing, 10 passed
FIX
58

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
form#new_user > div.row > div.col > input.submit form#new_user > div.row > div.col > input.submit
SIGN UP WITH FACEBOOK div.row > div.facebook-login-container > div.facebook-login-wrapper > a.facebook-login
Founder, Tribewanted div.seven > div.profile > div.info > p.title
Owner, Red Paper Plane div.seven > div.profile > div.info > p.title
Painter & Illustrator div.seven > div.profile > div.info > p.title
Featured In div.section > div.container > div.sixteen > p.light
We're fanatical about your success. Hear it from our users – Strikingly just wo… div.inner > div.container > div.ten > p.light
form#new_user > div.row > div.col > input.submit form#new_user > div.row > div.col > input.submit
SIGN UP WITH FACEBOOK div.row > div.facebook-login-container > div.facebook-login-wrapper > a.facebook-login

These are opportunities to improve the legibility of your content.

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
Ben Keene div.seven > div.profile > div.info > h4
Strikingly div.container > div.sixteen > div.footer-column > h6

These are opportunities to improve keyboard navigation in your application.

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.profile-row > div.seven > div.profile > img.lazy div.profile-row > div.seven > div.profile > img.lazy
div.profile-row > div.seven > div.profile > img.lazy div.profile-row > div.seven > div.profile > img.lazy
div.profile-row > div.seven > div.profile > img.lazy div.profile-row > div.seven > div.profile > img.lazy
div.ten > div.testimonial > div.info > img.lazy div.ten > div.testimonial > div.info > img.lazy
div.ten > div.testimonial > div.info > img.lazy div.ten > div.testimonial > div.info > img.lazy
div.ten > div.testimonial > div.info > img.lazy div.ten > div.testimonial > div.info > img.lazy
div.ten > div.testimonial > div.info > img.lazy div.ten > div.testimonial > div.info > img.lazy
div.ten > div.testimonial > div.info > img.lazy div.ten > div.testimonial > div.info > img.lazy

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.row > div.facebook-login-container > div.terms > input#user_gdpr_accepted div.row > div.facebook-login-container > div.terms > input#user_gdpr_accepted
div.row > div.facebook-login-container > div.terms > input#user_gdpr_accepted div.row > div.facebook-login-container > div.terms > input#user_gdpr_accepted

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.footer-column > div.footer-link-items > div.social-media-items > a.icon-item div.footer-column > div.footer-link-items > div.social-media-items > a.icon-item
div.footer-column > div.footer-link-items > div.social-media-items > a.icon-item div.footer-column > div.footer-link-items > div.social-media-items > a.icon-item
div.footer-column > div.footer-link-items > div.social-media-items > a.icon-item div.footer-column > div.footer-link-items > div.social-media-items > a.icon-item

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Templates div.sixteen > div.footer-column > div.footer-link-items > a.s-link
AI Site Builder div.sixteen > div.footer-column > div.footer-link-items > a.s-link
Pricing & Plans div.sixteen > div.footer-column > div.footer-link-items > a.s-link
Strikingly Kickstart div.sixteen > div.footer-column > div.footer-link-items > a.s-link
AI Logo Maker div.sixteen > div.footer-column > div.footer-link-items > a.s-link
iPhone App div.sixteen > div.footer-column > div.footer-link-items > a.s-link
Strikingly Blog div.sixteen > div.footer-column > div.footer-link-items > a.s-link
Idea Forum div.sixteen > div.footer-column > div.footer-link-items > a.s-link
Sitemap div.sixteen > div.footer-column > div.footer-link-items > a.s-link
Affiliate Program div.sixteen > div.footer-column > div.footer-link-items > a.s-link
Agencies & Resellers div.sixteen > div.footer-column > div.footer-link-items > a.s-link
We're Hiring! div.sixteen > div.footer-column > div.footer-link-items > a.s-link
Our Manifesto div.sixteen > div.footer-column > div.footer-link-items > a.s-link

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>`
Input buttons have discernible text.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
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.
Document has a main landmark.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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
Deprecated ARIA roles were not used
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 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
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
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<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
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.
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.
B
Heading Hierarchy
29 headings, 2 skip(s)
REVIEW
29 headings, 2 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.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Make a website in minutes
  • H2 Trusted by millions of entrepreneurs and creatives
  • H4 Ben Keene skipped
  • H4 Tsveti Kamova
  • H4 Edd Baptista
  • H2 The Easiest Website Editor Possible
  • H2 E-commerce Built In
  • H2 Turn Visitors to Superfans
  • H2 All the Features You Need
  • H3 Domain Names
  • H3 Simple Store
  • H3 Simple Blog
  • H3 Analytics
  • H3 Sign Up & Contact Forms
  • H3 Social Feed
  • H3 HTTPS Built-in
  • H3 ...and much, much more!
  • H2 24/7 Support
  • H2 Our Customers Love Us
  • H6 Strikingly skipped
  • H6 Extras
  • H6 Community
  • H6 Partners
  • H6 Company
  • H6 Help & Support
  • H3 About Strikingly
  • H4 Support
  • H4 Press
  • H4 Social Media

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

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

C
Alt Text Quality
Action
16 of 34 images have issues
REVIEW
16 of 34 images have issues
Critical::
16 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
34 images 17 good alt text 1 decorative 16 missing
IssueCount
missing16 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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
title How To Make a Website – Free Website B…
2.78:1
#000000
on
#5340B7
needs 4.5:1 (normal text)
16px · top of page (header area)
span Limited Time Only: Get a free domain wit…
2.91:1
#000000
on
#5344BB
needs 4.5:1 (normal text)
16px · top of page (header area)
span Offer ending soon.
3.05:1
#000000
on
#5348BF
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Make a website in mi…19.61:13.0:1
#000000
#F5F7FD
Pass
h2 Trusted by millions …19.61:13.0:1
#000000
#F5F7FD
Pass
h2 The Easiest Website …19.61:13.0:1
#000000
#F5F7FD
Pass
h2 E-commerce Built In19.61:13.0:1
#000000
#F5F7FD
Pass
h2 Turn Visitors to Sup…19.61:13.0:1
#000000
#F5F7FD
Pass
h2 All the Features You…19.61:13.0:1
#000000
#F5F7FD
Pass
h2 24/7 Support19.61:13.0:1
#000000
#F5F7FD
Pass
h2 Our Customers Love U…19.61:13.0:1
#000000
#F5F7FD
Pass
h3 Domain Names19.61:13.0:1
#000000
#F5F7FD
Pass
h3 Simple Store19.61:13.0:1
#000000
#F5F7FD
Pass
h3 Simple Blog19.61:13.0:1
#000000
#F5F7FD
Pass
h3 Analytics19.61:13.0:1
#000000
#F5F7FD
Pass
h3 Sign Up & Contact Fo…19.61:13.0:1
#000000
#F5F7FD
Pass
h3 Social Feed19.61:13.0:1
#000000
#F5F7FD
Pass
h3 HTTPS Built-in19.61:13.0:1
#000000
#F5F7FD
Pass
h3 ...and much, much mo…19.61:13.0:1
#000000
#F5F7FD
Pass
h3 About Strikingly19.61:13.0:1
#000000
#F5F7FD
Pass
title How To Make a Websit…2.78:14.5:1
#000000
#5340B7
Fail
span Limited Time Only: G…2.91:14.5:1
#000000
#5344BB
Fail
span Offer ending soon.3.05:14.5:1
#000000
#5348BF
Fail

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