Skip to content
https://themegrill.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top 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)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
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
Warning::
2 of 2 <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 (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

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

B
Heading Hierarchy
46 headings, 2 skip(s)
REVIEW
46 headings, 2 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.
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 Fast, Lightweight & Customizable Beautiful Themes for WordPress
  • H2 Elevate Your Website with Our Themes
  • H2 ColorMag
  • H2 Zakra
  • H2 Enhance your site with our plugins
  • H3 Masteriyo
  • H3 Everest Forms
  • H3 User Registration & Membership
  • H2 0
  • H2 0+
  • H2 0+
  • H2 Jump Start Your Websites with Our Starter Sites
  • H3 Main
  • H3 Flavorbud
  • H3 Main V2
  • H3 ColorMag 01
  • H3 TheNewsHive
  • H3 Newspaper
  • H2 Why You’ll Love ThemeGrill
  • H5 Friendly Dependable Support skipped
  • H5 Fast Loading Speed
  • H5 Easy Setup & Demo Import
  • H5 Professionally Well Coded
  • H5 Beautifully Designed Themes
  • H5 Risk-Free Purchase
  • H2 What ThemeGrill Customers are Saying
  • H3 Love this theme!
  • H3 Great and flixible theme
  • H3 Everything I expected!
  • H3 The best support
  • H3 Best theme for news site and more!
  • H3 Versatile
  • H2 Seamless Integration with Popular WordPress Plugins
  • H2 Proud To Be Mentioned By
  • H2 Dedicated Customer Support
  • H5 Live Chat skipped
  • H5 Support Form
  • H5 Dedicated Facebook Group
  • H2 Join 200,000+ satisfied site owners
  • H2 Join 200,000+ satisfied site owners
  • H3 Themes
  • H3 Gutenberg Blocks
  • H3 Plugins
  • H3 Company
  • H3 Resources
  • H2 Get ColorMag Free – Create Stunning News & Magazine Sites!

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

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 - ThemeGrill ✓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
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 20 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.

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
Explore All Themes div.blockart-column-inner > div.blockart-buttons > div.blockart-button > a.blockart-button-link
#1 Popular Magazine WordPress Theme div.blockart-section-inner > div.blockart-column > div.blockart-column-inner > p.blockart-paragraph
Explore More div.blockart-column-inner > div.blockart-buttons > div.blockart-button > a.blockart-button-link
Explore More div.blockart-column-inner > div.blockart-buttons > div.blockart-button > a.blockart-button-link
View All Plugins div.blockart-column-inner > div.blockart-buttons > div.blockart-button > a.blockart-button-link
Explore More Themes div.blockart-column-inner > div.blockart-buttons > div.blockart-button > a.blockart-button-link
div.blockart-section-inner > div.blockart-column > div.blockart-column-inner > p.blockart-paragraph div.blockart-section-inner > div.blockart-column > div.blockart-column-inner > p.blockart-paragraph
div#evf-18685 > form#evf-form-18685 > div.evf-submit-container > button#evf-submit-18685 div#evf-18685 > form#evf-form-18685 > div.evf-submit-container > button#evf-submit-18685

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
Friendly Dependable Support div.blockart-section-inner > div.blockart-column > div.blockart-column-inner > h5.blockart-heading
Live Chat div.blockart-section-inner > div.blockart-column > div.blockart-column-inner > h5.blockart-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.blockart-column-inner > div.blockart-socials > div.blockart-social-inner > a.blockart-social-link div.blockart-column-inner > div.blockart-socials > div.blockart-social-inner > a.blockart-social-link
div.blockart-column-inner > div.blockart-socials > div.blockart-social-inner > a.blockart-social-link div.blockart-column-inner > div.blockart-socials > div.blockart-social-inner > a.blockart-social-link
div.blockart-column-inner > div.blockart-socials > div.blockart-social-inner > a.blockart-social-link div.blockart-column-inner > div.blockart-socials > div.blockart-social-inner > a.blockart-social-link
div.blockart-column-inner > div.blockart-socials > div.blockart-social-inner > a.blockart-social-link div.blockart-column-inner > div.blockart-socials > div.blockart-social-inner > a.blockart-social-link

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.

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[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
●`[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
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○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.
○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
○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 83 images OK
PASS
All 83 images OK
Info::
59 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
83 images 24 good alt text 59 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#evf-18685-field_qI7dcmpleA-1emailEmail *for/id
#evf-18685-field-hptextPhonefor/id
#evf-26394-field_XDjYAD8qIw-1textFirst Namefor/id
#evf-26394-field_yFJ8Zq7Mbh-2textLast Namefor/id
#evf-26394-field_lyWwman12F-3emailEmail *for/id
#evf-26394-field-hptextEmailfor/id
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
h1 Beautiful Themes for…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Elevate Your Website…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Enhance your site wi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Jump Start Your Webs…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why You’ll Love Th…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What ThemeGrill21.00:13.0:1
#000000
#FFFFFF
Pass
h2 are Saying21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Seamless Integration…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Plugins21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Proud To Be Mentione…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dedicated Customer S…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join 200,000+ satisf…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join 200,000+ satisf…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get ColorMag Free …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Masteriyo21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Everest Forms21.00:13.0:1
#000000
#FFFFFF
Pass
h3 User Registration & …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Main21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Flavorbud21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Main V221.00:13.0: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