https://unmineable.wordpress.com/2025/11/09/how-to-get-an-unmineable-referral-code-and-make-the-most-of-it/

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

10 PASS 10 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Heading Hierarchy

25 headings, 1 skip(s)

REVIEW

25 headings, 1 skip(s)

Multiple H1 headings (2 found)

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

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 How to Get an unMineable Referral Code duplicate H1
H3 What is the referral code / program skipped
H3 How to get your own referral code
H3 How to use someone else’s referral code (or let someone use yours)
H3 What are the benefits / how much do you earn
H3 Step-by-Step: Quick Setup for New User
H3 Best Practices & Tips for Sharing and Using
H3 Frequently Asked Questions (FAQ)
H3 Share this:
H3 3 responses to “How to Get an unMineable Referral Code”
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

Link & Button Quality

1 issue(s) across 142 links and 7 buttons

REVIEW

1 issue(s) across 142 links and 7 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a.sd-link-color (#379 on page)

17 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://unmineable.wordpress.com/about/; https://unmineable.wordpress.com/2025/12/06/understanding-unmineables-referra…; https://rebrand.ly/Pepecoin-free; https://rebrand.ly/MystNode; https://www.quora.com/profile/Unmineablewordpress; https://rebrand.ly/PEPEcoin; https://rebrand.ly/PEPEcoin; https://rebrand.ly/PEPEcoin; https://unmineable.wordpress.com; https://unmineable.wordpress.com/2025/11/09/how-to-get-an-unmineable-referral… (+7 more)

124 link(s) with descriptive text

142 links

1 empty

0 generic text

17 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://unmineable.wordpress.com/about/	AboutUnmineable Coins – …	new tab	Add '(opens in new tab)' to text
https://unmineable.wordpress.com/2025/12…	unmineable Coin Referral	new tab	Add '(opens in new tab)' to text
https://rebrand.ly/Pepecoin-free	Mine Pepecoin for Free	new tab	Add '(opens in new tab)' to text
https://rebrand.ly/MystNode	Mysterium	new tab	Add '(opens in new tab)' to text
https://www.quora.com/profile/Unmineable…	Unmineablewordpress	new tab	Add '(opens in new tab)' to text
https://rebrand.ly/PEPEcoin	Unmineable	new tab	Add '(opens in new tab)' to text
https://rebrand.ly/PEPEcoin	UnmineableReferralCodes	new tab	Add '(opens in new tab)' to text
https://rebrand.ly/PEPEcoin	0lqw-qcab	new tab	Add '(opens in new tab)' to text
https://unmineable.wordpress.com	unMineable.wordpress.com	new tab	Add '(opens in new tab)' to text
https://unmineable.wordpress.com/2025/11…	Share on X (Opens in new windo…	new tab	Add '(opens in new tab)' to text
https://unmineable.wordpress.com/2025/11…	Share on Facebook (Opens in ne…	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://sites.google.com/view/unmineable…	Unmineable Referral Code	new tab	Add '(opens in new tab)' to text
https://x.com/unmineablecode	0lqw-qcab	new tab	Add '(opens in new tab)' to text
https://unmineablereferralcode.mystrikin…	referral incentive	new tab	Add '(opens in new tab)' to text
https://earn-pepe.com?ref=TaduVA	Earn-pepe	new tab	Add '(opens in new tab)' to text
https://pepecoinguide.carrd.co/	Unmineable	new tab	Add '(opens in new tab)' to text
https://unmineable.wordpress.com	Mine Unmineable Coins	img no alt	Add alt attribute to the image
https://unmineable.wordpress.com	Mine Unmineable Coins	img no alt	Add alt attribute to the image
https://wordpress.com/abuse/?report_url=…	Report this content	new tab	Add '(opens in new tab)' to text

131 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a.sd-link-color (#379 on page)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://unmineable.wordpress.com/about/; https://unmineable.wordpress.com/2025/12/06/understanding-unmineables-referra…; https://rebrand.ly/Pepecoin-free; https://rebrand.ly/MystNode; https://www.quora.com/profile/Unmineablewordpress; https://rebrand.ly/PEPEcoin; https://rebrand.ly/PEPEcoin; https://rebrand.ly/PEPEcoin; https://unmineable.wordpress.com; https://unmineable.wordpress.com/2025/11/09/how-to-get-an-unmineable-referral… (+7 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Mobile Keyboard & Autofill

Action

4/6 eligible field(s) missing autocomplete or inputmode

REVIEW

4/6 eligible field(s) missing autocomplete or inputmode

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">

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">

Iframe Accessibility

Action

4/5 iframe(s) missing title; 0 placeholder(s)

REVIEW

4/5 iframe(s) missing title; 0 placeholder(s)

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.

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.

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.

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.

Tap Target Adequacy

Action

7 tap target(s) too small or too close together

REVIEW

7 tap target(s) too small or too close together

7 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.

Mobile-Readable Font Sizes

91% of visible text renders at >= 12 CSS px (20 below threshold)

REVIEW

91% of visible text renders at >= 12 CSS px (20 below threshold)

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 ("Nov 9, 2025"); <a> 11.5px ("#workfromhome"); <a> 11.5px ("NC Wallet"); <a> 11.5px ("Uncategorized"); <a> 11.5px ("unmineable crypto").

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

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 ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

#0A100A

needs 3.0:1 (large text)

32px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Unmineable Coins	1.09:1	3.0:1	#000000	#0A100A	Fail
h1 How to Get an unMine…	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 What is the referral…	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 How to	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 your own referral co…	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 How to	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 someone else’s ref…	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 What are the benefit…	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Step-by-Step: Quick …	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Best Practices & Tip…	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Frequently Asked Que…	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Share this:	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 3 responses to “Ho…	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Leave a Reply	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Hey!	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Join the club	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Categories	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Tags	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Recent Posts	16.49:1	3.0:1	#000000	#E2E4E7	Pass
h3 Subscribe	16.49:1	3.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.

Lighthouse Accessibility Audits

Score 86/100 — 5 failing, 26 passed

REVIEW

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.