Skip to content
https://bearbottomclothing.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
9
REVIEW
2
PASS
13
INFO
0
Checks
24
13 PASS 2 REVIEW 9 FIX
D
Iframe Accessibility
Action
5/10 iframe(s) missing title; 0 placeholder(s)
FIX
5/10 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://bearbottomclothing.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/a…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://bearbottomclothing.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/c…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://bearbottomclothing.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/c…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://bearbottomclothing.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/c…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://bearbottomclothing.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/c…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
D
Tap Target Adequacy
Action
44 tap target(s) too small or too close together
FIX
44 tap target(s) too small or too close together
Warning::
44 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
D
404 Error Page
Action
HTTP 404, custom page
FIX
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 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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 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
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
Theme color only
FIX
Theme color only
Info::
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: #1b1b1b
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 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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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
Mobile-Readable Font Sizes
94% of visible text renders at >= 12 CSS px (3 below threshold)
REVIEW
94% of visible text renders at >= 12 CSS px (3 below threshold)
Info::
3 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.5px ("BUILT FOR THE IN-BETWEEN"); <span> 11.5px ("SHOP OUR SOFTEST COLLECTION"); <span> 11.5px ("FREE 2-3 DAY SHIPPING ON ORDERS $125+").
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 14 pass AA only
title Bearbottom | Everyday Men's Clothing - S…
1.16:1
#000000
on
#161616
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.87:1
#000000
on
#3B3B3B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Accessibility Statement
4.37:1
#000000
on
#727272
needs 4.5:1 (normal text)
16px · top of page (header area)
span Pause slideshow
2.87:1
#000000
on
#5A564D
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Play slideshow
1.13:1
#000000
on
#14130D
needs 4.5:1 (normal text)
16px · above the fold
span BUILT FOR THE IN-BETWEEN
1.10:1
#000000
on
#10100C
needs 4.5:1 (normal text)
16px · above the fold

2 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)
ElementRatioRequiredFGBGResult
h2 BEST SELLERS4.37:13.0:1
#000000
#727272
Pass
h2 NEW ARRIVALS4.37:13.0:1
#000000
#727272
Pass
h2 BUNDLE & SAVE4.37:13.0:1
#000000
#727272
Pass
h2 One Item Purchased =…4.37:13.0:1
#000000
#727272
Pass
h2 OVER 35,000 5-STAR R…4.37:13.0:1
#000000
#727272
Pass
h2 JOIN THE ADVENTURE @…4.37:13.0:1
#000000
#727272
Pass
h2 Shop4.37:13.0:1
#000000
#727272
Pass
h2 Support4.37:13.0:1
#000000
#727272
Pass
h2 More Info4.37:13.0:1
#000000
#727272
Pass
h2 Join the newsletter4.37:13.0:1
#000000
#727272
Pass
h3 Free Shipping4.37:13.0:1
#000000
#727272
Pass
h3 Quality Products4.37:13.0:1
#000000
#727272
Pass
h3 Great Value4.37:13.0:1
#000000
#727272
Pass
h3 Giving Back4.37:13.0:1
#000000
#727272
Pass
title Bearbottom | Everyda…1.16:14.5:1
#000000
#161616
Fail
a Skip to content1.87:14.5:1
#000000
#3B3B3B
Fail
a Accessibility Statem…4.37:14.5:1
#000000
#727272
Fail
span Pause slideshow2.87:14.5:1
#000000
#5A564D
Fail
span Play slideshow1.13:14.5:1
#000000
#14130D
Fail
span BUILT FOR THE IN-BET…1.10:14.5:1
#000000
#10100C
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.

A+
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" MAIN CONTENTINFO footer
A+
Heading Hierarchy
15 headings
PASS
15 headings
Info::
Single H1 present
  • H1 Bearbottom Clothing
  • H2 BEST SELLERS
  • H2 NEW ARRIVALS
  • H2 BUNDLE & SAVE
  • H2 One Item Purchased = 1 Meal Donated
  • H2 OVER 35,000 5-STAR REVIEWS
  • H3 Free Shipping
  • H3 Quality Products
  • H3 Great Value
  • H3 Giving Back
  • H2 JOIN THE ADVENTURE @bearbottomclothing
  • H2 Shop
  • H2 Support
  • H2 More Info
  • H2 Join the newsletter
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
4 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 4 all-caps heading(s)
A
Alt Text Quality
All 79 images OK
PASS
All 79 images OK
Info::
5 image(s) with alt text over 125 characters
Info::
12 decorative image(s) correctly marked
Info::
62 image(s) with good alt text
79 images 62 good alt text 12 decorative
IssueCount
too long5 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#SearchsearchSearchfor/id
#Email-1f1277f9-2eff-4c26-a783-2dabae56aa6aemailEnter your emailfor/id
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A
Tabindex Anti-Patterns
0 positive, 3 -1-on-focusable
PASS
0 positive, 3 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 27 passed
PASS
93

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

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.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
footer.site-footer > div.page-width > p.footer__small-text > a footer.site-footer > div.page-width > p.footer__small-text > 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
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
Sand Dune div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Black div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Charcoal Grey div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Crocodile div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Shadow div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Blue Jay div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
Dark Sage div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Navy div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Grey div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Black div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Camel div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Flint div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
Dark Clay div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Cactus div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Ash Grey div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Navy div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Cocoa div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Black div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
Grey div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Black div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Navy div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Dark Sage div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Desert div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Camel div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
Bone div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Duck Green div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
Black div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Shadow div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
Duck Green div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Shadow div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Bone div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Black div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
Black div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Bone div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Shadow div.grid > div.grid__item > div.grid-product__colors > a.color-swatch
Duck Green div.grid > div.grid__item > div.grid-product__colors > a.color-swatch

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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○`<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
○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.
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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.

Send Feedback