Skip to content
https://oberlo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
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
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::
1 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 1 <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.
B
Alt Text Quality
3 of 24 images have issues
REVIEW
3 of 24 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
2 image(s) with filename as alt text
Info::
3 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
24 images 18 good alt text 3 decorative 2 generic 1 missing
IssueCount
missing1 image(s)
filename2 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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="footer-lang-select-footer">; <select id="footer-lang-select-footer">
2 controls
0 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#footer-lang-select-footerselect(none)none
#footer-lang-select-footerselect(none)none

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

<select id="footer-lang-select-footer">; <select id="footer-lang-select-footer">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Oberlo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
13 icon(s) detected
REVIEW
13 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 Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 84/100 — 3 failing, 23 passed
REVIEW
84

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
div.relative > div#sticky-global-header > header#main-header > div.flex div.relative > div#sticky-global-header > header#main-header > div.flex

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > details#dropdown-nav > summary.list-none > button.relative div.flex > details#dropdown-nav > summary.list-none > button.relative

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
section.grid > article.col-span-4 > picture.bg-cover > img.absolute section.grid > article.col-span-4 > picture.bg-cover > img.absolute

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
●`[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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[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
○`[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
○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
○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.
○`[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.
○Identical links have the same purpose.
○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.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 menu" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
33 headings
PASS
33 headings
Info::
Single H1 present
  • H1 Fulfill your dropshipping dreams
  • H2 Our picks
  • H3 The Ultimate Guide to Dropshipping Products on TikTok & Instagram
  • H2 Master dropshipping on TikTok and Instagram. Discover the winning products for organic marketing, understand your targ...
  • H3 How to Dropship More Sustainably (and 9 Products to Help You Get Started)
  • H3 23 Best Small Business Website Examples to Inspire You
  • H3 What Is Dropshipping: A Detailed Breakdown for 2025
  • H3 The Ultimate Guide to Dropshipping on Shopify (2025)
  • H3 38 Passive Income Ideas To Build Wealth in 2024
  • H3 The 200 Best Inspirational Business Quotes (2024)
  • H2 Stories
  • H3 The Ultimate Guide to Dropshipping Products on TikTok & Instagram
  • H3 How to Dropship More Sustainably (and 9 Products to Help You Get Started)
  • H3 23 Best Small Business Website Examples to Inspire You
  • H3 What Is Dropshipping: A Detailed Breakdown for 2025
  • H2 Podcast
  • H3 Start yours
  • H2 Latest episode
  • H3 How This Couple Created a Sustainable Business While Working Full-Time
  • H2 Your life
  • H3 The Ultimate Guide to Dropshipping Products on TikTok & Instagram
  • H2 Master dropshipping on TikTok and Instagram. Discover the winning products for organic marketing, understand your targ...
  • H3 How to Dropship More Sustainably (and 9 Products to Help You Get Started)
  • H3 23 Best Small Business Website Examples to Inspire You
  • H3 What Is Dropshipping: A Detailed Breakdown for 2025
  • H2 Dropshipping
  • H3 This is business unusual
  • H3 23 Best Small Business Website Examples to Inspire You
  • H3 What Is Dropshipping: A Detailed Breakdown for 2025
  • H2 Build your business
  • H2 Stories
  • H2 Your life
  • H2 Free Business Tools
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 Fulfill your dropshi…16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Our picks16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Master dropshipping …16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Stories16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Podcast16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Latest episode16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Your life16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Master dropshipping …16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Dropshipping16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Build your business16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Stories16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Your life16.71:13.0:1
#000000
#B3EFFF
Pass
h2 Free Business Tools16.71:13.0:1
#000000
#B3EFFF
Pass
h3 The Ultimate Guide t…16.71:13.0:1
#000000
#B3EFFF
Pass
h3 How to Dropship More…16.71:13.0:1
#000000
#B3EFFF
Pass
h3 23 Best Small Busine…16.71:13.0:1
#000000
#B3EFFF
Pass
h3 What Is Dropshipping…16.71:13.0:1
#000000
#B3EFFF
Pass
h3 The Ultimate Guide t…16.71:13.0:1
#000000
#B3EFFF
Pass
h3 38 Passive Income Id…16.71:13.0:1
#000000
#B3EFFF
Pass
h3 The 200 Best Inspira…16.71:13.0:1
#000000
#B3EFFF
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