Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 2 REVIEW 8 FIX

Alt Text Quality

Action

2 of 78 images have issues

FIX

2 of 78 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

7 decorative image(s) correctly marked

69 image(s) with good alt text

78 images 69 good alt text 7 decorative 2 missing

Issue	Count
missing	2 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

18 issue(s) across 237 links and 109 buttons

FIX

18 issue(s) across 237 links and 109 buttons

11 link(s) with no accessible text

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

Got: ; ; ; ; ; ; ; ; ; (+1 more)

1 link(s) open in new tab without warning

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

Got: https://www.brooklinen.com/pages/faq?a=Does-Brooklinen-offer-free-US-shipping---id--1b50Cl_wSuiEqf4NUNMMOQ

7 button(s) with no accessible text

225 link(s) with descriptive text

237 links

11 empty

0 generic text

1 new tab

7 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.brooklinen.com/pages/super-p…	(empty)	empty	Add link text or aria-label
https://www.brooklinen.com/pages/faq?a=D…	Exclusions Apply *	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

327 links and buttons have descriptive text

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

; ; ; ; ; ; ; ; ; (+1 more)

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://www.brooklinen.com/pages/faq?a=Does-Brooklinen-offer-free-US-shipping---id--1b50Cl_wSuiEqf4NUNMMOQ

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

404 Error Page

Action

HTTP 429, custom page

FIX

HTTP 429, custom page

Unexpected status code: HTTP 429

Expected HTTP 404 but received 429. This may confuse search engine crawlers.

Got: HTTP 429

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 429 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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: #283455

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 ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 15 fail WCAG AA

REVIEW

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

5 pass 15 fail WCAG AA 2 pass AA only

h2 Shop by Category

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 150k+ 5-Star Reviews

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Don't Lie

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why Brooklinen?

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 In the News

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our Sheets

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get on the List

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Premium Materials & Exclusive Styles

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 365-Day Happiness Guarantee

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Fast, Free Shipping

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Get it before it's gone!

1.84:1

#000000

#42382F

needs 3.0:1 (large text)

19px · bottom of viewport

title Luxury Bedding, Sheets & Comforters Onli…

1.71:1

#000000

#283455

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.71:1

#000000

#283455

needs 4.5:1 (normal text)

16px · top of page (header area)

a Terms apply

2.12:1

#000000

#003AA1

needs 4.5:1 (normal text)

16px · above the fold

a Terms apply

2.12:1

#000000

#003AA1

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Shop by Category	1.84:1	3.0:1	#000000	#42382F	Fail
h2 150k+ 5-Star Reviews	1.84:1	3.0:1	#000000	#42382F	Fail
h2 Don't Lie	1.84:1	3.0:1	#000000	#42382F	Fail
h2 Why Brooklinen?	1.84:1	3.0:1	#000000	#42382F	Fail
h2 In the News	1.84:1	3.0:1	#000000	#42382F	Fail
h2 Our Sheets	1.84:1	3.0:1	#000000	#42382F	Fail
h2 Get on the List	1.84:1	3.0:1	#000000	#42382F	Fail
h3 Premium Materials & …	1.84:1	3.0:1	#000000	#42382F	Fail
h3 365-Day Happiness Gu…	1.84:1	3.0:1	#000000	#42382F	Fail
h3 Fast, Free Shipping	1.84:1	3.0:1	#000000	#42382F	Fail
h3 Get it before it's g…	1.84:1	3.0:1	#000000	#42382F	Fail
title Luxury Bedding, Shee…	1.71:1	4.5:1	#000000	#283455	Fail
a Skip to content	1.71:1	4.5:1	#000000	#283455	Fail
span COOLING Washed Europ…	5.56:1	4.5:1	#000000	#7D8396	Pass
a Shop now.	20.21:1	4.5:1	#000000	#FDFAF8	Pass
span Fast, free shipping …	20.21:1	4.5:1	#000000	#FDFAF8	Pass
span Just for you: 15% of…	16.27:1	4.5:1	#000000	#DDE3EC	Pass
a Click to redeem.	5.82:1	4.5:1	#000000	#6587C4	Pass
a Terms apply	2.12:1	4.5:1	#000000	#003AA1	Fail
a Terms apply	2.12:1	4.5:1	#000000	#003AA1	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.

Lighthouse Accessibility Audits

Score 89/100 — 4 failing, 31 passed

REVIEW

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.

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
a.media--link > div.media--video > video > img `a.media--link > div.media--video > video > img`

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
section#shopify-section-template--20183958847578__theme_hero_Jnaffx > section#template--20183958847578__theme_hero_Jnaffx > div.hero__media > a.media--link `section#shopify-section-template--20183958847578__theme_hero_Jnaffx > section#template--20183958847578__theme_hero_Jnaffx > div.hero__media > a.media--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

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
Facebook `div.footer__copyright > ul.footer__list-social > li.list-social__item > a.link`
Twitter `div.footer__copyright > ul.footer__list-social > li.list-social__item > a.link`
Pinterest `div.footer__copyright > ul.footer__list-social > li.list-social__item > a.link`
Instagram `div.footer__copyright > ul.footer__list-social > li.list-social__item > a.link`

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
Search ... `sticky-header.header-wrapper > header#bkl-5-v1 > div.header__icons > button.header__search`
1 `sticky-header.header-wrapper > header#bkl-5-v1 > div.header__icons > button.header__icon`

○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

●Buttons have an accessible name

●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

●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

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

○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

○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

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

○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

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

15 headings

PASS

15 headings

Multiple H1 headings (2 found)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H4 Your cart is empty
H4 Your Cart
H1 You Can't Outcool Our Linen You Can't Outcool Our Linen
H2 Shop by Category
H2 150k+ 5-Star Reviews Don't Lie
H1 (empty)
H2 Why Brooklinen?
H3 Premium Materials & Exclusive Styles
H3 365-Day Happiness Guarantee
H3 Fast, Free Shipping
H2 In the News
H2 Our Sheets
H3 Come Say Hi, IRL Come Say Hi, IRL
H2 Get on the List
H3 Get it before it's gone!

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Form Accessibility

All 9 controls labeled

PASS

All 9 controls labeled

9 control(s) properly labeled

9 controls

9 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#giftNoteCheckbox	checkbox		none
textarea	textarea	Gift Note	aria-label
BrokenCart_Popup	checkbox		none
#newsletter_email	email	newsletter signup	aria-label
#overlay_partial_sms_subscribe	tel	Phone Number	aria-label
#entranceOverlaySource	input	Source	for/id
#entranceOverlayUtmSource	input	UTM Source	for/id
#overlay_email	email	Email Address	aria-label
#overlay_partial_email	email	Email	aria-label

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