Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 1 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

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.

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 ✗

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

A+

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

28 headings

PASS

28 headings

Single H1 present

H1 Premium WooCommerce & WordPress themes for lightning-fast online stores
H2 All-in-one toolkit for eCommerce creators
H3 Lightning fast performance
H2 Google Lighthouse
H3 Fully customizable design
H3 Image Optimizer
H3 WooCommerce optimized
H3 One-Click Demo Import
H2 Create a website in one click for…
H2 What store owners say about XTemos
H3 JustusBope
H3 rproxy
H3 MSUMSUZZ
H3 planetorlando
H3 bontytech
H3 ozi_productions
H3 redontota
H3 a_zyabkin
H3 MBCtech
H2 Frequently asked questions
H3 Learn from XTemos Blog
H3 How we built the Fashion 2 demo website with WoodMart
H3 How we built the Electronics 3 demo website with WoodMart
H3 WoodMart 8.4 update
H3 Start building your high-converting store today!
H2 Powerful tools for growing your business.
H2 Resources
H2 Social Links

A+

Alt Text Quality

All 53 images OK

PASS

All 53 images OK

50 decorative image(s) correctly marked

3 image(s) with good alt text

53 images 3 good alt text 50 decorative

All images have appropriate alt text.

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#username	text	Username or email address *Required	for/id
#password	password	Password *Required	for/id
rememberme	checkbox		none
#g-recaptcha-response-100000	textarea	(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

Link & Button Quality

106 links, 2 buttons — all OK

PASS

106 links, 2 buttons — all OK

15 link(s) open in new tab without warning

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

Got: https://www.facebook.com/sharer/sharer.php?u=https://xtemos.com/how-we-built-…; https://x.com/share?url=https://xtemos.com/how-we-built-the-fashion-2-demo-we…; https://pinterest.com/pin/create/button/?url=https://xtemos.com/how-we-built-…; https://www.linkedin.com/shareArticle?mini=true&url=https://xtemos.com/how-we…; https://telegram.me/share/url?url=https://xtemos.com/how-we-built-the-fashion…; https://www.facebook.com/sharer/sharer.php?u=https://xtemos.com/how-we-built-…; https://x.com/share?url=https://xtemos.com/how-we-built-the-electronics-3-dem…; https://pinterest.com/pin/create/button/?url=https://xtemos.com/how-we-built-…; https://www.linkedin.com/shareArticle?mini=true&url=https://xtemos.com/how-we…; https://telegram.me/share/url?url=https://xtemos.com/how-we-built-the-electro… (+5 more)

91 link(s) with descriptive text

106 links

0 empty

0 generic text

15 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://xtemos.com/	Site logo	img no alt	Add alt attribute to the image
https://xtemos.com/	Site logo	img no alt	Add alt attribute to the image
#	Gutenberg	img no alt	Add alt attribute to the image
#	Elementor	img no alt	Add alt attribute to the image
#	WPBakery	img no alt	Add alt attribute to the image
https://www.facebook.com/sharer/sharer.p…	Facebook social link	new tab	Add '(opens in new tab)' to text
https://x.com/share?url=https://xtemos.c…	X social link	new tab	Add '(opens in new tab)' to text
https://pinterest.com/pin/create/button/…	Pinterest social link	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/shareArticle?mi…	Linkedin social link	new tab	Add '(opens in new tab)' to text
https://telegram.me/share/url?url=https:…	Telegram social link	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/sharer/sharer.p…	Facebook social link	new tab	Add '(opens in new tab)' to text
https://x.com/share?url=https://xtemos.c…	X social link	new tab	Add '(opens in new tab)' to text
https://pinterest.com/pin/create/button/…	Pinterest social link	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/shareArticle?mi…	Linkedin social link	new tab	Add '(opens in new tab)' to text
https://telegram.me/share/url?url=https:…	Telegram social link	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/sharer/sharer.p…	Facebook social link	new tab	Add '(opens in new tab)' to text
https://x.com/share?url=https://xtemos.c…	X social link	new tab	Add '(opens in new tab)' to text
https://pinterest.com/pin/create/button/…	Pinterest social link	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/shareArticle?mi…	Linkedin social link	new tab	Add '(opens in new tab)' to text
https://telegram.me/share/url?url=https:…	Telegram social link	new tab	Add '(opens in new tab)' to text

93 links and buttons have descriptive text

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

https://www.facebook.com/sharer/sharer.php?u=https://xtemos.com/how-we-built-…; https://x.com/share?url=https://xtemos.com/how-we-built-the-fashion-2-demo-we…; https://pinterest.com/pin/create/button/?url=https://xtemos.com/how-we-built-…; https://www.linkedin.com/shareArticle?mini=true&url=https://xtemos.com/how-we…; https://telegram.me/share/url?url=https://xtemos.com/how-we-built-the-fashion…; https://www.facebook.com/sharer/sharer.php?u=https://xtemos.com/how-we-built-…; https://x.com/share?url=https://xtemos.com/how-we-built-the-electronics-3-dem…; https://pinterest.com/pin/create/button/?url=https://xtemos.com/how-we-built-…; https://www.linkedin.com/shareArticle?mini=true&url=https://xtemos.com/how-we…; https://telegram.me/share/url?url=https://xtemos.com/how-we-built-the-electro… (+5 more)

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

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 - XTemos ✓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 Premium WooCommerce …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 for lightning-fast o…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 All-in-one toolkit f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Create a website in …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What store owners sa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Frequently asked que…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Powerful tools for g…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Social Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Lightning fast perfo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Fully customizable d…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Image Optimizer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 WooCommerce optimize…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 One-Click Demo Impor…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 JustusBope	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 rproxy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 MSUMSUZZ	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 planetorlando	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 bontytech	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ozi_productions	21.00:1	3.0: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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 27 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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●Image elements have `[alt]` attributes

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●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

○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

○Buttons have an accessible name

○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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.