Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 3 REVIEW 8 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

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

Alt Text Quality

Action

7 of 7 images have issues

FIX

7 of 7 images have issues

7 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 image-in-link without alt text

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

7 images 7 missing

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

Link & Button Quality

Action

34 issue(s) across 49 links and 45 buttons

FIX

34 issue(s) across 49 links and 45 buttons

8 link(s) with no accessible text

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

Got: https://teletype.in/; https://teletype.in/@autohumanism/Yre_JqRnrRy; https://blog.tema.ru/tffOotAQxDg; https://teletype.in/@greatstruggle/hamburg-masch-verfassungsschutz; https://teletype.in/@catx2/DhEFxQmQ426; https://teletype.in/@history_math/medianta-dvuh-drobei; https://blog.cassiopeia.center/opisanie-predstavitelya-reptiloidnoj-civilizac…; https://teletype.in/@catx2/qxSkyA1gxs7

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://teletype.in/about ("Learn more")

25 button(s) with no accessible text

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

Got: button.tab (#119 on page); button.articleInfo-item (#170 on page); button.iconButton (#183 on page); button.articleInfo-item (#235 on page); button.iconButton (#248 on page); button.articleInfo-item (#273 on page); button.articleInfo-item (#284 on page); button.iconButton (#297 on page); button.articleInfo-item (#334 on page); button.iconButton (#347 on page) (+15 more)

40 link(s) with descriptive text

49 links

8 empty

1 generic text

0 new tab

25 empty buttons

Element	Text	Issue	Suggested Fix
https://teletype.in/	(empty)	empty	Add link text or aria-label
https://teletype.in/@autohumanism/Yre_Jq…	(empty)	empty	Add link text or aria-label
https://teletype.in/about	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: About
https://blog.tema.ru/tffOotAQxDg	(empty)	empty	Add link text or aria-label
https://teletype.in/@greatstruggle/hambu…	(empty)	empty	Add link text or aria-label
https://teletype.in/@catx2/DhEFxQmQ426	(empty)	empty	Add link text or aria-label
https://teletype.in/@history_math/median…	(empty)	empty	Add link text or aria-label
https://blog.cassiopeia.center/opisanie-…	(empty)	empty	Add link text or aria-label
https://teletype.in/@catx2/qxSkyA1gxs7	(empty)	empty	Add link text or aria-label
<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
<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
<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
<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
<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
<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
<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
<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
<button>	(empty)	empty	Add button text or aria-label

60 links and buttons have descriptive text

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

https://teletype.in/; https://teletype.in/@autohumanism/Yre_JqRnrRy; https://blog.tema.ru/tffOotAQxDg; https://teletype.in/@greatstruggle/hamburg-masch-verfassungsschutz; https://teletype.in/@catx2/DhEFxQmQ426; https://teletype.in/@history_math/medianta-dvuh-drobei; https://blog.cassiopeia.center/opisanie-predstavitelya-reptiloidnoj-civilizac…; https://teletype.in/@catx2/qxSkyA1gxs7

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

Generic link text like 'click here' doesn't describe the destination.

https://teletype.in/about ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

button.tab (#119 on page); button.articleInfo-item (#170 on page); button.iconButton (#183 on page); button.articleInfo-item (#235 on page); button.iconButton (#248 on page); button.articleInfo-item (#273 on page); button.articleInfo-item (#284 on page); button.iconButton (#297 on page); button.articleInfo-item (#334 on page); button.iconButton (#347 on page) (+15 more)

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

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Lighthouse Accessibility Audits

Action

Score 52/100 — 6 failing, 8 passed

FIX

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.m_hidden > div.feed-nav > div.feed-nav-wrap > button.tab `div.m_hidden > div.feed-nav > div.feed-nav-wrap > button.tab`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`
div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item `div.articleCard-info > div.articleInfo > div.articleInfo-info > button.articleInfo-item`

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.articleCard-article > figure.articleCard-image > a > img `div.articleCard-article > figure.articleCard-image > a > img`
div.articleCard-article > figure.articleCard-image > a > img `div.articleCard-article > figure.articleCard-image > a > img`
div.articleCard-article > figure.articleCard-image > a > img `div.articleCard-article > figure.articleCard-image > a > img`
div.articleCard-article > figure.articleCard-image > a > img `div.articleCard-article > figure.articleCard-image > a > img`
div.articleCard-article > figure.articleCard-image > a > img `div.articleCard-article > figure.articleCard-image > a > img`
div.articleCard-article > figure.articleCard-image > a > img `div.articleCard-article > figure.articleCard-image > a > img`
div.articleCard-article > figure.articleCard-image > a > img `div.articleCard-article > figure.articleCard-image > a > 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.menu > div.menu__content > div.menu__item > a.router-link-active `div.menu > div.menu__content > div.menu__item > a.router-link-active`
div.articleCard-content > div.articleCard-article > figure.articleCard-image > a `div.articleCard-content > div.articleCard-article > figure.articleCard-image > a`
div.articleCard-content > div.articleCard-article > figure.articleCard-image > a `div.articleCard-content > div.articleCard-article > figure.articleCard-image > a`
div.articleCard-content > div.articleCard-article > figure.articleCard-image > a `div.articleCard-content > div.articleCard-article > figure.articleCard-image > a`
div.articleCard-content > div.articleCard-article > figure.articleCard-image > a `div.articleCard-content > div.articleCard-article > figure.articleCard-image > a`
div.articleCard-content > div.articleCard-article > figure.articleCard-image > a `div.articleCard-content > div.articleCard-article > figure.articleCard-image > a`
div.articleCard-content > div.articleCard-article > figure.articleCard-image > a `div.articleCard-content > div.articleCard-article > figure.articleCard-image > a`
div.articleCard-content > div.articleCard-article > figure.articleCard-image > a `div.articleCard-content > div.articleCard-article > figure.articleCard-image > 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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Гендерная нейтральность `div.articleCard-content > div.articleCard-article > h2.articleCard-title > a`
Выборы `div.articleCard-content > div.articleCard-article > h2.articleCard-title > a`

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

●Form elements have associated labels

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Heading elements appear in a sequentially-descending order

●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

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

○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

○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

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

Heading Hierarchy

10 headings

REVIEW

10 headings

No H1 heading found

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

H2 Персональный ад: Комфортно vs Привычно
H2 Гендерная нейтральность
H2 № 715 Боня обратилась к Путину / Коллапс в аэропортах ЕС / Хирург перепутал органы
H2 Выборы
H2 Гамбургский кружок экстремалов особо опасного чтения
H2 Иудейские войны 4. Конец Иудеи
H2 Медианта двух дробей: «сумма первокурсника»
H2 Люди, кто разбирается в типографском деле?
H2 Описание представителя рептилоидной цивилизации с планеты Дахриша
H2 Одиссея «Лебедя востока» Часть 4 Остров Паган

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input>

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	input	(Search...)	placeholder only

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

<input>

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

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
title Teletype	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span About Teletype	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Join	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Trending	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Following	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Михаил Мур�…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 17h	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Персональн…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p © Михаил Му…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 1 400	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Join Teletype Today	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Monetize your storie…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Join	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Learn more	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Артемий Ле�…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Гендерная �…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Самая боль�…	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span 2.3K	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Артемий Ле�…	11.07:1	4.5:1	#000000	#FEAA4D	Pass
a № 715 Боня о�…	10.46:1	4.5:1	#000000	#D2B195	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.