Skip to content
https://unmineable.wordpress.com/2026/03/07/is-unmineable-safe-full-review-2026/

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
5
REVIEW
9
PASS
10
INFO
0
Checks
24
10 PASS 9 REVIEW 5 FIX
F
Heading Hierarchy
Action
45 headings, 5 skip(s)
FIX
45 headings, 5 skip(s)
Warning::
Multiple H1 headings (14 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Unmineable Coins
  • H1 Is Unmineable Safe? Full Review 2026 duplicate H1
  • H1 Cryptocurrency mining has evolved rapidly over the last few years. duplicate H1
  • H1 What Is Unmineable? duplicate H1
  • H1 How Unmineable Works duplicate H1
  • H3 Mining Algorithms skipped
  • H3 Pool Rewards
  • H3 Conversion
  • H1 Is Unmineable Safe? duplicate H1
  • H1 Legitimacy of Unmineable duplicate H1
  • H1 Security Concerns duplicate H1
  • H1 Real User Experiences duplicate H1
  • H1 Advantages of Unmineable duplicate H1
  • H3 Beginner Friendly skipped
  • H3 Mine Non-Mineable Coins
  • H3 Low Withdrawal Thresholds
  • H3 Multiple Hardware Options
  • H1 Disadvantages of Unmineable duplicate H1
  • H3 Lower Profitability skipped
  • H3 Fees
  • H3 Negative Reviews
  • H3 Antivirus Warnings
  • H1 Is Unmineable Worth Using in 2026? duplicate H1
  • H1 Tips to Use Unmineable Safely duplicate H1
  • H3 Download from the official website only skipped
  • H3 Use a secure wallet
  • H3 Monitor your hashrate
  • H3 Withdraw regularly
  • H3 Use updated mining software
  • H1 So, is Unmineable safe in 2026? duplicate H1
  • H3 Share this: skipped
  • H3 Leave a Reply Cancel reply
  • H3 Hey!
  • H3 Join the club
  • H3 Categories
  • H3 Tags
  • H3 Recent Posts
  • H4 How Much of Earth’s Gold Remains Unmined
  • H4 Affilorama Subscribe REFRCC
  • H4 Affiliate Blueprints on REFRCC
  • H3 MORE THAN JUST A GAME:PLAY AND RECEIVE 25% FROM REFERRALS’ PROFIT15% FROM IN-GAME PURCHASES
  • H4 Choose Your Unmineable Crypto Cryptocurrency
  • H4 Share Your Referral Code
  • H4 Earn Unmineable Referral Rewards
  • H3 Subscribe

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

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

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
Info::
Hamburger menu detected (responsive design)
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)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Mobile Keyboard & Autofill
Action
4/6 eligible field(s) missing autocomplete or inputmode
REVIEW
4/6 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" name="email">
Warning::
3 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="email" id="subscribe-field">, <input type="email" name="email" id="subscribe-field-2">, <input type="email" name="email">
C
Iframe Accessibility
Action
4/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
4/4 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://widgets.wp.com/likes/master.html?ver=20261027#ver=20261027")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Tap Target Adequacy
Action
4 tap target(s) too small or too close together
REVIEW
4 tap target(s) too small or too close together
Warning::
4 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Mobile-Readable Font Sizes
93% of visible text renders at >= 12 CSS px (20 below threshold)
REVIEW
93% of visible text renders at >= 12 CSS px (20 below threshold)
Info::
20 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <time> 11.5px ("Mar 7, 2026"); <a> 11.5px ("#workfromhome"); <a> 11.5px ("NC Wallet"); <a> 11.5px ("Uncategorized"); <a> 11.5px ("unmineable crypto").
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 – Mine Unmineable Coins ✓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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h1 Unmineable Coins
1.09:1
#000000
on
#0A100A
needs 3.0:1 (large text)
32px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Unmineable Coins1.09:13.0:1
#000000
#0A100A
Fail
h1 Is Unmineable Safe? …16.49:13.0:1
#000000
#E2E4E7
Pass
h1 Cryptocurrency minin…16.49:13.0:1
#000000
#E2E4E7
Pass
h1 What Is Unmineable?16.49:13.0:1
#000000
#E2E4E7
Pass
h1 How Unmineable Works16.49:13.0:1
#000000
#E2E4E7
Pass
h1 Is Unmineable Safe?16.49:13.0:1
#000000
#E2E4E7
Pass
h1 Legitimacy of Unmine…16.49:13.0:1
#000000
#E2E4E7
Pass
h1 Security Concerns16.49:13.0:1
#000000
#E2E4E7
Pass
h1 Real User Experience…16.49:13.0:1
#000000
#E2E4E7
Pass
h1 Advantages of Unmine…16.49:13.0:1
#000000
#E2E4E7
Pass
h1 Disadvantages of Unm…16.49:13.0:1
#000000
#E2E4E7
Pass
h1 Is Unmineable Worth …16.49:13.0:1
#000000
#E2E4E7
Pass
h1 Tips to Use Unmineab…16.49:13.0:1
#000000
#E2E4E7
Pass
h1 So,16.49:13.0:1
#000000
#E2E4E7
Pass
h3 Mining Algorithms16.49:13.0:1
#000000
#E2E4E7
Pass
h3 Pool Rewards16.49:13.0:1
#000000
#E2E4E7
Pass
h3 Conversion16.49:13.0:1
#000000
#E2E4E7
Pass
h3 Beginner Friendly16.49:13.0:1
#000000
#E2E4E7
Pass
h3 Mine Non-Mineable Co…16.49:13.0:1
#000000
#E2E4E7
Pass
h3 Low Withdrawal Thres…16.49:13.0:1
#000000
#E2E4E7
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 27 passed
REVIEW
89

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
unmineable Coin Referral div.wp-block-group > ul.wp-block-list > li > a
Mine Pepecoin for Free div.wp-block-group > ul.wp-block-list > li > a
Food Revolution Network div.wp-block-group > ul.wp-block-list > li > a
Mysterium div.wp-block-group > blockquote.wp-block-quote > p.wp-block-paragraph > a
Unmineablewordpress div.wp-block-group > blockquote.wp-block-quote > p.wp-block-paragraph > a
Mar 7, 2026 div.wp-block-group > div.wp-block-post-date > a > time
#workfromhome div.wp-block-template-part > div.wp-block-group > div.taxonomy-category > a
NC Wallet div.wp-block-template-part > div.wp-block-group > div.taxonomy-category > a
Uncategorized div.wp-block-template-part > div.wp-block-group > div.taxonomy-category > a
unmineable crypto div.wp-block-template-part > div.wp-block-group > div.taxonomy-category > a
#BinanceCoin div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#Bitcoin div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#CryptoAnalysis div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#Cryptocurrency div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#CryptocurrencyTrends div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#CryptoExperts div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#CryptoInvesting div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#CryptoMarket div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#CryptoNews div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#CryptoTrading div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#Ethereum div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#PepeCoin div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
#PepeCrash div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
blockchain div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
crypto div.wp-block-template-part > div.wp-block-group > div.taxonomy-post_tag > a
Unmineable main#wp--skip-link--target > div.entry-content > p.wp-block-paragraph > a
Unmineable main#wp--skip-link--target > div.entry-content > p.wp-block-paragraph > a
Traders Union main#wp--skip-link--target > div.entry-content > p.wp-block-paragraph > a
Trustpilot div.entry-content > ul.wp-block-list > li > a
Add your name div.jetpack-comments__box > div.jetpack-comments__actions > span.jetpack-comments__identity > a
#workfromhome div.wp-block-group > ul.wp-block-categories-list > li.cat-item > a
Bitaxe div.wp-block-group > ul.wp-block-categories-list > li.cat-item > a
NC Wallet div.wp-block-group > ul.wp-block-categories-list > li.cat-item > a
Uncategorized div.wp-block-group > ul.wp-block-categories-list > li.cat-item > a
unmineable div.wp-block-group > ul.wp-block-categories-list > li.cat-item > a
Unmineable Coins div.wp-block-group > ul.wp-block-categories-list > li.cat-item > a
unmineable crypto div.wp-block-group > ul.wp-block-categories-list > li.cat-item > a
#BinanceCoin div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#Bitcoin div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#coingecko div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#CryptoAnalysis div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#Cryptocurrency div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#CryptocurrencyTrends div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#CryptoExperts div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#CryptoInvesting div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#CryptoMarket div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#CryptoNews div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#CryptoTrading div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#Ethereum div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#PepeCoin div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#PepeCrash div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
#Technology div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
ai div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
artificial-intelligence div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
bitcoin mining div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
blockchain div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
business div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
cpu mining div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
crypto div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
cryptocurrency mining div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
crypto mining div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-1850 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-1856 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-1897 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-1898 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-1899 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-1906 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-1907 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-1912 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-2015 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-2018 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
dailyprompt-2025 div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
defi div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
digital-marketing div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
finance div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
gpu mining div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
marketing div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
mining profitability div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
mining software div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
passive-income div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
unmineable div.wp-block-group > div.wp-block-group > p.is-style-outline > a.tag-cloud-link
Unmineable Referral Code div.wp-block-column > div.wp-block-group > p.wp-block-paragraph > a
0lqw-qcab div.wp-block-column > div.wp-block-group > p.wp-block-paragraph > a
referral incentive div.wp-block-column > div.wp-block-group > p.wp-block-paragraph > a.unmineable-referral-code-guide
Subscribe form#subscribe-blog-2 > div.wp-block-jetpack-subscriptions__form-elements > p#subscribe-submit > button.wp-block-button__link

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#cmp-app-container > div > div > iframe div#cmp-app-container > div > div > iframe

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

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
Mining Algorithms div.wp-block-column > main#wp--skip-link--target > div.entry-content > h3.wp-block-heading
Beginner Friendly div.wp-block-column > main#wp--skip-link--target > div.entry-content > h3.wp-block-heading
Lower Profitability div.wp-block-column > main#wp--skip-link--target > div.entry-content > h3.wp-block-heading
Download from the official website only div.wp-block-column > main#wp--skip-link--target > div.entry-content > h3.wp-block-heading
Share this: div#jp-post-flair > div.sharedaddy > div.robots-nocontent > h3.sd-title

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
unmineable Coin Referral div.wp-block-group > ul.wp-block-list > li > a
Mine Pepecoin for Free div.wp-block-group > ul.wp-block-list > li > a
Food Revolution Network div.wp-block-group > ul.wp-block-list > li > a
Mar 7, 2026 div.wp-block-template-part > div.wp-block-group > div.wp-block-post-date > a

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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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
●`[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.
●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
●No element has a `[tabindex]` value greater than 0
●Skip links are focusable.
●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 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.
○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+
Landmark Structure
5 landmarks
PASS
5 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 "Navigation" MAIN CONTENTINFO footer
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
4 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
10 images 6 good alt text 4 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 6 controls have issues
PASS
1 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="submit" id="submit">
Info::
5 control(s) properly labeled
6 controls
5 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#commenttextareaCommentaria-label
ak_hp_textareatextareaΔnone
#subscribe-fieldemailType your email…for/id
#subscribe-field-2emailType your email…for/id
emailemailEmail addressaria-label
#submitsubmit(none)none

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

<input type="submit" name="submit" id="submit">

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

A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback