Skip to content
https://themeansar.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Heading Hierarchy
Action
67 headings, 4 skip(s)
FIX
67 headings, 4 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Free & Premium Beautiful WordPress Themes
  • H5 Featured onWordPress.org skipped
  • H5 Featured onWPBeginner.com
  • H5 14-Day Money Back Guarantee
  • H2 Check Out Our Popular Themes
  • H3 Newsxo Pro Magazine & Blog WordPress Theme
  • H3 NewsPaperup Pro Magazine & Blog WordPress Theme
  • H3 BlogData Pro Minimal Blog & Magazine WordPress Theme
  • H3 BlogArise Pro Minimal Blog & Magazine WordPress Theme
  • H3 Blogus Pro Minimal Blog & Magazine WordPress Theme
  • H3 Agencyup Pro Business WordPress Theme
  • H2 Check Out Our Latest Themes
  • H3 Newsxo Pro Magazine & Blog WordPress Theme
  • H3 Blogier Pro Minimal Blog & Magazine WordPress Theme
  • H3 NewsPaperup Pro Magazine & Blog WordPress Theme
  • H3 BlogData Pro Minimal Blog & Magazine WordPress Theme
  • H3 NewsAir Pro Magazine & Blog WordPress Theme
  • H3 BlogArise Pro Minimal Blog & Magazine WordPress Theme
  • H2 Check Out Our Popular Free Themes
  • H3 Blogfull WordPress Theme
  • H3 Newsxpo Free Magazine & Blog WordPress Theme
  • H3 Newspaperup Free Magazine & Blog WordPress Theme
  • H3 BlogData Free WordPress Theme
  • H3 Blogus Free Blog WordPress Theme
  • H3 Newsup Free News & Magazine WordPress Theme
  • H2 Check Out Our Latest Free Themes
  • H3 Blogmode WordPress Theme
  • H3 Newstwenty Free Blog & Magazine Elementor WordPress Theme
  • H3 Blogtimes Free Blog & Magazine WordPress Theme
  • H3 Newstack Free Blog & Magazine Elementor WordPress Theme
  • H3 Newsgo Free Blog & Magazine Elementor WordPress Theme
  • H3 Penpress Free Blog & Magazine Elementor WordPress Theme
  • H2 Features
  • H2 Why Choose Us
  • H5 Responsive Design skipped
  • H5 Fast and Easy Setup
  • H5 Browser Compatibility
  • H5 Global Marketplace
  • H5 Money Back Guarantee
  • H5 24/7 Support
  • H2 Testimonials
  • H2 Our Clients Says
  • H5 Theme Support skipped
  • H6 Hapedo Hanspeter
  • H5 Great theme, great customer service
  • H6 Neil Bagg
  • H5 Amazing Support
  • H6 Amyripplenami
  • H5 Great theme so far
  • H6 Board Gamegran
  • H5 Best customer support I’ve ever had
  • H6 Olkunlex
  • H5 Great so far!
  • H6 Vincent Vangrond
  • H5 Excellent help
  • H6 Rakusj
  • H5 One of the best
  • H6 Hish Codes
  • H5 First class theme and excellent support
  • H6 Ash
  • H5 Excellent Support
  • H6 Ian
  • H3 Term & Conditions
  • H3 Info
  • H3 Latest News
  • H5 Introducing BlogNews Addons for Elementor skipped
  • H3 Newsletter

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ 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::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV 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

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - ThemeAnsar ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA
h2 Free & Premium Beautiful WordPress Theme…
1.18:1
#000000
on
#001C13
needs 3.0:1 (large text)
24px · mid-page
title Premium & Free WordPress Themes | ThemeA…
1.31:1
#000000
on
#01271A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.29:1
#000000
on
#01261A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.29:1
#000000
on
#01261A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Themes
1.29:1
#000000
on
#01261A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Free Themes
1.28:1
#000000
on
#012519
needs 4.5:1 (normal text)
16px · above the fold
a Plugins
1.28:1
#000000
on
#012519
needs 4.5:1 (normal text)
16px · above the fold
a Ansar Import
1.27:1
#000000
on
#012418
needs 4.5:1 (normal text)
16px · above the fold
a BlogNews Elementor
1.25:1
#000000
on
#012318
needs 4.5:1 (normal text)
16px · above the fold
a Blog
1.24:1
#000000
on
#012217
needs 4.5:1 (normal text)
16px · above the fold
a Support
1.23:1
#000000
on
#012117
needs 4.5:1 (normal text)
16px · above the fold
a Documantation
1.22:1
#000000
on
#002016
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Free & Premium Beaut…1.18:13.0:1
#000000
#001C13
Fail
h2 Check Out Our Popula…16.96:13.0:1
#000000
#E5E7EB
Pass
h2 Check Out Our Latest…16.96:13.0:1
#000000
#E5E7EB
Pass
h2 Check Out Our Popula…16.96:13.0:1
#000000
#E5E7EB
Pass
h2 Check Out Our Latest…16.96:13.0:1
#000000
#E5E7EB
Pass
h3 Term & Conditions16.96:13.0:1
#000000
#E5E7EB
Pass
h3 Info16.96:13.0:1
#000000
#E5E7EB
Pass
h3 Latest News16.96:13.0:1
#000000
#E5E7EB
Pass
h3 Newsletter16.96:13.0:1
#000000
#E5E7EB
Pass
title Premium & Free WordP…1.31:14.5:1
#000000
#01271A
Fail
a Skip to content1.29:14.5:1
#000000
#01261A
Fail
a Home1.29:14.5:1
#000000
#01261A
Fail
a Themes1.29:14.5:1
#000000
#01261A
Fail
a Free Themes1.28:14.5:1
#000000
#012519
Fail
a Plugins1.28:14.5:1
#000000
#012519
Fail
a Ansar Import1.27:14.5:1
#000000
#012418
Fail
a BlogNews Elementor1.25:14.5:1
#000000
#012318
Fail
a Blog1.24:14.5:1
#000000
#012217
Fail
a Support1.23:14.5:1
#000000
#012117
Fail
a Documantation1.22:14.5:1
#000000
#002016
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 83/100 — 4 failing, 16 passed
REVIEW
83

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.container > div.main > div.header-menu > button.menu-btn div.container > div.main > div.header-menu > button.menu-btn

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
POPULAR div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
POPULAR div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
POPULAR div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon
NEW div.ta-product > div.ta-product-bottom > div.ta-title-wrap > span.ribbon

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
Featured on WordPress.org div.ta-feature-wrapper > div.feature_widget > div.media-body > h5.mt-0
Responsive Design div.elementor-widget-container > div.feature_widget > div.media-body > h5.mt-0
Theme Support div.elementor-widget-container > div.testi > div.sub-qute > h5.testi-card-heading
Introducing BlogNews Addons for Elementor div#footer_recent_blog-3 > div.bs-blog > div.bs-post-info > h5

These are opportunities to improve keyboard navigation in your application.

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 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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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-hidden="true"]` elements do not contain focusable descendents
●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
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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 use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○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+
Alt Text Quality
All 38 images OK
PASS
All 38 images OK
Info::
26 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
38 images 12 good alt text 26 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback