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 5 REVIEW 6 FIX

Landmark Structure

Action

No landmarks

FIX

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

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

Form Accessibility

Action

4 of 5 controls have issues

FIX

4 of 5 controls have issues

3 control(s) without accessible label

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

Got: <input type="text" name="q">; <input type="checkbox" id="footer__search-form__checkbox">; <input type="submit" name="search">

1 control(s) rely on placeholder only

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

Got: <input type="search" name="q">

1 control(s) properly labeled

5 controls

1 labeled

1 placeholder only

3 unlabeled

Control	Type	Label	Method
input	submit		none
q	search	(Search)	placeholder only
#footer__search-form__checkbox	checkbox	(none)	none
q	text	(none)	none
search	submit	(none)	none

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

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

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

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

Link & Button Quality

Action

35 issue(s) across 253 links and 3 buttons

FIX

35 issue(s) across 253 links and 3 buttons

33 link(s) with no accessible text

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

Got: https://www.liveinternet.ru/click;RTNEWS; https://t.me/rtnews; https://www.rt.com/rss-feeds/; //twitter.com/RT_com; //vk.com/rt_international; //rumble.com/c/RTNews; //odysee.com/@RT:fd; a.js-mobile-element-nav (#386 on page); a.js-mobile-element-nav (#392 on page); https://t.me/rtnews (+23 more)

1 link(s) with generic text

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

Got: # ("More")

17 link(s) open in new tab without warning

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

Got: //arabic.rt.com/; //actualidad.rt.com/; //russian.rt.com/; //de.rt.com/; //francais.rt.com/; //rt.rs/; //russian.rt.com/inotv; //en.arteldoc.tv/; //gw2ru.com/; //ruptly.agency/ (+7 more)

1 button(s) with no accessible text

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

Got: input[type="submit"].visually-hidden (#1638 on page)

202 link(s) with descriptive text

253 links

33 empty

1 generic text

17 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.liveinternet.ru/click;RTNEWS	(empty)	empty	Add link text or aria-label
//arabic.rt.com/	العربية	new tab	Add '(opens in new tab)' to text
//actualidad.rt.com/	ESP	new tab	Add '(opens in new tab)' to text
//russian.rt.com/	РУС	new tab	Add '(opens in new tab)' to text
//de.rt.com/	DE	new tab	Add '(opens in new tab)' to text
//francais.rt.com/	FR	new tab	Add '(opens in new tab)' to text
//rt.rs/	RS	new tab	Add '(opens in new tab)' to text
//russian.rt.com/inotv	RT	new tab	Add '(opens in new tab)' to text
//en.arteldoc.tv/	RT	new tab	Add '(opens in new tab)' to text
//gw2ru.com/	RT	new tab	Add '(opens in new tab)' to text
//ruptly.agency/	RT	new tab	Add '(opens in new tab)' to text
//academy.rt.com/	RT	new tab	Add '(opens in new tab)' to text
https://t.me/rtnews	(empty)	empty	Add link text or aria-label
https://www.rt.com/rss-feeds/	(empty)	empty	Add link text or aria-label
//twitter.com/RT_com	(empty)	empty	Add link text or aria-label
//vk.com/rt_international	(empty)	empty	Add link text or aria-label
//rumble.com/c/RTNews	(empty)	empty	Add link text or aria-label
//odysee.com/@RT:fd	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://t.me/rtnews	(empty)	empty	Add link text or aria-label
https://www.rt.com/rss-feeds/	(empty)	empty	Add link text or aria-label
//twitter.com/RT_com	(empty)	empty	Add link text or aria-label
//vk.com/rt_international	(empty)	empty	Add link text or aria-label
//rumble.com/c/RTNews	(empty)	empty	Add link text or aria-label
//odysee.com/@RT:fd	(empty)	empty	Add link text or aria-label
/russia/638837-ukraine-sbu-draft-enforce…	(empty)	empty	Add link text or aria-label
/africa/638751-pope-leo-prays-angola-sla…	(empty)	empty	Add link text or aria-label
#	More	generic text	Replace with descriptive text
Before: More Suggested: #
//russian.rt.com/inotv	RT	new tab	Add '(opens in new tab)' to text
//en.arteldoc.tv/	RT	new tab	Add '(opens in new tab)' to text
//gw2ru.com/	RT	new tab	Add '(opens in new tab)' to text
//ruptly.agency/	RT	new tab	Add '(opens in new tab)' to text
//academy.rt.com/	RT	new tab	Add '(opens in new tab)' to text
https://t.me/rtnews	(empty)	empty	Add link text or aria-label
https://www.rt.com/rss-feeds/	(empty)	empty	Add link text or aria-label
//twitter.com/RT_com	(empty)	empty	Add link text or aria-label
//vk.com/rt_international	(empty)	empty	Add link text or aria-label
//rumble.com/c/RTNews	(empty)	empty	Add link text or aria-label
//odysee.com/@RT:fd	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://www.rt.com/privacy-policy/	Privacy policy	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
<input>	(empty)	empty	Add button text or aria-label

204 links and buttons have descriptive text

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

https://www.liveinternet.ru/click;RTNEWS; https://t.me/rtnews; https://www.rt.com/rss-feeds/; //twitter.com/RT_com; //vk.com/rt_international; //rumble.com/c/RTNews; //odysee.com/@RT:fd; a.js-mobile-element-nav (#386 on page); a.js-mobile-element-nav (#392 on page); https://t.me/rtnews (+23 more)

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.

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

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

//arabic.rt.com/; //actualidad.rt.com/; //russian.rt.com/; //de.rt.com/; //francais.rt.com/; //rt.rs/; //russian.rt.com/inotv; //en.arteldoc.tv/; //gw2ru.com/; //ruptly.agency/ (+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

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

input[type="submit"].visually-hidden (#1638 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

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

3 headings

REVIEW

3 headings

No H1 heading found

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

H2 Top stories
H2 Top stories
H2 Opinion

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

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 icon fm ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

8 icon(s) detected

REVIEW

8 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA 1 pass AA only

title RT - Breaking News, Russia News, World N…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a العربية

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a ESP

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a РУС

1.59:1

#000000

#303030

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title RT - Breaking News, …	1.00:1	4.5:1	#000000	#000000	Fail
a العربية	1.00:1	4.5:1	#000000	#000000	Fail
a ESP	1.00:1	4.5:1	#000000	#000000	Fail
a РУС	1.59:1	4.5:1	#000000	#303030	Fail
div Where to watch	5.54:1	4.5:1	#000000	#838383	Pass
div Schedule	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div RT News App	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Question more	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a EU will bankroll Ukr…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a live	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Russia & Former Sovi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a World News	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Business	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a India	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Africa	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a RT Features	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Analysis	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Opinion	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Entertainment	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Shows	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.

Lighthouse Accessibility Audits

Score 85/100 — 4 failing, 19 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
LIVE `div.header__main-wrapper > div.header__line > div.header__live > a.live-button`
EXCLUSIVE `li.main-promobox__item > a.main-promobox__heading > div.main-promobox__wrapper > span.category-tag`
EXCLUSIVE `div.Section-block > div.article-card > div.article-card__title > span.category-tag`
© Autonomous Nonprofit Organization “TV-Novosti”, 2005–2026. All rights reserve… `div.footer__copiright__BlockWrapper > div.footer__copyright_block > div.copyright__text > p`

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.Section-container > div.Section-block > div#mainnews_2 > iframe#odysee-iframe `div.Section-container > div.Section-block > div#mainnews_2 > iframe#odysee-iframe`
div.Section-container > div.Section-block > div#mainnews_3 > iframe#odysee-iframe `div.Section-container > div.Section-block > div#mainnews_3 > iframe#odysee-iframe`

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
body > a.visually-hidden `body > a.visually-hidden`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.main-promobox__cover > div.media > div.media__image > a.link `div.main-promobox__cover > div.media > div.media__image > a.link`
div.article-card__cover > div.media > div.media__image > a.link `div.article-card__cover > div.media > div.media__image > a.link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__copiright__BlockWrapper > div.footer__copyright_block > div.copyright__logo > a `div.footer__copiright__BlockWrapper > div.footer__copyright_block > div.copyright__logo > 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

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-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

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

●Heading elements appear in a sequentially-descending order

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

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

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

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

Alt Text Quality

All 65 images OK

PASS

All 65 images OK

6 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

58 image(s) with good alt text

65 images 58 good alt text 1 decorative

Issue	Count
too long	6 image(s)

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: RT in English

192x192 icon present

Display mode: fullscreen

PWA Install Criteria ✓ Installable

Name RT in English ✓192×192 icon ✓512×512 icon ✗Start URL https://www.rt.com/?utm_source=homescreen_android&utm_medium=tap&utm_campaign=homescreen ✓Display Mode fullscreen ✓

Name RT in English Display Mode fullscreen Theme Color green Background Color green Icons 1 icon(s)

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.