Skip to content
https://muffingroup.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
7 landmarks
FIX
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header 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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
16 headings, 1 skip(s)
REVIEW
16 headings, 1 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H1 The author of Betheme, the biggest wordpress theme ever. duplicate H1
  • H1 700+ pre-built websites available for all! duplicate H1
  • H1 The most intuitive website installer ever duplicate H1
  • H1 Building from scratch is easy. No coding skills required! duplicate H1
  • H1 We always try to understand you and help in any situation. duplicate H1
  • H2 What makes us better than others?
  • H2 300 000
  • H2 700+
  • H2 Premium plugins
  • H2 Who we are
  • H2 Get in touch with us
  • H6 This website uses cookies skipped
  • H6 Neccessary
  • H6 Analytics & Performance
  • H6 Marketing

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="cookies_neccessary">; <input type="checkbox" id="cookies_analytics">; <input type="checkbox" id="cookies_marketing">
3 controls
0 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#cookies_neccessarycheckbox(none)none
#cookies_analyticscheckbox(none)none
#cookies_marketingcheckbox(none)none

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

<input type="checkbox" id="cookies_neccessary">; <input type="checkbox" id="cookies_analytics">; <input type="checkbox" id="cookies_marketing">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 The author of Betheme,
1.24:1
#000000
on
#0F1D2E
needs 3.0:1 (large text)
32px · mid-page
h1 the biggest wordpress theme ever.
1.24:1
#000000
on
#0F1D2E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 700+ pre-built websites
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
32px · bottom of viewport
h1 available for all!
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
32px · bottom of viewport
h1 The most intuitive
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
32px · bottom of viewport
h1 website installer ever
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Building from scratch is easy.
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
32px · bottom of viewport
h1 No coding skills required!
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
32px · bottom of viewport
h1 We always try to understand you
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
32px · bottom of viewport
h1 and help in any situation.
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
32px · bottom of viewport
h2 What makes
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
24px · bottom of viewport
h2 us better
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
24px · bottom of viewport
h2 than others?
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
24px · bottom of viewport
h2 300 000
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
24px · bottom of viewport
h2 700+
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Premium plugins
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Who we are
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get in touch with us
1.25:1
#000000
on
#0F1E30
needs 3.0:1 (large text)
24px · bottom of viewport
title Muffin Group | The Most Popular WordPres…
1.21:1
#000000
on
#0D1B2A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.21:1
#000000
on
#0D1B2A
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The author of Bethem…1.24:13.0:1
#000000
#0F1D2E
Fail
h1 the biggest wordpres…1.24:13.0:1
#000000
#0F1D2E
Fail
h1 700+ pre-built websi…1.25:13.0:1
#000000
#0F1E30
Fail
h1 available for all!1.25:13.0:1
#000000
#0F1E30
Fail
h1 The most intuitive1.25:13.0:1
#000000
#0F1E30
Fail
h1 website installer ev…1.25:13.0:1
#000000
#0F1E30
Fail
h1 Building from scratc…1.25:13.0:1
#000000
#0F1E30
Fail
h1 No coding skills req…1.25:13.0:1
#000000
#0F1E30
Fail
h1 We always try to und…1.25:13.0:1
#000000
#0F1E30
Fail
h1 and help in any situ…1.25:13.0:1
#000000
#0F1E30
Fail
h2 What makes1.25:13.0:1
#000000
#0F1E30
Fail
h2 us better1.25:13.0:1
#000000
#0F1E30
Fail
h2 than others?1.25:13.0:1
#000000
#0F1E30
Fail
h2 300 0001.25:13.0:1
#000000
#0F1E30
Fail
h2 700+1.25:13.0:1
#000000
#0F1E30
Fail
h2 Premium plugins1.25:13.0:1
#000000
#0F1E30
Fail
h2 Who we are1.25:13.0:1
#000000
#0F1E30
Fail
h2 Get in touch with us1.25:13.0:1
#000000
#0F1E30
Fail
title Muffin Group | The M…1.21:14.5:1
#000000
#0D1B2A
Fail
a Home1.21:14.5:1
#000000
#0D1B2A
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 85/100 — 5 failing, 26 passed
REVIEW
85

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

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
The author of Betheme, the biggest wordpress theme ever. Check Betheme 700+ pre… div.wrapper > div.muffinSlider > div.slick-list > div.slick-track
Be Theme has been one of the most popular multipurpose WordPress themes for a l… div.wrapper > div.quoteSlider > div.slick-list > div.slick-track

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
Buy now div#mfn-demo-panel > div.panel-controls > a.control > span.text
700+ website templates div#mfn-demo-panel > div.panel-controls > a.control > span.faa-flash

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
This website uses cookies div.mfn-cookies-popup > div.mfn-cookies-wrapper > div.cookies-tab-content > h6

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#mfn-demo-panel > div.panel-content > div.panel-header > a div#mfn-demo-panel > div.panel-content > div.panel-header > a
div#mfn-demo-panel > div.panel-content > div.panel-header > a.panel-close div#mfn-demo-panel > div.panel-content > div.panel-header > a.panel-close

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

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
●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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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
●ARIA toggle fields have accessible names
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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 219 images OK
PASS
All 219 images OK
Info::
200 decorative image(s) correctly marked
Info::
19 image(s) with good alt text
219 images 19 good alt text 200 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback