Skip to content
https://websitedemos.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
F
Heading Hierarchy
Action
35 headings, 5 skip(s)
FIX
35 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Professional Designs, Stunning Results
  • H2 Ecommerce Website Templates for WordPress
  • H2 WordPress Blog Themes
  • H2 WordPress Community Themes
  • H2 Multipurpose WordPress Themes
  • H3 Launch an Amazing Website in Just 3 Steps
  • H4 Click andImport
  • H2 1
  • H4 Customize and Personalize skipped
  • H2 2
  • H4 Publish andGo Live skipped
  • H2 3
  • H3 Build Stunning, High-Performance Websites
  • H6 Websites Without Limits skipped
  • H6 Lightning-Fast Performance
  • H6 Impress with Modern Designs
  • H6 Responsive on Every Device
  • H6 Get Started in Minutes
  • H6 Trusted by Millions
  • H3 Customization Made Easy
  • H6 Unleash Your Creativity skipped
  • H6 Tailor Themes to Your Brand
  • H6 Powerful WooCommerce Integration
  • H6 Perfect for Any Industry
  • H6 Custom Features for All Needs
  • H6 Regular Updates and World-Class Support
  • H3 Designed for Growth and Success
  • H6 SEO Optimized for High Rankings skipped
  • H6 Engage Your Audience Effortlessly
  • H6 Build and Scale Your Business Online
  • H6 Empower Your Online Presence
  • H6 Simplified Management
  • H6 Fully Integrated with Modern Tools
  • H3 Frequently Asked Questions
  • H2 Start Creating Your Dream Website Today!

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

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
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
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "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

C
Alt Text Quality
Action
24 of 185 images have issues
REVIEW
24 of 185 images have issues
Critical::
24 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
112 decorative image(s) correctly marked
Info::
49 image(s) with good alt text
185 images 49 good alt text 112 decorative 24 missing
IssueCount
missing24 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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Website Demos ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
title Website Templates Archive - Website Demo…
4.01:1
#000000
on
#9B36E1
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
4.15:1
#000000
on
#A236E1
needs 4.5:1 (normal text)
16px · top of page (header area)
span Business & Services
4.33:1
#000000
on
#A937E2
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Professional Designs…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ecommerce Website Te…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 WordPress Blog Theme…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 WordPress Community …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Multipurpose WordPre…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Start Creating Your …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Launch an Amazing We…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Build Stunning, High…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Customization Made E…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Designed for Growth …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Frequently Asked Que…21.00:13.0:1
#000000
#FFFFFF
Pass
title Website Templates Ar…4.01:14.5:1
#000000
#9B36E1
Fail
a Skip to content4.15:14.5:1
#000000
#A236E1
Fail
span Business & Services4.33:14.5:1
#000000
#A937E2
Fail
span Business19.81:14.5:1
#000000
#F8F8FB
Pass
span Digital Agency19.81:14.5:1
#000000
#F8F8FB
Pass
span Transport19.81:14.5:1
#000000
#F8F8FB
Pass
span Pet & Animal19.81:14.5:1
#000000
#F8F8FB
Pass
span Landscaping19.81:14.5:1
#000000
#F8F8FB
Pass
span Automotive19.81:14.5:1
#000000
#F8F8FB
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 — 6 failing, 26 passed
REVIEW
82

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
div#directory-search-filter > form#search-form > div.stc-search > button.stc-search-icon div#directory-search-filter > form#search-form > div.stc-search > button.stc-search-icon

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
form#search-form > div.stc-search > button.stc-search-icon > img form#search-form > div.stc-search > button.stc-search-icon > img
div#directory-search-filter > div#filtersWrapper > div#filterToggle > img div#directory-search-filter > div#filtersWrapper > div#filterToggle > img
div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img
div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img
div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img
div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img
div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img
div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img div.stc-grid-item-badge-outer > div.stc-grid-item-badge-wrapper > div.stc-grid-item-badge > img

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.st-sites-grid > div#pagination > div.pagination-inner > a.next-page div.st-sites-grid > div#pagination > div.pagination-inner > a.next-page

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.

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
Customize and Personalize div.wp-block-uagb-container > div.wp-block-uagb-container > div.wp-block-uagb-advanced-heading > h4.uagb-heading-text
Publish and Go Live div.wp-block-uagb-container > div.wp-block-uagb-container > div.wp-block-uagb-advanced-heading > h4.uagb-heading-text
Websites Without Limits div.wp-block-uagb-info-box > div.uagb-ifb-content > div.uagb-ifb-title-wrap > h6.uagb-ifb-title
Unleash Your Creativity div.wp-block-uagb-info-box > div.uagb-ifb-content > div.uagb-ifb-title-wrap > h6.uagb-ifb-title
SEO Optimized for High Rankings div.wp-block-uagb-info-box > div.uagb-ifb-content > div.uagb-ifb-title-wrap > h6.uagb-ifb-title

These are opportunities to improve keyboard navigation in your application.

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#directory-search-filter > form#search-form > div.stc-search > button.stc-search-icon div#directory-search-filter > form#search-form > div.stc-search > button.stc-search-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 html

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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Skip links are focusable.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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.
○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.
○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.
A
Form Accessibility
1 of 7 controls have issues
PASS
1 of 7 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search">
Info::
6 control(s) properly labeled
7 controls
6 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
page-builderradionone
page-builderradionone
typeradionone
typeradionone
order-byradionone
order-byradionone
searchtext(Search for templates)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="search">

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

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

Send Feedback