Accessibility

F

Heading Hierarchy

Action

44 headings, 7 skip(s)

FIX

44 headings, 7 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H1 → H3 (missing H2)

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.

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: H1 → H3 (missing H2)

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

Heading level skipped: H2 → H5 (missing H3)

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

H4 BUY PSILOCYBIN MUSHROOM IN THE USA, CANADA, EUROPE AND UK. YOUR #1 MUSHROOM DISPENSARY
H3 BUY PSILOCYBIN MUSHROOM IN THE USA, CANADA, EUROPE AND UK. YOUR #1 MUSHROOM DISPENSARY
H1 BUY PSILOCYBIN MUSHROOM IN THE USA, CANADA, EUROPE AND UK. YOUR #1 MUSHROOM DISPENSARY
H3 BUY PREMIUM HIGH QUALITY DMT ONLINE skipped
H2 BUY PREMIUM MUSHROOMS ONLINE | DRIED MUSHROOMS | FUNCTIONAL MUSHROOMS | GOURMET MUSHROOMS | MUSHROOM CAPSULES | SPECIALTY MUSHROOM PRODUCTS
H2 DRIED MUSHROOMS
H3 BUY MUSHROOMS CHOCOLATE BAR CANADA | MUSHROOMS EDIBLES CANADA
H3 MUSHROOM CHOCOLATE FOR SALE | BUY MAGIC SHROOM CANADA
H2 BUY MUSHROOM GUMMIES ONLINE
H4 QUALITIIES OF GOOD CHOCOLATE MUSHROOMS skipped
H2 MUSHROOM CHOCOLATE BARS
H4 MUSHROOM TEA FOR SALE skipped
H2 MUSHROOM TEA
H4 BUY SHROOMS CAPSULE skipped
H2 MUSHROOM CAPSULES
H4 MICRODOSE SHROOMS FOR SALE skipped
H2 MICRODOSE SHROOMS
H2 RELATED PRODUCTS
H2 …..OUR DMT PRODUCTS …..
H2 …..OUR LSD PRODUCTS …..
H2 ❓ FREQUENTLY ASKED QUESTIONS
H1 🍄 HOW TO PLACE AN ORDER duplicate H1
H3 Worldwide Shipping skipped
H3 Order Tracking
H3 Buy Mushrooms For Sale Canada Safely & Discreetly Delivered | Shroom Delivery
H3 Psychedelic Mushrooms For Sale Canada – Best place to buy psychedelics Canada
H3 BUY MUSHROOM CAPSULES IN CANADA | BUY PSYCHEDELICS CANADA
H2 SHIPPING ACROSS CANADA & WORLDWIDE
H2 Learn About Psilocybin Mushrooms
H2 Mushroom Gummies in Canada
H2 Choosing the Right Mushroom Product
H2 …..Why Customers Choose Us…..
H2 Get 15% OFF Orders Above $300
H2 Best Selling Products
H2 …..Latest From Our Learning Corner…..
H5 Learn About Psilocybin Mushrooms in Canada | Complete Guide to Magic Mushroom Varieties & Research skipped
H5 Mushroom Gummies in Canada | Everything You Need to Know About Mushroom Gummies
H5 Mushroom Products in Canada | Comparing Gummies, Capsules, Chocolates & More
H2 …..What Our Customers Are Saying…..
H2 …..How to Order…..
H1 🍄 HOW TO PLACE AN ORDER duplicate H1
H2 🍄 READY TO EXPLORE MORE?
H3 🌿 BUYMAGICSHROOM.COM
H3 Login

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

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

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

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

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

Form Accessibility

2 of 7 controls have issues

REVIEW

2 of 7 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email" name="your-email">

5 control(s) properly labeled

7 controls

5 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#woocommerce-product-search-field-0	search	Search for:	for/id
#woocommerce-product-search-field-1	search	Search for:	for/id
#username	text	Username or email address *	for/id
#password	password	Password *	for/id
#rememberme	checkbox		none
your-email	email	(Your Email (required))	placeholder only
input	submit	(none)	none

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

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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B

Link & Button Quality

3 issue(s) across 507 links and 21 buttons

REVIEW

3 issue(s) across 507 links and 21 buttons

2 link(s) with no accessible text

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

Got: https://shroomnearby.com/product-category/buy-shrooms-capsules/; https://shroomnearby.com/product-category/mushrooms-grow-kit/

1 link(s) with generic text

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

Got: https://shroomnearby.com/product-category/dmt-products/ ("more")

504 link(s) with descriptive text

507 links

2 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://shroomnearby.com/product-categor…	more	generic text	Replace with descriptive text
Before: more Suggested: Dmt Products
https://shroomnearby.com/product-categor…	(empty)	empty	Add link text or aria-label
https://shroomnearby.com/product-categor…	(empty)	empty	Add link text or aria-label

525 links and buttons have descriptive text

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

https://shroomnearby.com/product-category/buy-shrooms-capsules/; https://shroomnearby.com/product-category/mushrooms-grow-kit/

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

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

https://shroomnearby.com/product-category/dmt-products/ ("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

C

Mobile Keyboard & Autofill

Action

3/5 eligible field(s) missing autocomplete or inputmode

REVIEW

3/5 eligible field(s) missing autocomplete or inputmode

3 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.

Got: <input type="search" name="s" id="woocommerce-product-search-field-0">, <input type="email" name="your-email">, <input type="search" name="s" id="woocommerce-product-search-field-1">

C

Tap Target Adequacy

Action

4 tap target(s) too small or too close together

REVIEW

4 tap target(s) too small or too close together

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

C

Mobile-Readable Font Sizes

Action

80% of visible text renders at >= 12 CSS px (27 below threshold)

REVIEW

80% of visible text renders at >= 12 CSS px (27 below threshold)

27 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: <p> 10.8px ("Dried magic mushrooms"); <a> 11.5px ("Select options"); <p> 10.8px ("Dried magic mushrooms"); <a> 11.5px ("Select options"); <p> 10.8px ("Dried magic mushrooms").

C

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 14 fail WCAG AA

REVIEW

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

6 pass 14 fail WCAG AA 1 pass AA only

h2 Why Customers Choose Us

2.06:1

#000000

on

#414141

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get 15% OFF Orders Above $300

2.06:1

#000000

on

#414141

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest From Our Learning Corner

2.06:1

#000000

on

#414141

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What Our Customers Are Saying

2.06:1

#000000

on

#414141

needs 3.0:1 (large text)

24px · bottom of viewport

h2 🍄 READY TO EXPLORE MORE?

2.06:1

#000000

on

#414141

needs 3.0:1 (large text)

24px · bottom of viewport

h3 🌿 BUYMAGICSHROOM.COM

1.23:1

#145A2B

on

#414141

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

h3 Login

2.06:1

#000000

on

#414141

needs 3.0:1 (large text)

19px · bottom of viewport

title Home - SHROOM NEARBY

2.86:1

#000000

on

#2B6212

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.55:1

#000000

on

#2E2E2E

needs 4.5:1 (normal text)

16px · top of page (header area)

strong ✈ Free express shipping on orders $300…

1.55:1

#000000

on

#2E2E2E

needs 3.0:1 (large text)

16px · top of page (header area)

strong ✈ Free express shipping on orders $300…

1.66:1

#000000

on

#363231

needs 3.0:1 (large text)

16px · top of page (header area)

label Search for:

2.23:1

#000000

on

#494548

needs 4.5:1 (normal text)

16px · above the fold

a Home

3.45:1

#000000

on

#636262

needs 4.5:1 (normal text)

16px · above the fold

a Shop

3.12:1

#000000

on

#5E5B5B

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
h1 🍄 HOW TO PLACE AN…	10.21:1	3.0:1	#FFFFFF	#414141	Pass
h1 🍄 HOW TO PLACE AN…	10.21:1	3.0:1	#FFFFFF	#414141	Pass
h2 ❓ FREQUENTLY ASKED…	3.10:1	3.0:1	#16A34A	#414141	Pass
h2 SHIPPING ACROSS CANA…	10.21:1	3.0:1	#FFFFFF	#414141	Pass
h2 Why Customers Choose…	2.06:1	3.0:1	#000000	#414141	Fail
h2 Get 15% OFF Orders A…	2.06:1	3.0:1	#000000	#414141	Fail
h2 Latest From Our Lear…	2.06:1	3.0:1	#000000	#414141	Fail
h2 What Our Customers A…	2.06:1	3.0:1	#000000	#414141	Fail
h2 🍄 READY TO EXPLOR…	2.06:1	3.0:1	#000000	#414141	Fail
h3 Worldwide Shipping	10.21:1	3.0:1	#FFFFFF	#414141	Pass
h3 Order Tracking	10.21:1	3.0:1	#FFFFFF	#414141	Pass
h3 🌿 BUYMAGICSHROOM.…	1.23:1	3.0:1	#145A2B	#414141	Fail
h3 Login	2.06:1	3.0:1	#000000	#414141	Fail
title Home - SHROOM NEARBY	2.86:1	4.5:1	#000000	#2B6212	Fail
a Skip to content	1.55:1	4.5:1	#000000	#2E2E2E	Fail
strong ✈ Free express shi…	1.55:1	3.0:1	#000000	#2E2E2E	Fail
strong ✈ Free express shi…	1.66:1	3.0:1	#000000	#363231	Fail
label Search for:	2.23:1	4.5:1	#000000	#494548	Fail
a Home	3.45:1	4.5:1	#000000	#636262	Fail
a Shop	3.12:1	4.5:1	#000000	#5E5B5B	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.

B

Lighthouse Accessibility Audits

Score 83/100 — 6 failing, 28 passed

REVIEW

83

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
BUY PREMIUM HIGH QUALITY DMT ONLINE DMT for sale Online Less Costly and Safe D… `div.slider > div.flickity-viewport > div.flickity-slider > div#banner-2083843694`

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.

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
$50.00 `li > del > span.woocommerce-Price-amount > bdi`
CONTACT US `div.menu-secondary-container > ul#menu-secondary > li#menu-item-3852 > a`
BLOG `div.menu-secondary-container > ul#menu-secondary > li#menu-item-2647 > a`
ABOUT US `div.menu-secondary-container > ul#menu-secondary > li#menu-item-3853 > a`
REFUND AND RETURNS POLICY `div.menu-secondary-container > ul#menu-secondary > li#menu-item-3854 > a`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
e `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
Dried `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
s `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
. `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
, `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
Gummies `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
Tea `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
, `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
more `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
. `div.col-inner > div#text-3891831439 > p.call-to-action__subtitle > a`
at `div.stk-block-content > div#what-are-peptides > p > a`
s `div.stk-block-content > div#what-are-peptides > p > a`
. `div.stk-block-content > div#what-are-peptides > p > a`
capsules `div#col-957238388 > div.col-inner > p > a`
Learning Center `section#section_1446632157 > div.section-content > p > a`
Everyday `main#main > div#content > p > a`
how `main#main > div#content > p > a`

These are opportunities to improve the legibility of your content.

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
QUALITIIES OF GOOD CHOCOLATE MUSHROOMS `section#section_1572301584 > div.section-content > div#text-39877661 > h4`
MUSHROOM TEA FOR SALE `section#section_1572301584 > div.section-content > div#text-2618682891 > h4`
BUY SHROOMS CAPSULE `section#section_1572301584 > div.section-content > div#text-735343455 > h4`
MICRODOSE SHROOMS FOR SALE `section#section_1572301584 > div.section-content > div#text-604858309 > h4`
Learn About Psilocybin Mushrooms in Canada \| Complete Guide to Magic Mushroom V… `div.box > div.box-text > div.box-text-inner > h5.post-title`

These are opportunities to improve keyboard navigation in your application.

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#col-779218918 > div.col-inner > div#image_251381391 > a `div#col-779218918 > div.col-inner > div#image_251381391 > a`
div#col-14226251 > div.col-inner > div#image_125102254 > a `div#col-14226251 > div.col-inner > div#image_125102254 > 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
CONTACT US `div.menu-secondary-container > ul#menu-secondary > li#menu-item-3852 > a`
BLOG `div.menu-secondary-container > ul#menu-secondary > li#menu-item-2647 > a`
ABOUT US `div.menu-secondary-container > ul#menu-secondary > li#menu-item-3853 > a`
REFUND AND RETURNS POLICY `div.menu-secondary-container > ul#menu-secondary > li#menu-item-3854 > a`

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

●Input buttons have discernible text.

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

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●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

●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

●`[lang]` attributes have a valid value

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

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

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

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

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

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

○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

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

A

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 139 chars

Got: 1 >120-char heading(s)

27 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: 27 all-caps heading(s)

A

Alt Text Quality

All 143 images OK

PASS

All 143 images OK

26 image(s) with alt text over 125 characters

8 decorative image(s) correctly marked

109 image(s) with good alt text

143 images 109 good alt text 8 decorative

Issue	Count
too long	26 image(s)

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "username" should use type="email" (currently type="text")

Field name "username" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.

A

Form Input Quality

1 input-semantic issue(s) across 7 form control(s)

PASS

1 input-semantic issue(s) across 7 form control(s)

1 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="your-email">.

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - SHROOM NEARBY ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.