Skip to content
https://wp-royal-themes.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Heading Hierarchy
Action
16 headings, 2 skip(s)
FIX
16 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
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.
  • H2 What to Expect?
  • H4 Lightweight skipped
  • H4 Customizable
  • H4 E-commerce
  • H4 Top Notch Support
  • H2 Latest Themes
  • H4 News Mgazine X – PRO Version skipped
  • H4 News Mgazine X – Free Version
  • H4 Bard Blog – Free Version
  • H4 Bard Blog – Pro Version
  • H4 Ashe Blog – Free Version
  • H4 Ashe Blog – Pro Version
  • H2 Customer Reviews
  • H2 About Us
  • H2 We are WP Royal, a creative and dedicated group of WordPress Theme Developers and Designers.
  • H2 Clients & Awwards

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

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
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 - WP Royal Themes Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 81/100 — 5 failing, 21 passed
REVIEW
81

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.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot
div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot
div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot
div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot
div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot
div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot
div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot div.wpb_wrapper > div.owl-carousel > div.owl-dots > button.owl-dot

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
article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone
article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone
article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone
article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone
article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone
article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone article.post > figure.woocom-project > div.woo-buttons-on-img > a.alignnone

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
Blogger div.content-wrap > div.testimonial-vcard > div.testimonial-position > span.text-secondary
Envato Market div.wpb_text_column > div.wpb_wrapper > p > a

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
Lightweight div.ult-animation > div#ultimate-heading-894269e86e07e98e7 > div.uvc-main-heading > h4
News Mgazine X – PRO Version article.post > figure.woocom-project > figcaption.woocom-list-content > h4.entry-title

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
Select elements have associated label elements.
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
Links are distinguishable without relying on color.
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.
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
`[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 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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
Identical links have the same purpose.
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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A+
Alt Text Quality
All 26 images OK
PASS
All 26 images OK
Info::
23 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
26 images 3 good alt text 23 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
selectselectDropdown menuaria-label
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 What to Expect?19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Latest Themes19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Customer Reviews19.60:13.0:1
#000000
#F7F7F7
Pass
h2 About Us19.60:13.0:1
#000000
#F7F7F7
Pass
h2 We are WP Royal, a c…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Clients & Awwards19.60:13.0:1
#000000
#F7F7F7
Pass
title Home - WP Royal Them…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
div WP Royal Themes21.00:14.5:1
#000000
#FFFFFF
Pass
div Crafting Best Wordpr…21.00:14.5:1
#000000
#FFFFFF
Pass
span Home21.00:14.5:1
#000000
#FFFFFF
Pass
span Themes21.00:14.5:1
#000000
#FFFFFF
Pass
span Plugins21.00:14.5:1
#000000
#FFFFFF
Pass
span Easy Website Backup …18.76:14.5:1
#000000
#F2F2F2
Pass
span Royal Elementor Addo…21.00:14.5:1
#000000
#FFFFFF
Pass
span Support21.00:14.5:1
#000000
#FFFFFF
Pass
span Ashe Theme21.00:14.5:1
#000000
#FFFFFF
Pass
span Ashe Free Support Fo…21.00:14.5:1
#000000
#FFFFFF
Pass
span Ashe Pro Support For…21.00:14.5:1
#000000
#FFFFFF
Pass
span Documentation21.00:14.5:1
#000000
#FFFFFF
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.

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

Send Feedback