Accessibility

D

Heading Hierarchy

Action

21 headings, 4 skip(s)

FIX

21 headings, 4 skip(s)

Single H1 present

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 → H6 (missing H3)

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.

Heading level skipped: H2 → H4 (missing H3)

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

H1 We create WP themes that take the Customizer to the next level
H2 Our Themes
H4 One Page Drag & Drop Theme skipped
H4 Multi-purpose Drag & Drop Theme
H4 Materialis Design Drag & Drop Theme
H4 Full Screen Drag & Drop Theme
H4 Business Drag & Drop Theme
H2 Our Happy Clients
H6 @SwirishNinja skipped
H6 @ilariacalutas
H6 @1inhimministries
H6 @jonjon1989
H6 @adtiplyme
H6 @katikakatika
H2 Our Awesome Support Team
H5 14 DAYS MONEY BACK GUARANTEE skipped
H5 CONSTANT UPDATES
H5 AMAZING SUPPORT
H5 CONTACT US
H2 Ready to get started?
H4 ExtendThemes skipped

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

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

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

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation

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.

C

Landmark Structure

Action

No landmarks

REVIEW

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

Skip navigation link present

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

C

Alt Text Quality

Action

5 of 8 images have issues

REVIEW

5 of 8 images have issues

5 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 decorative image(s) correctly marked

2 image(s) with good alt text

8 images 2 good alt text 1 decorative 5 missing

Issue	Count
missing	5 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

Link & Button Quality

1 issue(s) across 46 links and 1 buttons

REVIEW

1 issue(s) across 46 links and 1 buttons

1 link(s) with no accessible text

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

Got: #

18 link(s) open in new tab without warning

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

Got: http://onepageexpress.com; http://onepageexpress.com; https://extendthemes.com/mesmerize; https://extendthemes.com/mesmerize; https://extendthemes.com/materialis; https://extendthemes.com/materialis; https://extendthemes.com/highlight; https://extendthemes.com/highlight; https://extendthemes.com/empowerwp-pro; https://extendthemes.com/empowerwp-pro (+8 more)

27 link(s) with descriptive text

46 links

1 empty

0 generic text

18 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
http://onepageexpress.com	VIEW THEME	new tab	Add '(opens in new tab)' to text
http://onepageexpress.com	ONE PAGE EXPRESS THEME	new tab	Add '(opens in new tab)' to text
https://extendthemes.com/mesmerize	VIEW THEME	new tab	Add '(opens in new tab)' to text
https://extendthemes.com/mesmerize	MESMERIZE THEME	new tab	Add '(opens in new tab)' to text
https://extendthemes.com/materialis	VIEW THEME	new tab	Add '(opens in new tab)' to text
https://extendthemes.com/materialis	MATERIALIS THEME	new tab	Add '(opens in new tab)' to text
https://extendthemes.com/highlight	VIEW THEME	new tab	Add '(opens in new tab)' to text
https://extendthemes.com/highlight	HIGHLIGHT THEME	new tab	Add '(opens in new tab)' to text
https://extendthemes.com/empowerwp-pro	VIEW THEME	new tab	Add '(opens in new tab)' to text
https://extendthemes.com/empowerwp-pro	EMPOWERWP THEME	new tab	Add '(opens in new tab)' to text
https://wordpress.org/support/topic/grea…	See on WordPress.org	new tab	Add '(opens in new tab)' to text
https://wordpress.org/support/topic/grea…	See on WordPress.org	new tab	Add '(opens in new tab)' to text
https://wordpress.org/support/topic/exce…	See on WordPress.org	new tab	Add '(opens in new tab)' to text
https://wordpress.org/support/topic/i-ca…	See on WordPress.org	new tab	Add '(opens in new tab)' to text
https://wordpress.org/support/topic/dont…	See on WordPress.org	new tab	Add '(opens in new tab)' to text
https://wordpress.org/support/topic/supe…	See on WordPress.org	new tab	Add '(opens in new tab)' to text
http://onepageexpress.com	GET ONE PAGE EXPRESS	new tab	Add '(opens in new tab)' to text
#	<img src="https://extendtheme…	img no alt	Add alt attribute to the image
https://extendthemes.com/cookies-policy/	use of cookies	new tab	Add '(opens in new tab)' to text

28 links and buttons have descriptive text

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

#

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

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

http://onepageexpress.com; http://onepageexpress.com; https://extendthemes.com/mesmerize; https://extendthemes.com/mesmerize; https://extendthemes.com/materialis; https://extendthemes.com/materialis; https://extendthemes.com/highlight; https://extendthemes.com/highlight; https://extendthemes.com/empowerwp-pro; https://extendthemes.com/empowerwp-pro (+8 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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 6 pass AA only

h2 Our Happy Clients

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our Awesome Support Team

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to get started?

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 We create WP themes …	6.64:1	3.0:1	#000000	#5D8CFD	Pass
h2 Our Themes	5.97:1	3.0:1	#000000	#697DFE	Pass
h2 Our Happy Clients	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Our Awesome Support …	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Ready to get started…	1.72:1	3.0:1	#000000	#2E363F	Fail
title Extend Themes: drag …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Testimonials	8.14:1	4.5:1	#000000	#47A6FD	Pass
a Blog	7.75:1	4.5:1	#000000	#4CA0FD	Pass
a Members Area	7.39:1	4.5:1	#000000	#519AFD	Pass
a VIEW THEMES	7.05:1	4.5:1	#000000	#5694FD	Pass
a Check out our themes	6.27:1	4.5:1	#000000	#6484FE	Pass
a VIEW THEME	5.70:1	4.5:1	#000000	#6F76FE	Pass
h4 One Page Drag & Drop…	5.49:1	3.0:1	#000000	#7470FE	Pass
a ONE PAGE EXPRESS THE…	5.31:1	4.5:1	#000000	#796AFE	Pass
a VIEW THEME	5.14:1	4.5:1	#000000	#7E64FE	Pass
h4 Multi-purpose Drag &…	5.00:1	3.0:1	#000000	#835EFE	Pass
a MESMERIZE THEME	4.87:1	4.5:1	#000000	#8858FE	Pass
a VIEW THEME	6.14:1	4.5:1	#000000	#9F6EFE	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.

B

Lighthouse Accessibility Audits

Score 82/100 — 5 failing, 18 passed

REVIEW

82

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
Check out our themes `div.header-content > div.align-holder > div.header-buttons-wrapper > a.button`
See on WordPress.org `div.row > div.col-xs-12 > div.card > a`
See on WordPress.org `div.row > div.col-xs-12 > div.card > a`
See on WordPress.org `div.row > div.col-xs-12 > div.card > a`
See on WordPress.org `div.row > div.col-xs-12 > div.card > a`
See on WordPress.org `div.row > div.col-xs-12 > div.card > a`
See on WordPress.org `div.row > div.col-xs-12 > div.card > a`
CONTACT US `div.gridContainer > div.row > div.col-xs-12 > a.button`
GET ONE PAGE EXPRESS `div.gridContainer > div.row > div > a.button`
GET MESMERIZE `div.gridContainer > div.row > div > a.button`
GET MATERIALIS `div.gridContainer > div.row > div > a.button`
GET EMPOWERWP `div.gridContainer > div.row > div > a.button`
GET HIGHLIGHT `div.gridContainer > div.row > div > a.button`
© 2026 ExtendThemes. `div.row > div.col-xs-12 > div.muted > p.copyright`
Home `div.horizontal_footer_menu > ul#footer_menu > li#menu-item-416 > a`
Themes `div.horizontal_footer_menu > ul#footer_menu > li#menu-item-417 > a`
Support `div.horizontal_footer_menu > ul#footer_menu > li#menu-item-419 > a`
Blog `div.horizontal_footer_menu > ul#footer_menu > li#menu-item-491 > a`
License `div.horizontal_footer_menu > ul#footer_menu > li#menu-item-415 > a`
Terms `div.horizontal_footer_menu > ul#footer_menu > li#menu-item-783 > a`
Privacy Policy `div.horizontal_footer_menu > ul#footer_menu > li#menu-item-790 > a`
Members Area `div.horizontal_footer_menu > ul#footer_menu > li#menu-item-13864 > a`
I ACCEPT `body.home > div#eu-cookie-bar > button#euCookieAcceptWP`

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
One Page Drag & Drop Theme `div.col-xs-12 > div.card > div.space-bottom > h4`
@SwirishNinja `div.row > div.col-xs-12 > div.card > h6`
14 DAYS MONEY BACK GUARANTEE `div.col-xs-12 > div.row > div.col-xs-12 > h5`
ExtendThemes `div.row > div.col-xs-12 > div.footer-logo > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded `div.card > div.contentswap-effect > div.initial-image > img.lazyloaded`
div.card > div.contentswap-effect > div.initial-image > img.lazyload `div.card > div.contentswap-effect > div.initial-image > img.lazyload`
div.card > div.contentswap-effect > div.initial-image > img.lazyload `div.card > div.contentswap-effect > div.initial-image > img.lazyload`
div.card > div.contentswap-effect > div.initial-image > img.lazyload `div.card > div.contentswap-effect > div.initial-image > img.lazyload`
div.card > div.contentswap-effect > div.initial-image > img.lazyload `div.card > div.contentswap-effect > div.initial-image > img.lazyload`

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.navigation-wrapper > div.row > div.main_menu_col > a `div.navigation-wrapper > div.row > div.main_menu_col > a`
div#page > div#page-content > div.content > a `div#page > div#page-content > div.content > 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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.touch-enabled `html.touch-enabled`

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

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

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

●Buttons have an accessible name

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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.