Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #6108ce

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Link & Button Quality

1 issue(s) across 291 links and 45 buttons

REVIEW

1 issue(s) across 291 links and 45 buttons

7 link(s) open in new tab without warning

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

Got: https://storeleads.app/reports; https://storeleads.app/reports; https://w3techs.com/technologies/details/cm-wordpress; https://www.facebook.com/woocommerce; https://www.x.com/woocommerce; https://www.instagram.com/woocommerce; https://www.linkedin.com/company/woocommerce/

1 button(s) with no accessible text

284 link(s) with descriptive text

291 links

0 empty

0 generic text

7 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://storeleads.app/reports	Store Leads	new tab	Add '(opens in new tab)' to text
https://storeleads.app/reports	Store Leads	new tab	Add '(opens in new tab)' to text
https://w3techs.com/technologies/details…	W3Techs	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/woocommerce	Follow us on Facebook	new tab	Add '(opens in new tab)' to text
https://www.x.com/woocommerce	Follow us on X	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/woocommerce	Follow us on Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/woocomm…	Follow us on LinkedIn	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

328 links and buttons have descriptive text

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

https://storeleads.app/reports; https://storeleads.app/reports; https://w3techs.com/technologies/details/cm-wordpress; https://www.facebook.com/woocommerce; https://www.x.com/woocommerce; https://www.instagram.com/woocommerce; https://www.linkedin.com/company/woocommerce/

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Landmark Structure

16 landmarks

PASS

16 landmarks

<main> landmark present

13 <nav> landmark(s) found

10 of 13 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+

Heading Hierarchy

18 headings

PASS

18 headings

Single H1 present

H1 The most flexible ecommerce platform
H2 The most-trusted ecommerce platform
H2 How can Woo help you?
H3 Sell with WooCommerce
H3 Sell with WooCommerce
H3 Build stores for others
H3 Add new features
H2 The brands you love, love Woo
H2 Real WooCommerce results
H3 Nutribullet: A site that doesn’t blend in
H3 House of Malt: A double shot of success
H3 Dan-O’s Seasoning: A spicy multichannel success
H2 Take control of your success with WooCommerce
H3 Sell
H3 Marketplace
H3 Build
H3 Resources
H3 woo

A+

Alt Text Quality

All 181 images OK

PASS

All 181 images OK

49 decorative image(s) correctly marked

132 image(s) with good alt text

181 images 132 good alt text 49 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#wccom-header-search__q--mobile	search	Find extensions, themes, guides, and more	for/id
#wccom-header-search__q--desktop	search	Find extensions, themes, guides, and more	for/id

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 - WooCommerce ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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)

Element	Ratio	Required	FG	BG	Result
h1 The most flexible ec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The most-trusted eco…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 How can Woo help you…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The brands you love,…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Real WooCommerce res…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Take control of your…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sell with WooCommerc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sell with WooCommerc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Build stores for oth…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Add new features	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Nutribullet: A site …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 House of Malt: A dou…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Dan-O’s Seasoning:…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sell	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Marketplace	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Build	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 woo	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title WooCommerce	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to navigation	21.00:1	4.5:1	#000000	#FFFFFF	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.

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 30 passed

PASS

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.

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
“WooCommerce allowed us to go from something as simple as we needed in the begi… `div.wp-block-wccom-effect-block > div.wp-block-group > div.wp-block-group > p.has-x-large-font-size`
Ryan Fertig Senior Marketing Activation Director, Dan-O’s Seasoning `div.wp-block-wccom-effect-block > div.wp-block-group > div.wp-block-group > p.has-medium-large-font-size`

These are opportunities to improve the legibility of your content.

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
Brodo Broth Co `div.wp-block-wccom-gallery-slider > div.wccom-gallery-slider__footer > div.wccom-gallery-slider__indicators > button.wccom-gallery-slider__indicator`
Grüum `div.wp-block-wccom-gallery-slider > div.wccom-gallery-slider__footer > div.wccom-gallery-slider__indicators > button.wccom-gallery-slider__indicator`
Boost Oxygen `div.wp-block-wccom-gallery-slider > div.wccom-gallery-slider__footer > div.wccom-gallery-slider__indicators > button.wccom-gallery-slider__indicator`

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○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

○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

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