Skip to content
https://t.me

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
9
REVIEW
2
PASS
2
INFO
0
Checks
13
2 PASS 2 REVIEW 9 FIX
D
Landmark Structure
Action
No landmarks
FIX
No 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
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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
Alt Text Quality
Action
11 of 11 images have issues
FIX
11 of 11 images have issues
Critical::
11 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
11 images 11 missing
IssueCount
missing11 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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-2chj04
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://t.me/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://t.me/manifest.json

Manifest contains invalid JSON.

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.
D
Lighthouse Accessibility Audits
Action
Score 60/100 — 6 failing, 9 passed
FIX
60

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
EN div.container > ul.nav > li.dropdown > a.dropdown-toggle
Home div.container > ul.nav > li.active > a
FAQ div.container > ul.nav > li > a
Apps div.container > ul.nav > li > a
a new era of messaging div.tl_main_wrap > div.tl_main_head > div.tl_main_logo_wrap > p.tl_main_logo_lead
Telegram for Android div.tl_page > div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link
Android div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link > b
Recent News div.tl_main_wrap > div.tl_main_recent_news_wrap > h3.tl_main_recent_news_header > a
AI Editor, Mighty Polls, Live Photos, Bots Managed by Bots, and More a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > div.dev_blog_card_alltext_wrap > h4.dev_blog_card_title
Mar 31, 2026 div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > div.dev_blog_card_date
Member Tags, Login with Telegram, Disable Sharing, GIF Editing, Date Formatting… a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > div.dev_blog_card_alltext_wrap > h4.dev_blog_card_title
Mar 1, 2026 div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > div.dev_blog_card_date
Browse more Telegram apps div.tl_page > div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_more_btn
API div.tl_main_card_cell > div.tl_main_card_wrap > div.tl_main_card_lead > a
ABOUT div.footer_columns_wrap > div.footer_column > h5 > a
BLOG div.footer_columns_wrap > div.footer_column > h5 > a
PRESS div.footer_columns_wrap > div.footer_column > h5 > a
MODERATION div.footer_columns_wrap > div.footer_column > h5 > a

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
ABOUT div.footer_wrap > div.footer_columns_wrap > div.footer_column > h5

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image
div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image

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
Telegram div.tl_main_wrap > div.tl_main_head > div.tl_main_logo_wrap > a.tl_main_logo

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
●`[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
●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.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
○`[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
○Buttons have an accessible name
○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 a valid value for its `[lang]` attribute
○`<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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
C
Heading Hierarchy
Action
23 headings, 1 skip(s)
REVIEW
23 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H5 (missing H4)
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.
  • H3 (empty)
  • H3 Recent News
  • H4 AI Editor, Mighty Polls, Live Photos, Bots Managed by Bots, and More
  • H4 Member Tags, Login with Telegram, Disable Sharing, GIF Editing, Date Formatting, Voting Timestamps
  • H3 Why Telegram?
  • H3 Simple
  • H3 Private
  • H3 Synced
  • H3 Fast
  • H3 Powerful
  • H3 Open
  • H3 Secure
  • H3 Social
  • H3 Expressive
  • H5 Telegram skipped
  • H5 About
  • H5 Mobile Apps
  • H5 Desktop Apps
  • H5 Platform
  • H5 About
  • H5 Blog
  • H5 Press
  • H5 Moderation

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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
h3 Why Telegram?21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Simple21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Private21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Synced21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Fast21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Powerful21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Open21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Secure21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Social21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Expressive21.00:13.0:1
#000000
#FFFFFF
Pass
title Telegram Messenger21.00:14.5:1
#000000
#FFFFFF
Pass
a English21.00:14.5:1
#000000
#FFFFFF
Pass
a Bahasa Indonesia21.00:14.5:1
#000000
#FFFFFF
Pass
a Bahasa Melayu21.00:14.5:1
#000000
#FFFFFF
Pass
a Deutsch21.00:14.5:1
#000000
#FFFFFF
Pass
a Español21.00:14.5:1
#000000
#FFFFFF
Pass
a Français21.00:14.5:1
#000000
#FFFFFF
Pass
a Italiano21.00:14.5:1
#000000
#FFFFFF
Pass
a Nederlands21.00:14.5:1
#000000
#FFFFFF
Pass
a O‘zbek21.00:14.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.

Send Feedback