Skip to content
https://catchthemes.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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.
C
Landmark Structure
Action
47 landmarks
REVIEW
47 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary Menu" MAIN (missing!) CONTENTINFO footer

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

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

B
Heading Hierarchy
49 headings, 1 skip(s)
REVIEW
49 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Catch Themes
  • H1 Free & Premium WordPress themes for a diverse range of Web Publishers duplicate H1
  • H2 Design Visually with Modern Block Themes
  • H2 Bizboost Pro
  • H2 Photofocus Blocks Pro
  • H3 High Performance Pro
  • H3 High Performance
  • H3 Soundscape
  • H3 Soundscape Pro
  • H3 Euphony Blocks Pro
  • H3 Euphony Blocks
  • H2 Premium WordPress Themes
  • H3 Catch Responsive Pro
  • H3 Fotografie Pro
  • H3 BizBoost Pro
  • H3 Catch Fullscreen Pro
  • H3 Audioman Pro
  • H3 Bold Photography Pro
  • H3 My Music Band Pro
  • H3 Euphony Pro
  • H3 Photofocus Pro
  • H3 Clean Fotografie Pro
  • H3 Zubin Pro
  • H3 Adonis Pro
  • H3 Fotografie Blocks Pro
  • H3 Kiddiemart
  • H3 Drinkify
  • H3 Skincues
  • H3 OutWit
  • H3 Furnitrix Pro
  • H2 5 Stars Reviews
  • H2 Active Installs
  • H2 Total Downloads
  • H2 Support Forum
  • H2 Free WordPress Themes
  • H3 High Performance
  • H3 Soundscape
  • H3 Euphony Blocks
  • H3 Rock Tune
  • H3 Photofocus Blocks
  • H3 Bold Photography Blocks
  • H2 We were featured on
  • H2 Why Try Catch Themes?
  • H2 Catch Plugins for Free and Premium WordPress Plugins
  • H2 What Our Customers Have to Say about Catch Themes? Let our Customers do the Talking for you!
  • H2 Marius84
  • H2 Landyvlad
  • H2 Nicolas Bassand
  • H4 Privacy Overview skipped

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

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 2 pass AA only
a Catch Themes
3.19:1
#000000
on
#006390
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Free & Premium WordP…4.14:13.0:1
#000000
#0075AC
Pass
h2 Design Visually with…4.37:13.0:1
#000000
#0079B1
Pass
h2 Bizboost Pro8.62:13.0:1
#000000
#66AFD1
Pass
h2 Photofocus Blocks Pr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Premium WordPress Th…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 5 Stars Reviews21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Active Installs21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Total Downloads21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Support Forum21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Free WordPress Theme…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We were featured on21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why Try Catch Themes…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Catch Plugins for Fr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What Our Customers H…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Marius8421.00:13.0:1
#000000
#FFFFFF
Pass
h2 Landyvlad21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nicolas Bassand21.00:13.0:1
#000000
#FFFFFF
Pass
title Free and Premium Res…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
a Catch Themes3.19:14.5:1
#000000
#006390
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 6 failing, 20 passed
REVIEW
78

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.

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
header#masthead > div.wrapper > div.site-header-main > button#menu-toggle header#masthead > div.wrapper > div.site-header-main > button#menu-toggle

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.entry-container > div.entry-header > div.testimonial-social-icon > a.social-icon div.entry-container > div.entry-header > div.testimonial-social-icon > a.social-icon
div.entry-container > div.entry-header > div.testimonial-social-icon > a.social-icon div.entry-container > div.entry-header > div.testimonial-social-icon > a.social-icon
div.entry-container > div.entry-header > div.testimonial-social-icon > a.social-icon div.entry-container > div.entry-header > div.testimonial-social-icon > a.social-icon

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.

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
BUY THEMES article#page-hero > div.entry-content > p.button > a.button-minimal
BUY NOW div.section-wrapper > div.entry-header > div.button > a.button-minimal
VIEW THEME div.section-wrapper > div.entry-header > div.button > a.button-minimal
BUY NOW div.section-wrapper > div.entry-header > div.button > a.button-minimal
VIEW THEME div.section-wrapper > div.entry-header > div.button > a.button-minimal
VIEW FSE THEMES div.wrapper > div.entry-content > p.button > a.button-minimal
Got it! span > div.cli-bar-container > div.cli-bar-btn_container > a#cookie_action_close_header

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These are opportunities to improve the interpretation of your content by users in different locales.

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
div.entry-header > header.entry-header > p.entry-meta > a div.entry-header > header.entry-header > p.entry-meta > a
div.entry-container > div.entry-header > div.testimonial-social-icon > a.social-icon div.entry-container > div.entry-header > div.testimonial-social-icon > a.social-icon

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.js html.js

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
●`[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
●`<frame>` or `<iframe>` elements have a title
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Deprecated ARIA roles were not used
●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 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
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has a valid value for its `[lang]` attribute
○`<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.
○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+
Alt Text Quality
All 45 images OK
PASS
All 45 images OK
Info::
33 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
45 images 12 good alt text 33 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
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">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#wt-cli-checkbox-necessarycheckboxNecessaryfor/id
#wt-cli-checkbox-non-necessarycheckboxNon-necessaryfor/id
#g-recaptcha-response-100000textarea(none)none

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

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

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

A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - Catch Themes ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback