Skip to content
https://cryoutcreations.eu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 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::
5 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <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
Form Accessibility
Action
3 of 7 controls have issues
REVIEW
3 of 7 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="wp-submit" id="wp-submit1">; <input type="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">
Info::
4 control(s) properly labeled
7 controls
4 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#user_login1textE-mail or username:for/id
#user_pass1passwordPassword:for/id
#rememberme1checkboxnone
#subscribe-field-blog_subscription-2emailYour e-mailfor/id
ssearch(Search)placeholder only
inputsubmit(none)none
#wp-submit1submit(none)none

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

<input type="submit" name="wp-submit" id="wp-submit1">; <input type="submit">

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="search" name="s">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found • Cryout Creations ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
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
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Bravada is our18.10:13.0:1
#000000
#EEEEEE
Pass
h2 WordPress theme18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Esotera is our18.10:13.0:1
#000000
#EEEEEE
Pass
h2 WordPress theme18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Our selection of18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Why choose18.10:13.0:1
#000000
#EEEEEE
Pass
h3 6 614 000+ downloads18.10:13.0:1
#000000
#EEEEEE
Pass
h3 139 000+ active user…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Most popular18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Small team18.10:13.0:1
#000000
#EEEEEE
Pass
h3 WordPress experience18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Long lifecycles18.10:13.0:1
#000000
#EEEEEE
Pass
h3 No shortcuts18.10:13.0:1
#000000
#EEEEEE
Pass
h3 User input18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Customization18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Stay up to date18.10:13.0:1
#000000
#EEEEEE
Pass
title Free and Premium Wor…21.00:14.5:1
#000000
#FFFFFF
Pass
a Cryout Creations21.00:14.5:1
#000000
#FFFFFF
Pass
span Free WordPress Theme…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content6.57:14.5:1
#000000
#459D9E
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
Landmark Structure
14 landmarks
PASS
14 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
4 of 5 <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 ASIDE 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
15 headings
PASS
15 headings
Info::
Single H1 present
  • H1 We Create Responsive & Fluid  WordPress Themes and Plugins
  • H2 Bravada is our bolder WordPress theme
  • H2 Esotera is our warmer WordPress theme
  • H3 6 614 000+ downloads
  • H3 139 000+ active users
  • H3 Most popular
  • H2 Our selection of WordPress Themes
  • H2 Why choose Cryout Creations?
  • H3 Small team
  • H3 WordPress experience
  • H3 Long lifecycles
  • H3 No shortcuts
  • H3 User input
  • H3 Customization
  • H3 Stay up to date
A+
Alt Text Quality
All 55 images OK
PASS
All 55 images OK
Info::
45 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
55 images 10 good alt text 45 decorative
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 25 passed
PASS
93

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Toggle Uber Navigation div#site-header-main > div#site-header-main-inside > nav#access-uber > a.ubermenu-responsive-toggle

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
CRYOUT CREATIONS div#branding > div#site-title > span > a
Free & Premium header > h1.color-black > strong#pp-adjectives > span#pp-adjectives-inside
bolder div.cryout-header > header > h2.color-black > strong
Bravada is a fullscreen WordPress theme that looks amazing, behaves flawlessly … section.cryout-pp-header2 > div.cryout-header > header > p.byline-small
VIEW DEMO div.cryout-header > header > div.overflow-hidden > a.crybutton-blue
warmer div.cryout-header > header > h2.color-black > strong
Esotera is a colorful, clean and beautifully animated WordPress theme with a gr… section.cryout-pp-header2 > div.cryout-header > header > p.byline-small
VIEW DEMO div.cryout-header > header > div.overflow-hidden > a.crybutton-blue
Together, our free WordPress themes and plugins have been downloaded over six m… section#cryout-pp-numbers > div.text-align-center > div.cryout-element > p.color-gray
With an average rating of 4.6 out of 5 based on 474 reviews, all of our creatio… section#cryout-pp-numbers > div.text-align-center > div.cryout-element > p.color-gray
We believe in quality and versatility over quantity and mediocrity, so we put a… main#main > section#cryout-pp-themes-showcase > header.section-box > p.byline
It's just us, the developers – we don't get middlemen to handle things for us. … section#cryout-theme-features > div.section-box > div.cryout-element > p.color-gray
We have it. Whether in the form of WordPress themes, plugins, custom coding or … section#cryout-theme-features > div.section-box > div.cryout-element > p.color-gray
We never retire our WordPress themes. We stand behind them all the way. They're… section#cryout-theme-features > div.section-box > div.cryout-element > p.color-gray
Our free WordPress themes and plugins are live at WordPress.org. That means we'… section#cryout-theme-features > div.section-box > div.cryout-element > p.color-gray
Our creations have always benefited from user feedback. We bring them to life b… section#cryout-theme-features > div.section-box > div.cryout-element > p.color-gray
There's more than meets the eye with our free WordPress themes. What you see in… section#cryout-theme-features > div.section-box > div.cryout-element > p.color-gray
Documentation nav.footermenu > ul > li#menu-item-43265 > a
Tutorials nav.footermenu > ul > li#menu-item-42535 > a
OpenCart Archives nav.footermenu > ul > li#menu-item-55563 > a
Support Forum nav.footermenu > ul > li#menu-item-43266 > a
News & Blog nav.footermenu > ul > li#menu-item-43270 > a
Themes nav.footermenu > ul > li#menu-item-43269 > a
Plugins nav.footermenu > ul > li#menu-item-55564 > a
Pricing nav.footermenu > ul > li#menu-item-42527 > a
Priority Support nav.footermenu > ul > li#menu-item-44084 > a
Customization nav.footermenu > ul > li#menu-item-42529 > a
About Us nav.footermenu > ul > li#menu-item-37907 > a
Terms and Conditions nav.footermenu > ul > li#menu-item-37912 > a
Online Dispute Resolution nav.footermenu > ul > li#menu-item-70355 > a
Privacy Policy nav.footermenu > ul > li#menu-item-37906 > a
Contact nav.footermenu > ul > li#menu-item-37914 > a
Are you enjoying our creations? Subscribe and we'll let you know when we releas… div.wp-block-jetpack-subscriptions__container > form#subscribe-blog-blog_subscription-2 > div#subscribe-text > p
Copyright © 2010-2026, Cryout Creations Srl • Imprint • Engineered in Europe footer#footer > div#footer-inside > div#footer-bottom > div.footer-copyright
Imprint div#footer-inside > div#footer-bottom > div.footer-copyright > a
ACCEPT body.home > div#cryout-cookies-notification > button.close-button

These are opportunities to improve the legibility of your content.

○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
●Form elements have associated labels
●`[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
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○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.
○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.

Send Feedback