Skip to content
https://lnk.to

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
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
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
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
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
23 headings, 2 skip(s)
REVIEW
23 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Smartlinks for |
  • H3 Unleash your creative potential skipped
  • H3 Craft audience experiences that match your brand and goals.
  • H3 Understand fans like never before
  • H2 See how the best use Linkfire
  • H5 One Great Vegan skipped
  • H5 Zak Abel
  • H5 Taylor Swift
  • H5 Wiser Than Me
  • H5 Shakira
  • H5 Dean Lewis
  • H5 Ed Sheeran
  • H5 Zoë Ferguson
  • H5 Selena Gomez
  • H5 Kid Cudi
  • H5 AI
  • H5 Barbie The Album
  • H5 One Great Vegan
  • H5 Zak Abel
  • H5 Taylor Swift
  • H5 Wiser Than Me
  • H2 Linkfire customers' spotlight
  • H3 Try Linkfire for free

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
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 No page with this URL exists Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA
a Smartlinks
1.17:1
#000000
on
#17161F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Pre-release
1.17:1
#000000
on
#171622
needs 4.5:1 (normal text)
16px · above the fold
span Increase streams on release day
1.17:1
#000000
on
#171521
needs 4.5:1 (normal text)
16px · above the fold
a Release
1.17:1
#000000
on
#171620
needs 4.5:1 (normal text)
16px · above the fold
span Simplify your release marketing
1.17:1
#000000
on
#171620
needs 4.5:1 (normal text)
16px · above the fold
a Bio
1.17:1
#000000
on
#171620
needs 4.5:1 (normal text)
16px · above the fold
span Bring all your content together
1.17:1
#000000
on
#171620
needs 4.5:1 (normal text)
16px · above the fold
a Podcast
1.17:1
#000000
on
#171620
needs 4.5:1 (normal text)
16px · above the fold
span Elevate your podcast marketing
1.17:1
#000000
on
#171620
needs 4.5:1 (normal text)
16px · above the fold
a Reward
1.17:1
#000000
on
#171620
needs 4.5:1 (normal text)
16px · above the fold
span Turn fans into superfans
1.17:1
#000000
on
#171620
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Smartlinks for20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Linkfire customers' …20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Unleash your creativ…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Craft audience exper…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Understand fans like…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Try Linkfire for fre…20.12:13.0:1
#000000
#FAFAFA
Pass
title Smart Links for Musi…20.65:14.5:1
#000000
#FDFDFD
Pass
a Skip to content19.95:14.5:1
#000000
#F9F9F9
Pass
a Close19.95:14.5:1
#000000
#F9F9F9
Pass
a Smartlinks1.17:14.5:1
#000000
#17161F
Fail
a Pre-release1.17:14.5:1
#000000
#171622
Fail
span Increase streams on …1.17:14.5:1
#000000
#171521
Fail
a Release1.17:14.5:1
#000000
#171620
Fail
span Simplify your releas…1.17:14.5:1
#000000
#171620
Fail
a Bio1.17:14.5:1
#000000
#171620
Fail
span Bring all your conte…1.17:14.5:1
#000000
#171620
Fail
a Podcast1.17:14.5:1
#000000
#171620
Fail
span Elevate your podcast…1.17:14.5:1
#000000
#171620
Fail
a Reward1.17:14.5:1
#000000
#171620
Fail
span Turn fans into super…1.17:14.5:1
#000000
#171620
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 25 passed
REVIEW
88

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
TRUSTED BY INDUSTRY LEADERS AND ARTISTS ALIKE div.pwr-sec-clients > div.page-center > div.pwr-sec-clients__intro-sec > span.pwr-sec__title-intro
ROCKING THE MIC OR PUSHING RECORDS div.row-fluid > div.pwr-sec-split__left > div.pwr-sec-split__content > span.pwr-sec__title-intro
READ MORE div.row-fluid > div.pwr-sec-split__left > div.pwr-sec-split__content > a.pwr-sec-split__link
COLLECT DATA, DRIVE RESULTS div.row-fluid > div.pwr-sec-split__left > div.pwr-sec-split__content > span.pwr-sec__title-intro
READ MORE div.row-fluid > div.pwr-sec-split__left > div.pwr-sec-split__content > a.pwr-sec-split__link
YOU'LL BE IN GOOD COMPANY div.row-fluid > div.pwr-sec-image-boxes__intro-sec > span.pwr-sec__title-intro > center
YOU'LL BE IN GOOD COMPANY div.pwr-sec-testimonials > div.page-center > div.pwr-sec-testimonials__intro-sec > span.pwr-sec__title-intro
INDUSTRY PARTNERS div.pwr-sec-clients > div.page-center > div.pwr-sec-clients__intro-sec > span.pwr-sec__title-intro
Try Linkfire for free div.pwr-sec-cta-global > div.page-center > div.pwr-sec-contemt > h3#try-linkfire-for-free
Sign up for a 7-day or 14-day free trial. No credit card needed. div.page-center > div.pwr-sec-contemt > div.pwr-sec-cta__desc > p

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
Unleash your creative potential div.row-fluid > div.pwr-sec-split__left > div.pwr-sec-split__content > h3#unleash-your-creative-potential
Zak Abel div.pwr-image-box > div.pwr-image-box__below > span.pwr-rich-text > h5#zak-abel

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
linkfire-logo-light div.row-fluid > div.pwr-footer-company-info > div.pwr-footer__logo > 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.

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
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide div.pwr-sec-testimonials__slider > div.pwr--light > div.swiper-pagination > span.swiper-pagination-bullet
Platform div#hs_menu_wrapper_footer_page_ > ul > li.hs-menu-item > a
Company div#hs_menu_wrapper_footer_page_ > ul > li.hs-menu-item > a

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[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
`[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.
`button`, `link`, and `menuitem` elements have accessible names
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
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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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 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
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 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.
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.
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+
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Navigation Menu" MAIN CONTENTINFO footer
A+
Alt Text Quality
1 of 55 images have issues
PASS
1 of 55 images have issues
Warning::
1 image(s) with generic alt text
Info::
54 image(s) with good alt text
55 images 54 good alt text 1 generic
IssueCount
generic1 image(s)
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