Skip to content
https://linktr.ee

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Landmark Structure
Action
11 landmarks
FIX
11 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header NAV MAIN (missing!) ASIDE CONTENTINFO (missing!)

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

D
Form Accessibility
Action
4 of 4 controls have issues
FIX
4 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="Username" id="username-header">; <input type="text" name="Username" id="username-footer">
4 controls
0 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#username-headertext(linktr.ee/yourname)placeholder only
#username-footertext(linktr.ee/yourname)placeholder only
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">

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="Username" id="username-header">; <input type="text" name="Username" id="username-footer">

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

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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Linktree ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
11 icon(s) detected
REVIEW
11 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 89/100 — 5 failing, 24 passed
REVIEW
89

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
creators influencers small businesses athletes models monetizers health educato… section.trusted-by > div._w-scrolling-heading > div.swiper > div#swiper-wrapper-9219c5bde34181ae

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Why should podcasters use Linktree? div.faq-item > div.faq-head > div.q-wrapper > h4.faq-question

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
div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button
div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.w-mod-js html.w-mod-js

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English div.dg-app > div > div.dg-main-language-dropdown > button.language-dropdown-trigger
○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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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.
●`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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
○`[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
○`[role]`s are contained by their required parent element
○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
○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
○Links are distinguishable without relying on color.
○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.
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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
Heading Hierarchy
28 headings, 1 skip(s)
PASS
28 headings, 1 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.
  • H1 A link in bio built for you.
  • H2 Create and customize your Linktree in minutes
  • H2 Share your Linktree anywhere you like!
  • H2 Analyze your audience and keep them engaged
  • H2 The only link in bio trusted by 70M+
  • H3 Share every type of content in limitless ways
  • H3 Sell products, collect payments and make monetization simple
  • H3 Grow, own and engage your audience across all of your channels
  • H2 The fast, friendly and powerful link in bio tool.
  • H2 As featured in...
  • H3 “With Linktree, I can definitely see the monetization of my following becoming a full-time thing.”
  • H3 “Linktree simplifies the process for creators to share multiple parts of themselves in one inclusive link.”
  • H3 “Linktree helps my customers get where they need to go. It's fast and easy.”
  • H3 “I use Linktree's analytics to better understand my audience and what converts them.”
  • H3 “My Linktree resume stood out from the rest, securing me my first full-time job as a TV reporter!”
  • H3 “With Linktree, I can definitely see the monetization of my following becoming a full-time thing.”
  • H3 “Linktree simplifies the process for creators to share multiple parts of themselves in one inclusive link.”
  • H2 Questions? Answered
  • H4 Why should podcasters use Linktree? skipped
  • H4 Is Linktree the original link in bio tool?
  • H4 Can you get paid and sell things from a Linktree?
  • H4 Is Linktree safe to use on all of my social media profiles?
  • H4 What makes Linktree better than the other link in bio options?
  • H4 How can I drive more traffic to and through my Linktree?
  • H4 How many links should I have on my Linktree?
  • H4 Do I need a website to use Linktree?
  • H4 Where can I download the app?
  • H2 Jumpstart your corner of the internet today

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

A+
Alt Text Quality
All 73 images OK
PASS
All 73 images OK
Info::
63 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
73 images 10 good alt text 63 decorative
All images have appropriate alt text.
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Linktree
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: minimal-ui
PWA Install Criteria ✓ Installable
Name Linktree ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode minimal-ui ✓
Name Linktree Display Mode minimal-ui Theme Color #F3F3F1 Background Color #F3F3F1 Icons 8 icon(s)
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)
ElementRatioRequiredFGBGResult
h1 A link in bio built …10.25:13.0:1
#000000
#ADBF1C
Pass
h2 Create and customize…10.25:13.0:1
#000000
#ADBF1C
Pass
h2 Share your Linktree …10.25:13.0:1
#000000
#ADBF1C
Pass
h2 Analyze your audienc…10.25:13.0:1
#000000
#ADBF1C
Pass
h2 The only link in bio…10.25:13.0:1
#000000
#ADBF1C
Pass
h2 The fast, friendly a…10.25:13.0:1
#000000
#ADBF1C
Pass
h2 As featured in...10.25:13.0:1
#000000
#ADBF1C
Pass
h2 Questions? Answered10.25:13.0:1
#000000
#ADBF1C
Pass
h2 Jumpstart your corne…10.25:13.0:1
#000000
#ADBF1C
Pass
h3 Share every type of …10.25:13.0:1
#000000
#ADBF1C
Pass
h3 Sell products, colle…10.25:13.0:1
#000000
#ADBF1C
Pass
h3 Grow, own and engage…10.25:13.0:1
#000000
#ADBF1C
Pass
h3 “With Linktree, I …10.25:13.0:1
#000000
#ADBF1C
Pass
h3 “Linktree simplifi…10.25:13.0:1
#000000
#ADBF1C
Pass
h3 “Linktree helps my…10.25:13.0:1
#000000
#ADBF1C
Pass
h3 “I use Linktree's …10.25:13.0:1
#000000
#ADBF1C
Pass
h3 “My Linktree resum…10.25:13.0:1
#000000
#ADBF1C
Pass
h3 “With Linktree, I …10.25:13.0:1
#000000
#ADBF1C
Pass
h3 “Linktree simplifi…10.25:13.0:1
#000000
#ADBF1C
Pass
title Link in bio tool: Ev…15.31:14.5:1
#000000
#D2E823
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