Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Link & Button Quality

Action

7 issue(s) across 141 links and 7 buttons

FIX

7 issue(s) across 141 links and 7 buttons

4 link(s) with no accessible text

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

Got: https://twitter.com/cointelegraph; https://telegram.me/cointelegraph; https://www.facebook.com/cointelegraph; https://www.youtube.com/channel/UCRqBu-grVX1p97WaX4d-OuQ

15 link(s) open in new tab without warning

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

Got: https://cointelegraph-magazine.com/neo-governance-reset-pakistan-crypto-banki…; https://cointelegraph.com/rss-feeds; https://twitter.com/cointelegraph; https://telegram.me/cointelegraph; https://www.facebook.com/cointelegraph; https://www.instagram.com/cointelegraph/; https://www.youtube.com/channel/UCRqBu-grVX1p97WaX4d-OuQ; https://apps.apple.com/app/cointelegraph-crypto-news/id1640089162; https://play.google.com/store/apps/details?id=cointelegraph.com; https://cointelegraph.com/rss-feeds (+5 more)

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button[data-testid="desktop-search-popover-toggle"]; button.btn (#1016 on page); button.btn (#1021 on page)

122 link(s) with descriptive text

141 links

4 empty

0 generic text

15 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://twitter.com/cointelegraph	(empty)	empty	Add link text or aria-label
https://telegram.me/cointelegraph	(empty)	empty	Add link text or aria-label
https://www.facebook.com/cointelegraph	(empty)	empty	Add link text or aria-label
https://www.youtube.com/channel/UCRqBu-g…	(empty)	empty	Add link text or aria-label
https://cointelegraph-magazine.com/neo-g…	53 DeFi projects infiltrated, …	new tab	Add '(opens in new tab)' to text
https://cointelegraph.com/rss-feeds	Rss Feed	new tab	Add '(opens in new tab)' to text
https://twitter.com/cointelegraph	Twitter	new tab	Add '(opens in new tab)' to text
https://telegram.me/cointelegraph	Telegram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/cointelegraph	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/cointelegraph/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCRqBu-g…	Youtube	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/app/cointelegraph…	Cointelegraph iOS App	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Cointelegraph Android App	new tab	Add '(opens in new tab)' to text
https://cointelegraph.com/rss-feeds	Rss Feed	new tab	Add '(opens in new tab)' to text
https://twitter.com/cointelegraph	Twitter	new tab	Add '(opens in new tab)' to text
https://telegram.me/cointelegraph	Telegram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/cointelegraph	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/cointelegraph/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCRqBu-g…	Youtube	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

126 links and buttons have descriptive text

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

https://twitter.com/cointelegraph; https://telegram.me/cointelegraph; https://www.facebook.com/cointelegraph; https://www.youtube.com/channel/UCRqBu-grVX1p97WaX4d-OuQ

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://cointelegraph-magazine.com/neo-governance-reset-pakistan-crypto-banki…; https://cointelegraph.com/rss-feeds; https://twitter.com/cointelegraph; https://telegram.me/cointelegraph; https://www.facebook.com/cointelegraph; https://www.instagram.com/cointelegraph/; https://www.youtube.com/channel/UCRqBu-grVX1p97WaX4d-OuQ; https://apps.apple.com/app/cointelegraph-crypto-news/id1640089162; https://play.google.com/store/apps/details?id=cointelegraph.com; https://cointelegraph.com/rss-feeds (+5 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

Icon-only buttons need an aria-label so screen readers can announce them.

button[data-testid="desktop-search-popover-toggle"]; button.btn (#1016 on page); button.btn (#1021 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Alt Text Quality

3 of 10 images have issues

REVIEW

3 of 10 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 image(s) with good alt text

10 images 7 good alt text 3 missing

Issue	Count
missing	3 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

Favicon & Branding

7 icon(s) detected

REVIEW

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

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 85/100 — 2 failing, 15 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.

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
MOBILE APPS `div.md:max-w-243 > div.py-4 > div.flex-none > div.text-center`
COINTELEGRAPH NEWSLETTER `div.md:max-w-243 > div.py-4 > div.flex > div.text-center`
Cointelegraph covers fintech, blockchain and Bitcoin bringing you the latest cr… `div.md:max-w-243 > div.py-4 > div.flex > div.text-center`
© Cointelegraph 2013 - 2026 `div.py-4 > div.flex > div > div`
Cointelegraph is committed to providing independent, high-quality journalism ac… `div.md:max-w-243 > div.py-4 > div.text-start > p`
All news, reviews, and analysis are produced with full journalistic independenc… `div.md:max-w-243 > div.py-4 > div.text-start > p`

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.flex > div.flex > div.w-[4.5rem] > img.image_GVcVq `div.flex > div.flex > div.w-[4.5rem] > img.image_GVcVq`
div.header-zone__flower > div.container > div.relative > img.image_GVcVq `div.header-zone__flower > div.container > div.relative > img.image_GVcVq`
ul.grid > li.group-[.inline]:mb-8 > div.rounded-lg > img.image_GVcVq `ul.grid > li.group-[.inline]:mb-8 > div.rounded-lg > img.image_GVcVq`

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.

○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-hidden="true"]` is not present on the document `<body>`

●Buttons have an accessible name

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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` 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 use only permitted ARIA attributes

○`[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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

○Heading elements appear in a sequentially-descending order

○`<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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

Landmark Structure

42 landmarks

PASS

42 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Latest Crypto & Bitcoin News

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#footer-subscription-form-input	email	Email Address	for/id
query	text		none

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Cointelegraph

192x192 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Cointelegraph ✓192×192 icon ✓512×512 icon ✗Start URL ./?utm_source=web_app_manifest ✓Display Mode standalone ✓

Name Cointelegraph Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

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)

Element	Ratio	Required	FG	BG	Result
h1 Latest Crypto & Bitc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Cointelegraph: Bitco…	12.29:1	4.5:1	#000000	#FABC2C	Pass
span Ecosystem	15.17:1	4.5:1	#000000	#FCD780	Pass
div News	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Indexes	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div In Depth	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Learn	20.82:1	4.5:1	#000000	#FEFEFE	Pass
a Podcasts	20.65:1	4.5:1	#000000	#FDFDFD	Pass
div Sponsored	20.65:1	4.5:1	#000000	#FDFDFD	Pass
div About	20.65:1	4.5:1	#000000	#FDFDFD	Pass
div LINK	20.65:1	4.5:1	#000000	#FDFDFD	Pass
div $9.40	20.65:1	4.5:1	#000000	#FDFDFD	Pass
span 0.52%	20.65:1	4.5:1	#000000	#FDFDFD	Pass
div TRX	20.65:1	4.5:1	#000000	#FDFDFD	Pass
div $0.3338	20.65:1	4.5:1	#000000	#FDFDFD	Pass
span 1.74%	20.65:1	4.5:1	#000000	#FDFDFD	Pass
div BCH	20.65:1	4.5:1	#000000	#FDFDFD	Pass
div $445.19	20.65:1	4.5:1	#000000	#FDFDFD	Pass
span 0.18%	20.82:1	4.5:1	#000000	#FEFEFE	Pass
div DOGE	21.00:1	4.5: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.