Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureActionNo landmarksFIX
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>.
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.
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
FForm AccessibilityAction18 of 18 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| #user_profile_attributes_first_name | text | (First Name) | placeholder only |
| #user_email | text | (Email) | placeholder only |
| #user_password | password | (Create Password) | placeholder only |
| #user_profile_attributes_first_name | text | (First Name) | placeholder only |
| #user_email | text | (Email) | placeholder only |
| #user_password | password | (Create Password) | placeholder only |
| #user_password_dummy | password | (none) | none |
| commit | submit | (none) | none |
| #user_password_dummy | password | (none) | none |
| #user_gdpr_accepted | checkbox | (none) | none |
| commit | submit | (none) | none |
| #user_gdpr_accepted | checkbox | (none) | none |
| input | checkbox | (none) | none |
| input | checkbox | (none) | none |
| input | checkbox | (none) | none |
| input | checkbox | (none) | none |
| input | checkbox | (none) | none |
| input | checkbox | (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)
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">
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
DLink & Button QualityAction5 issue(s) across 70 links and 2 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| http://support.strikingly.com/hc/en-us/a… | Terms of Service | new tab | Add '(opens in new tab)' to text |
| http://support.strikingly.com/hc/en-us/a… | Privacy Policy | new tab | Add '(opens in new tab)' to text |
| http://www.nytimes.com/2013/05/05/magazi… | Y Combinator, Silicon Valley's… | new tab | Add '(opens in new tab)' to text |
| http://www.forbes.com/sites/morganhartle… | How a Y Combinator Startup Is … | new tab | Add '(opens in new tab)' to text |
| http://www.techcrunch.com/2013/02/13/str… | Y Combinator-Backed Strikingly… | new tab | Add '(opens in new tab)' to text |
| http://www.lifehacker.com/5989963/striki… | Strikingly Creates Simple, Bea… | new tab | Add '(opens in new tab)' to text |
| http://thenextweb.com/insider/2013/04/26… | Strikingly raises $1.5M from S… | new tab | Add '(opens in new tab)' to text |
| http://www.usatoday.com/story/tech/2013/… | TECH NOW: What to put on your … | new tab | Add '(opens in new tab)' to text |
| http://www.inc.com/issie-lapowsky/4-ways… | 4 Mistakes You're Probably Mak… | new tab | Add '(opens in new tab)' to text |
| http://support.strikingly.com/hc/en-us/a… | Terms of Service | new tab | Add '(opens in new tab)' to text |
| http://support.strikingly.com/hc/en-us/a… | Privacy Policy | new tab | Add '(opens in new tab)' to text |
| /s/ai_site_builder | AI Site Builder | new tab | Add '(opens in new tab)' to text |
| /logo-maker | AI Logo Maker | new tab | Add '(opens in new tab)' to text |
| https://apps.apple.com/us/app/strikingly… | iPhone App | new tab | Add '(opens in new tab)' to text |
| //x.com/strikingly | (empty) | empty | Add link text or aria-label |
| //www.instagram.com/striking.ly?igsh=MWI… | (empty) | empty | Add link text or aria-label |
| //www.facebook.com/strikingly/ | (empty) | empty | Add link text or aria-label |
| https://support.strikingly.com/hc/en-us/… | Learn More | generic text | Replace with descriptive text |
Before: Learn More Suggested: 9775440838939 | |||
| http://facebook.com/strikingly | new tab | Add '(opens in new tab)' to text | |
| http://twitter.com/Strikingly | new tab | Add '(opens in new tab)' to text | |
| https://support.strikingly.com/hc/en-us/… | Learn More | generic text | Replace with descriptive text |
Before: Learn More Suggested: 9775440838939 | |||
Links without text are announced as raw URLs by screen readers.
//x.com/strikingly; //www.instagram.com/striking.ly?igsh=MWI2bGVhYTVpcXZ3YQ==; //www.facebook.com/strikingly/
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
Generic link text like 'click here' doesn't describe the destination.
https://support.strikingly.com/hc/en-us/articles/9775440838939 ("Learn More"); https://support.strikingly.com/hc/en-us/articles/9775440838939 ("Learn More")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
http://support.strikingly.com/hc/en-us/articles/214364828; http://support.strikingly.com/hc/en-us/articles/214364818; http://www.nytimes.com/2013/05/05/magazine/y-combinator-silicon-valleys-start…; http://www.forbes.com/sites/morganhartley/2013/03/19/how-a-y-combinator-start…; http://www.techcrunch.com/2013/02/13/strikingly/; http://www.lifehacker.com/5989963/strikingly-creates-simple-beautiful-web-sit…; http://thenextweb.com/insider/2013/04/26/yc-alum-strikingly-nabs-1-5m-from-sv…; http://www.usatoday.com/story/tech/2013/09/29/personal-website-free-strikingl…; http://www.inc.com/issie-lapowsky/4-ways-screwing-up-website.html?cid=sf01001; http://support.strikingly.com/hc/en-us/articles/214364828 (+6 more)
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
F404 Error PageActionSoft 404 detectedFIX
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.
FFavicon & BrandingAction2 icon(s) detectedFIX
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
DLighthouse Accessibility AuditsActionScore 58/100 — 6 failing, 10 passedFIX
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.
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.
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.
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.
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.
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.
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.
BHeading Hierarchy29 headings, 2 skip(s)REVIEW
- 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.
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.
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
CAlt Text QualityAction16 of 34 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 16 image(s) |
Images without alt text are invisible to screen readers.
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
CColor Contrast (Screenshot)Action20 text elements analyzed, 3 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Make a website in mi… | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h2 Trusted by millions … | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h2 The Easiest Website … | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h2 E-commerce Built In | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h2 Turn Visitors to Sup… | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h2 All the Features You… | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h2 24/7 Support | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h2 Our Customers Love U… | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h3 Domain Names | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h3 Simple Store | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h3 Simple Blog | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h3 Analytics | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h3 Sign Up & Contact Fo… | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h3 Social Feed | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h3 HTTPS Built-in | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h3 ...and much, much mo… | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| h3 About Strikingly | 19.61:1 | 3.0:1 | #000000 | #F5F7FD | Pass |
| title How To Make a Websit… | 2.78:1 | 4.5:1 | #000000 | #5340B7 | Fail |
| span Limited Time Only: G… | 2.91:1 | 4.5:1 | #000000 | #5344BB | Fail |
| span Offer ending soon. | 3.05:1 | 4.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.