Skip to content
https://themeisle.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Form Accessibility
Action
6 of 8 controls have issues
FIX
6 of 8 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="checkbox" name="footer-box-toggle-1" id="footer-box-toggle-1">; <input type="checkbox" name="footer-box-toggle-2" id="footer-box-toggle-2">; <input type="checkbox" name="footer-box-toggle-3" id="footer-box-toggle-3">; <input type="checkbox" name="footer-box-toggle-4" id="footer-box-toggle-4">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email" id="download-email">
Info::
2 control(s) properly labeled
8 controls
2 labeled
1 placeholder only
5 unlabeled
ControlTypeLabelMethod
ssearchSearcharia-label
#obfx-checkbox-cbcheckboxXfor/id
#download-emailemail(Add your email address)placeholder only
#footer-box-toggle-1checkbox(none)none
#footer-box-toggle-2checkbox(none)none
#footer-box-toggle-3checkbox(none)none
#footer-box-toggle-4checkbox(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="checkbox" name="footer-box-toggle-1" id="footer-box-toggle-1">; <input type="checkbox" name="footer-box-toggle-2" id="footer-box-toggle-2">; <input type="checkbox" name="footer-box-toggle-3" id="footer-box-toggle-3">; <input type="checkbox" name="footer-box-toggle-4" id="footer-box-toggle-4">

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.

<input type="email" name="email" id="download-email">

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

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
Info::
Hamburger menu detected (responsive design)
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)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
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, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h1 WordPress Themes & Plugins for yer voyag…
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Themes
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Plugins
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Set sail with a fleet of 471,039 pirates
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Blog
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About Us
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Supported by Real People
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our products be used by
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our tutorials
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Join over 400k users who build aweso…
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
span Themes
3.81:1
#000000
on
#0767CB
needs 4.5:1 (normal text)
16px · top of page (header area)
a Neve
3.76:1
#000000
on
#0566CA
needs 4.5:1 (normal text)
16px · top of page (header area)
a Hestia
3.66:1
#000000
on
#0464C8
needs 4.5:1 (normal text)
16px · above the fold
a Neve FSE
3.61:1
#000000
on
#0263C7
needs 4.5:1 (normal text)
16px · above the fold
a All Themes
3.61:1
#000000
on
#0263C7
needs 4.5:1 (normal text)
16px · above the fold
span Plugins
3.60:1
#000000
on
#0363C6
needs 4.5:1 (normal text)
16px · above the fold
a Feedzy RSS Feeds
3.61:1
#000000
on
#0463C6
needs 4.5:1 (normal text)
16px · above the fold
a Visualizer
3.64:1
#000000
on
#0664C5
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 WordPress Themes & P…1.66:13.0:1
#000000
#333333
Fail
h2 Themes1.66:13.0:1
#000000
#333333
Fail
h2 Plugins1.66:13.0:1
#000000
#333333
Fail
h2 Set sail with a flee…1.66:13.0:1
#000000
#333333
Fail
h2 Blog1.66:13.0:1
#000000
#333333
Fail
h2 About Us1.66:13.0:1
#000000
#333333
Fail
h2 Supported by Real Pe…1.66:13.0:1
#000000
#333333
Fail
h2 Our products be used…1.66:13.0:1
#000000
#333333
Fail
h2 Our tutorials1.66:13.0:1
#000000
#333333
Fail
h3 Join over 400k u…1.66:13.0:1
#000000
#333333
Fail
title Themeisle - Built to…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
span Themes3.81:14.5:1
#000000
#0767CB
Fail
a Neve3.76:14.5:1
#000000
#0566CA
Fail
a Hestia3.66:14.5:1
#000000
#0464C8
Fail
a Neve FSE3.61:14.5:1
#000000
#0263C7
Fail
a All Themes3.61:14.5:1
#000000
#0263C7
Fail
span Plugins3.60:14.5:1
#000000
#0363C6
Fail
a Feedzy RSS Feeds3.61:14.5:1
#000000
#0463C6
Fail
a Visualizer3.64:14.5:1
#000000
#0664C5
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 88/100 — 4 failing, 24 passed
REVIEW
88

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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.footer-cols > div.footer-box > label.caret div.row > div.footer-cols > div.footer-box > label.caret
div.row > div.footer-cols > div.footer-box > label.caret div.row > div.footer-cols > div.footer-box > label.caret
div.row > div.footer-cols > div.footer-box > label.caret div.row > div.footer-cols > div.footer-box > label.caret
div.row > div.footer-cols > div.footer-box > label.caret div.row > div.footer-cols > div.footer-box > label.caret

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
Blimey! Add more firepower to yer site, theme and rule the seven seas. div.nv-content-wrap > div.wp-block-columns > div.wp-block-column > p.is-style-default
See All Plugins div.wp-block-column > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link
Find th’ gold wit’ our treasure maps for land lubbers and seafarers alike. div.nv-content-wrap > div.wp-block-columns > div.wp-block-column > p.has-text-color
See what’s new div.wp-block-column > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link
Accept body.home > div#obfx-cookie-bar > span.obfx-cookie-bar > a#obfx-accept-cookie-policy

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
How to install WordPress guide div.wp-block-column > div.wp-block-themeisle-icon-card > div.ti-card-content-wrap > h5.wp-block-heading

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.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-image > a div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-image > a
div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-image > a div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-image > a
div.wp-block-columns > div.wp-block-column > p.is-style-default > a div.wp-block-columns > div.wp-block-column > p.is-style-default > 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.

○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
●`[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
●`<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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 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
○`<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
○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.
○Skip links are focusable.
○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.
○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
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 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 MAIN CONTENTINFO footer

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
23 headings, 1 skip(s)
PASS
23 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 WordPress Themes & Plugins for yer voyage
  • H2 Themes
  • H2 Neve
  • H2 Hestia
  • H3 Otter Blocks
  • H3 Visualizer
  • H3 Feedzy
  • H2 Plugins
  • H2 Set sail with a fleet of 471,039 pirates
  • H2 Blog
  • H2 About Us
  • H2 Supported by Real People
  • H2 Our products be used by
  • H2 Our tutorials
  • H5 How to install WordPress guide skipped
  • H5 Best WordPress hosting compared
  • H5 Best 9 free blogging sites compared
  • H5 How to create a successful blog
  • H5 Start an online store with WordPress
  • H5 How to create a website for free
  • H5 Most profitable blog niches
  • H5 Best domain registrars to buy domains from
  • H3 Join over 400k users who build awesome sites with our products!

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

A
Alt Text Quality
4 of 15 images have issues
PASS
4 of 15 images have issues
Warning::
4 image(s) with generic alt text
Info::
11 decorative image(s) correctly marked
15 images 11 decorative 4 generic
IssueCount
generic4 image(s)
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 - Themeisle ✓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