Accessibility

D

Landmark Structure

Action

2 landmarks

FIX

2 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

F

Heading Hierarchy

Action

88 headings, 4 skip(s)

FIX

88 headings, 4 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Bralettes & Underwear
H2 Bralettes & Underwear
H2 Bralettes & Underwear
H2 Socks
H2 Socks
H2 Socks
H2 Slippers & Shoes
H2 Slippers & Shoes
H2 Slippers & Shoes
H2 T-Shirts
H2 T-Shirts
H2 T-Shirts
H2 THE WHITE SOCK EDIT
H2 THE WHITE SOCK EDIT
H2 THE WHITE SOCK EDIT
H2 THE WHITE SOCK EDIT
H2 THE WHITE SOCK EDIT
H2 THE WHITE SOCK EDIT
H2 CASUAL
H2 CASUAL
H2 CASUAL
H2 COMPRESSION
H2 COMPRESSION
H2 COMPRESSION
H2 SPORT
H2 SPORT
H2 SPORT
H2 DRESS
H2 DRESS
H2 DRESS
H2 ONE PURCHASED = ONE DONATED
H2 New Arrivals
H4 Women's Friday Clog skipped
H4 Beach Day Ankle Sock 4-Pack
H4 Garden Party Half Calf Socks
H4 Summer Ragg Quarter Sock 4-Pack
H2 New Arrivals
H2 New Arrivals
H2 New Arrivals
H4 Women's Friday Clog skipped
H4 Beach Day Ankle Sock 4-Pack
H4 Garden Party Half Calf Socks
H4 Summer Ragg Quarter Sock 4-Pack
H2 New Arrivals
H4 Men's Friday Slide skipped
H4 Run Ankle Sock 3-Pack
H4 Dress Calf Socks
H4 Originals Half Calf Sock 4-Pack
H2 New Arrivals
H2 New Arrivals
H2 New Arrivals
H4 Men's Friday Slide skipped
H4 Run Ankle Sock 3-Pack
H4 Dress Calf Socks
H4 Originals Half Calf Sock 4-Pack
H2 No Show
H2 No Show
H2 No Show
H2 Ankle
H2 Ankle
H2 Ankle
H2 Quarter
H2 Quarter
H2 Quarter
H2 Half Calf
H2 Half Calf
H2 Half Calf
H2 Calf
H2 Calf
H2 Calf
H2 Knee High
H2 Knee High
H2 Knee High
H2 200 MILLION+ DONATIONS
H2 200 MILLION+ DONATIONS
H2 200 MILLION+ DONATIONS
H2 200 MILLION+ DONATIONS
H2 200 MILLION+ DONATIONS
H2 200 MILLION+ DONATIONS
H2 SLIPPERS & SHOES
H2 SLIPPERS & SHOES
H2 SLIPPERS & SHOES
H2 UNDERWEAR
H2 UNDERWEAR
H2 UNDERWEAR
H2 TEES
H2 TEES
H2 TEES

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

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

F

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

D

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.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 2 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Link & Button Quality

1 issue(s) across 356 links and 71 buttons

REVIEW

1 issue(s) across 356 links and 71 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://bombas.com/pages/b-corp-certified ("Learn More")

10 link(s) open in new tab without warning

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

Got: https://www.beebetter.com; https://www.beebetter.com; https://www.beebetter.com; https://www.beebetter.com; https://www.beebetter.com; https://www.beebetter.com; https://www.instagram.com/bombas; https://www.facebook.com/bombassocks; https://www.twitter.com/bombas; https://www.pinterest.com/bombassocks

345 link(s) with descriptive text

356 links

0 empty

1 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.beebetter.com	See Your Impact	new tab	Add '(opens in new tab)' to text
https://www.beebetter.com	See Your Impact	new tab	Add '(opens in new tab)' to text
https://www.beebetter.com	See Your Impact	new tab	Add '(opens in new tab)' to text
https://www.beebetter.com	See Your Impact	new tab	Add '(opens in new tab)' to text
https://www.beebetter.com	See Your Impact	new tab	Add '(opens in new tab)' to text
https://www.beebetter.com	See Your Impact	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/bombas	instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/bombassocks	facebook	new tab	Add '(opens in new tab)' to text
https://www.twitter.com/bombas	twitter	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/bombassocks	pinterest	new tab	Add '(opens in new tab)' to text
https://bombas.com/pages/b-corp-certifie…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: B Corp Certified

416 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://bombas.com/pages/b-corp-certified ("Learn More")

Why this matters

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.

https://www.beebetter.com; https://www.beebetter.com; https://www.beebetter.com; https://www.beebetter.com; https://www.beebetter.com; https://www.beebetter.com; https://www.instagram.com/bombas; https://www.facebook.com/bombassocks; https://www.twitter.com/bombas; https://www.pinterest.com/bombassocks

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

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found - Bombas ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 2 pass AA only

h2 Slippers & Shoes

1.22:1

#000000

on

#20191D

needs 3.0:1 (large text)

24px · mid-page

h2 Slippers & Shoes

1.15:1

#000000

on

#191416

needs 3.0:1 (large text)

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

h2 T-Shirts

1.26:1

#000000

on

#141F2D

needs 3.0:1 (large text)

24px · mid-page

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 Bralettes & Underwea…	13.45:1	3.0:1	#000000	#D5CEC4	Pass
h2 Bralettes & Underwea…	13.32:1	3.0:1	#000000	#D4CDC3	Pass
h2 Bralettes & Underwea…	13.05:1	3.0:1	#000000	#D2CBC1	Pass
h2 Socks	13.09:1	3.0:1	#000000	#D4CBBF	Pass
h2 Socks	13.58:1	3.0:1	#000000	#D5CFC7	Pass
h2 Socks	13.75:1	3.0:1	#000000	#D7D0C8	Pass
h2 Slippers & Shoes	5.37:1	3.0:1	#000000	#838081	Pass
h2 Slippers & Shoes	1.22:1	3.0:1	#000000	#20191D	Fail
h2 Slippers & Shoes	1.15:1	3.0:1	#000000	#191416	Fail
h2 T-Shirts	1.26:1	3.0:1	#000000	#141F2D	Fail
h2 T-Shirts	3.06:1	3.0:1	#000000	#545974	Pass
h2 T-Shirts	4.42:1	3.0:1	#000000	#6B728D	Pass
h2 THE WHITE SOCK EDIT	8.16:1	3.0:1	#000000	#96A1C1	Pass
h2 THE WHITE SOCK EDIT	8.16:1	3.0:1	#000000	#96A1C1	Pass
h2 THE WHITE SOCK EDIT	8.16:1	3.0:1	#000000	#96A1C1	Pass
h2 THE WHITE SOCK EDIT	8.16:1	3.0:1	#000000	#96A1C1	Pass
h2 THE WHITE SOCK EDIT	8.16:1	3.0:1	#000000	#96A1C1	Pass
h2 THE WHITE SOCK EDIT	8.16:1	3.0:1	#000000	#96A1C1	Pass
h2 CASUAL	8.16:1	3.0:1	#000000	#96A1C1	Pass
h2 CASUAL	8.16:1	3.0:1	#000000	#96A1C1	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.

B

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 23 passed

REVIEW

88

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.

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
Women's Friday Clog `div.ProductCard-styled__ProductCardContent-sc-c2e0cdfa-14 > a > div.ProductCard-styled__Info-sc-c2e0cdfa-1 > h4.ProductCard-styled__Title-sc-c2e0cdfa-7`
Men's Friday Slide `div.ProductCard-styled__ProductCardContent-sc-c2e0cdfa-14 > a > div.ProductCard-styled__Info-sc-c2e0cdfa-1 > h4.ProductCard-styled__Title-sc-c2e0cdfa-7`

These are opportunities to improve keyboard navigation in your application.

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

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > input `body > input`

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 `html`

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

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

●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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

●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

○`button`, `link`, and `menuitem` elements have accessible names

○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

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

○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

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

Alt Text Quality

All 130 images OK

PASS

All 130 images OK

114 decorative image(s) correctly marked

16 image(s) with good alt text

130 images 16 good alt text 114 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 63 controls labeled

PASS

All 63 controls labeled

63 control(s) properly labeled

63 controls

63 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
#footerFormEmail	email	Email	for/id