Skip to content
https://explodingtopics.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
Alt Text Quality
Action
7 of 24 images have issues
FIX
7 of 24 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
17 image(s) with good alt text
24 images 17 good alt text 7 missing
IssueCount
missing7 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Form Accessibility
Action
7 of 7 controls have issues
FIX
7 of 7 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">
Warning::
5 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="email" name="email" id="awf_field-113227448">; <input>; <input type="text" name="q">; <input type="text" name="email" id="awf_field-113227448">
7 controls
0 labeled
5 placeholder only
2 unlabeled
ControlTypeLabelMethod
qtext(Enter your domain or URL)placeholder only
#awf_field-113227448email(Email address)placeholder only
inputinput(Search Trends)placeholder only
qtext(Enter topic...)placeholder only
#awf_field-113227448text(Email address)placeholder only
submitsubmit(none)none
#g-recaptcha-responsetextarea(none)none

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

<input type="submit" name="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">

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

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

<input type="text" name="q">; <input type="email" name="email" id="awf_field-113227448">; <input>; <input type="text" name="q">; <input type="text" name="email" id="awf_field-113227448">

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
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::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) ASIDE 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

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 Exploding Topics - 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 25 passed
REVIEW
86

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
2 Years div.filterContainer > div.trendDbPageButtonDropdown > div.dropdownFilterButton > span.filterButtonText
All Categories div.filterContainer > div.trendDbPageButtonDropdown > div.dropdownFilterButton > span.filterButtonText
Volume div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
+99X+ div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop
Growth div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
Volume div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
+99X+ div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop
Growth div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
Volume div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
+1567% div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop
Growth div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
Volume div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
+900% div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop
Growth div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
Volume div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
+900% div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop
Growth div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
Volume div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
+875% div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop
Growth div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom
April 22, 2026 div.articleCard > div.articleCardInner > div.articleContent > p.articleDate
April 17, 2026 div.articleCard > div.articleCardInner > div.articleContent > p.articleDate
April 14, 2026 div.articleCard > div.articleCardInner > div.articleContent > p.articleDate
April 9, 2026 div.articleCard > div.articleCardInner > div.articleContent > p.articleDate

These are opportunities to improve the legibility of your content.

Names and labels

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
div.grid > div.trendCard > div.trendCardInner > img div.grid > div.trendCard > div.trendCardInner > img
div.grid > div.trendCard > div.trendCardInner > img div.grid > div.trendCard > div.trendCardInner > img
div.grid > div.trendCard > div.trendCardInner > img div.grid > div.trendCard > div.trendCardInner > 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.megaMenuWrapper > div.megaMenuInnerWrapper > div.megaMenuTop > a.logo div.megaMenuWrapper > div.megaMenuInnerWrapper > div.megaMenuTop > a.logo
div.container > div.pagerAndResultsContainer > div.pagination-container > a.pagerButton div.container > div.pagerAndResultsContainer > div.pagination-container > a.pagerButton
div.container > div.pagerAndResultsContainer > div.pagination-container > a.pagerButton div.container > div.pagerAndResultsContainer > div.pagination-container > a.pagerButton
div.container > div.footer_bottom > div.footer_logo > a div.container > div.footer_bottom > div.footer_logo > a

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

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#af-form-1686512983 > div#af-body-1686512983 > div.newsletter_form_inner > input#awf_field-113227448 div#af-form-1686512983 > div#af-body-1686512983 > div.newsletter_form_inner > input#awf_field-113227448
div#af-form-1686512983 > div#af-body-1686512983 > div.newsletter_form_inner > input.submit div#af-form-1686512983 > div#af-body-1686512983 > div.newsletter_form_inner > input.submit

These are opportunities to improve keyboard navigation in your application.

○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
●Buttons have an accessible name
●Input buttons have discernible text.
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●Elements use only permitted ARIA attributes
●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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○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.
○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+
Heading Hierarchy
28 headings
PASS
28 headings
Info::
Single H1 present
  • H2 Discover Trends 12+ Months Before Everyone Else
  • H3 Trusted by brands that refuse to fall behind.
  • H1 Discover Exploding Topics
  • H2 Check Real Search Demand for Any Topic or Keyword
  • H2 Powerful Free Tools To Give You An Edge
  • H3 Keyword Research
  • H3 SEO Checker
  • H3 Competitor Analysis
  • H3 Rank Checker
  • H3 Backlink Checker
  • H3 Keyword Difficulty
  • H2 Expert Insights, Data, And Trends
  • H3 How Two Entrepreneurs Used TikTok and Trends to Create a Viral Launch
  • H3 How to Find Semantic Keywords for Google Visibility
  • H3 Top 19 SEO Tools I Recommend for Web and AI Visibility
  • H3 13 Top Marketing Trends (2025)
  • H2 How We Find Trends
  • H3 Analyze
  • H3 Identify
  • H3 Curate
  • H2 Get Exclusive Access to Emerging Trends
  • H2 Breaking Down Trends & Strategies
  • H3 How to Use Exploding Topics: A Quick Start Guide
  • H3 Top Trending Topics (April 2026)
  • H3 E-commerce SEO in 2026: Grow Your Traffic Without Ads
  • H3 Meet the Travel Blogger Using Trends to Enhance His Trips
  • H2 Get Free Email Reports
  • H2 About cookies on this site
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 Discover Exploding T…20.00:13.0:1
#000000
#F5FAFF
Pass
h2 Discover Trends 12+ …20.00:13.0:1
#000000
#F5FAFF
Pass
h2 Check Real Search De…20.00:13.0:1
#000000
#F5FAFF
Pass
h2 Powerful20.00:13.0:1
#000000
#F5FAFF
Pass
h2 To Give You An Edge20.00:13.0:1
#000000
#F5FAFF
Pass
h2 Expert Insights, Dat…20.00:13.0:1
#000000
#F5FAFF
Pass
h2 How We Find Trends20.00:13.0:1
#000000
#F5FAFF
Pass
h2 Get Exclusive Access…20.00:13.0:1
#000000
#F5FAFF
Pass
h2 Breaking Down Trends…20.00:13.0:1
#000000
#F5FAFF
Pass
h2 Get Free Email Repor…20.00:13.0:1
#000000
#F5FAFF
Pass
h2 About cookies on thi…20.00:13.0:1
#000000
#F5FAFF
Pass
h3 Trusted by brands th…20.00:13.0:1
#000000
#F5FAFF
Pass
h3 How Two Entrepreneur…20.00:13.0:1
#000000
#F5FAFF
Pass
h3 How to Find Semantic…20.00:13.0:1
#000000
#F5FAFF
Pass
h3 Top 19 SEO Tools I R…20.00:13.0:1
#000000
#F5FAFF
Pass
h3 13 Top Marketing Tre…20.00:13.0:1
#000000
#F5FAFF
Pass
h3 Analyze20.00:13.0:1
#000000
#F5FAFF
Pass
h3 Identify20.00:13.0:1
#000000
#F5FAFF
Pass
h3 Curate20.00:13.0:1
#000000
#F5FAFF
Pass
h3 How to Use Exploding…20.00:13.0:1
#000000
#F5FAFF
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