Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Landmark Structure

Action

1 landmarks

FIX

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

Page Structure — as a screen reader sees it

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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Link & Button Quality

Action

3 issue(s) across 109 links and 5 buttons

REVIEW

3 issue(s) across 109 links and 5 buttons

3 link(s) with no accessible text

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

Got: /; https://techcrunch.com/2020/12/18/unfold-bio-sites/?guccounter=1&guce_referre…; https://www.inc.com/rebecca-deczynski/squarespace-new-ecommerce-tools-hollist…

23 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://blog.biosites.com/blog/sell-digital-products-through-your-link-in-bio; https://blog.biosites.com/blog/monetize-your-time-through-your-link-in-bio; https://www.squarespace.com/; https://blog.biosites.com/blog/sell-digital-products-through-your-link-in-bio; https://blog.biosites.com/blog/monetize-your-time-through-your-link-in-bio; https://blog.biosites.com/blog/introducing-product-links; https://blog.biosites.com/blog/sell-digital-products-through-your-link-in-bio; https://blog.biosites.com/blog/monetize-your-time-through-your-link-in-bio; https://help.unfold.com/hc/en-us; https://help.unfold.com/hc/en-us/requests/new (+13 more)

83 link(s) with descriptive text

109 links

3 empty

0 generic text

23 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://techcrunch.com/2020/12/18/unfold…	(empty)	empty	Add link text or aria-label
https://www.inc.com/rebecca-deczynski/sq…	(empty)	empty	Add link text or aria-label
https://blog.biosites.com/blog/sell-digi…	digital downloads	new tab	Add '(opens in new tab)' to text
https://blog.biosites.com/blog/monetize-…	1:1 appointments	new tab	Add '(opens in new tab)' to text
https://www.squarespace.com/	Squarespace	new tab	Add '(opens in new tab)' to text
https://blog.biosites.com/blog/sell-digi…	digital products	new tab	Add '(opens in new tab)' to text
https://blog.biosites.com/blog/monetize-…	1:1 appointments	new tab	Add '(opens in new tab)' to text
https://blog.biosites.com/blog/introduci…	Product Links	new tab	Add '(opens in new tab)' to text
https://blog.biosites.com/blog/sell-digi…	Downloadable digital products	new tab	Add '(opens in new tab)' to text
https://blog.biosites.com/blog/monetize-…	1:1 appointments calendar	new tab	Add '(opens in new tab)' to text
https://help.unfold.com/hc/en-us	Help Desk page	new tab	Add '(opens in new tab)' to text
https://help.unfold.com/hc/en-us/request…	support team at Squarespace	new tab	Add '(opens in new tab)' to text
https://www.squarespace.com/	Squarespace	new tab	Add '(opens in new tab)' to text
https://squarespace.com	Squarespace	new tab	Add '(opens in new tab)' to text
https://unfold.com/	Unfold	new tab	Add '(opens in new tab)' to text
https://www.squarespace.com/about/career…	Careers	new tab	Add '(opens in new tab)' to text
https://help.unfold.com	Help Desk	new tab	Add '(opens in new tab)' to text
https://help.unfold.com/hc/en-us/request…	Contact	new tab	Add '(opens in new tab)' to text
mailto:press@unfold.com	Press	new tab	Add '(opens in new tab)' to text
https://www.squarespace.com/terms-of-ser…	Terms of service	new tab	Add '(opens in new tab)' to text
https://www.squarespace.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/bio.sites/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@bio.sites	TikTok	new tab	Add '(opens in new tab)' to text
https://www.squarespace.com/cookie-polic…	Cookie Policy	new tab	Add '(opens in new tab)' to text
https://www.squarespace.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text

88 links and buttons have descriptive text

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

/; https://techcrunch.com/2020/12/18/unfold-bio-sites/?guccounter=1&guce_referre…; https://www.inc.com/rebecca-deczynski/squarespace-new-ecommerce-tools-hollist…

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

Add '(opens in new tab)' to link text or aria-label.

https://blog.biosites.com/blog/sell-digital-products-through-your-link-in-bio; https://blog.biosites.com/blog/monetize-your-time-through-your-link-in-bio; https://www.squarespace.com/; https://blog.biosites.com/blog/sell-digital-products-through-your-link-in-bio; https://blog.biosites.com/blog/monetize-your-time-through-your-link-in-bio; https://blog.biosites.com/blog/introducing-product-links; https://blog.biosites.com/blog/sell-digital-products-through-your-link-in-bio; https://blog.biosites.com/blog/monetize-your-time-through-your-link-in-bio; https://help.unfold.com/hc/en-us; https://help.unfold.com/hc/en-us/requests/new (+13 more)

Why this matters

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

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h2 Stand out with engaging designs

1.01:1

#000000

#010101

needs 3.0:1 (large text)

24px · above the fold

h2 Make money online

1.01:1

#000000

#010101

needs 3.0:1 (large text)

24px · above the fold

h2 Build lasting connections

2.41:1

#000000

#4B4B4B

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

h3 Why should I use a link in bio tool?

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Is a link in bio from Bio Sites really f…

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

h3 How do I monetize my link in bio?

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Do I need a website to use a link in bio…

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

h3 How do I add a link in bio to my profile…

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

h3 What should I put in my link in bio?

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Can I have more than one link in bio pag…

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Can I use Bio Sites to create a link in …

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

h3 I have some questions about my Bio Site.…

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Can I make a Bio Site if I'm new to Squa…

1.01:1

#000000

#010101

needs 3.0:1 (large text)

19px · bottom of viewport

span Log in

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Sign up

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Sign up for free

1.01:1

#000000

#010101

needs 4.5:1 (normal text)

16px · above the fold

span Your brand, your storefront, one link.

1.01:1

#000000

#010101

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Stand out with engag…	1.01:1	3.0:1	#000000	#010101	Fail
h2 Make money online	1.01:1	3.0:1	#000000	#010101	Fail
h2 Build lasting connec…	2.41:1	3.0:1	#000000	#4B4B4B	Fail
h2 See what's working	13.08:1	3.0:1	#000000	#CCCCCC	Pass
h3 Why should I use a l…	1.01:1	3.0:1	#000000	#010101	Fail
h3 Is a link in bio fro…	1.01:1	3.0:1	#000000	#010101	Fail
h3 How do I monetize my…	1.01:1	3.0:1	#000000	#010101	Fail
h3 Do I need a website …	1.01:1	3.0:1	#000000	#010101	Fail
h3 How do I add a link …	1.01:1	3.0:1	#000000	#010101	Fail
h3 What should I put in…	1.01:1	3.0:1	#000000	#010101	Fail
h3 Can I have more than…	1.01:1	3.0:1	#000000	#010101	Fail
h3 Can I use Bio Sites …	1.01:1	3.0:1	#000000	#010101	Fail
h3 I have some question…	1.01:1	3.0:1	#000000	#010101	Fail
h3 Can I make a Bio Sit…	1.01:1	3.0:1	#000000	#010101	Fail
title Free Link in Bio Too…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Blog	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Log in	1.00:1	4.5:1	#000000	#000000	Fail
span Sign up	1.00:1	4.5:1	#000000	#000000	Fail
span Sign up for free	1.01:1	4.5:1	#000000	#010101	Fail
span Your brand, your sto…	1.01:1	4.5:1	#000000	#010101	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.

Heading Hierarchy

20 headings

PASS

20 headings

Multiple H1 headings (2 found)

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

H1 Your brand, your storefront, one link.
H2 Stand out with engaging designs
H2 Make money online
H2 Build lasting connections
H2 See what's working
H3 Trusted by millions of
H4 As Seen In
H2 Frequently Asked Questions
H3 Why should I use a link in bio tool?
H3 Is a link in bio from Bio Sites really free?
H3 How do I monetize my link in bio?
H3 Do I need a website to use a link in bio tool?
H3 How do I add a link in bio to my profile?
H3 What should I put in my link in bio?
H3 Can I have more than one link in bio page with Bio Sites?
H3 Can I use Bio Sites to create a link in bio for my clients?
H3 I have some questions about my Bio Site. Do you have a support team?
H3 Can I make a Bio Site if I'm new to Squarespace?
H1 Build your free link in bio page duplicate H1
H2 bio.site/Yourname ↗

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

A+

Alt Text Quality

All 74 images OK

PASS

All 74 images OK

2 decorative image(s) correctly marked

72 image(s) with good alt text

74 images 72 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Bio Sites

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Bio Sites ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Bio Sites Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 27 passed

PASS

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
Interior designer `div.index_carouselWrapper__m9Do0 > div.index_carousel__Uad_T > figure.index_card__KykGK > span.index_cardHeading__O9mki`
Musician `div.index_carouselWrapper__m9Do0 > div.index_carousel__Uad_T > figure.index_card__KykGK > span.index_cardHeading__O9mki`
Interior designer `div.index_carouselWrapper__m9Do0 > div.index_carousel__Uad_T > figure.index_card__KykGK > span.index_cardHeading__O9mki`
Musician `div.index_carouselWrapper__m9Do0 > div.index_carousel__Uad_T > figure.index_card__KykGK > span.index_cardHeading__O9mki`
Interior designer `div.index_carouselWrapper__m9Do0 > div.index_carousel__Uad_T > figure.index_card__KykGK > span.index_cardHeading__O9mki`
Musician `div.index_carouselWrapper__m9Do0 > div.index_carousel__Uad_T > figure.index_card__KykGK > span.index_cardHeading__O9mki`
Interior designer `div.index_carouselWrapper__m9Do0 > div.index_carousel__Uad_T > figure.index_card__KykGK > span.index_cardHeading__O9mki`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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 > div#navbar > div.index_navbar__wrapper__0cyoK > a.index_logoLinkWrapper__JxkgS `div > div#navbar > div.index_navbar__wrapper__0cyoK > a.index_logoLinkWrapper__JxkgS`
div > div.index_asSeenIn__wn3qF > div.index_container__bfonW > a.index_frame__NxMFK `div > div.index_asSeenIn__wn3qF > div.index_container__bfonW > a.index_frame__NxMFK`
div > div.index_asSeenIn__wn3qF > div.index_container__bfonW > a.index_frame__NxMFK `div > div.index_asSeenIn__wn3qF > div.index_container__bfonW > a.index_frame__NxMFK`

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-*]` 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

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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

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

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

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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.