Skip to content
https://moe.video

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
B
Form Accessibility
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="client_e" id="client_e">; <input type="text" name="client_nt" id="client_nt">; <input type="text" name="client_n" id="client_n">; <textarea name="client_m" id="client_m">
4 controls
0 labeled
4 placeholder only
0 unlabeled
ControlTypeLabelMethod
#client_eemail(E-mail)placeholder only
#client_nttext(Номер телефона/ник в телеграме)placeholder only
#client_ntext(Имя)placeholder only
#client_mtextarea(Здесь Вы можете оставить название сайта, его посещаемость или любую другую информацию, которая поможет нам подготовить для Вас коммерческое предложение)placeholder only

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

<input type="email" name="client_e" id="client_e">; <input type="text" name="client_nt" id="client_nt">; <input type="text" name="client_n" id="client_n">; <textarea name="client_m" id="client_m">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 74/100 — 4 failing, 15 passed
REVIEW
74

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#stickyNav > div.content > div.w-full > button#mobileNavToggle div#stickyNav > div.content > div.w-full > button#mobileNavToggle

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
body.bg-white > iframe body.bg-white > iframe

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.

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
12+ лет section.content > ul.w-full > li.text-brand-copy > span.block
90+ тыс section.content > ul.w-full > li.text-brand-copy > span.block
100+ млрд section.content > ul.w-full > li.text-brand-copy > span.block
150 млн section.content > ul.w-full > li.text-brand-copy > span.block
> 90% section.content > ul.w-full > li.text-brand-copy > span.block
CTR 1,5% section.content > ul.w-full > li.text-brand-copy > span.block
Для паблишеров section.content > div.w-full > div.w-full > h3.font-semibold
Для рекламодателей section.content > div.w-full > div.w-full > h3.font-semibold
Работаем в соответствии с требованиями федерального законодательства body.bg-white > main.w-full > section.content > h2.section-heading-blue
Своевременно исполняем требования ст.18.1 ФЗ № 38 “О рекламе” от 13.03.2006 и о… body.bg-white > main.w-full > section.content > p.text-lg
31.03.2026 div.w-full > div.rounded-lg > div.w-full > div.text-brand-copy/50
Подробнее div.w-full > div.rounded-lg > div.w-full > a.font-semibold
12.02.2026 div.w-full > div.rounded-lg > div.w-full > div.text-brand-copy/50
Подробнее div.w-full > div.rounded-lg > div.w-full > a.font-semibold
05.12.2025 div.w-full > div.rounded-lg > div.w-full > div.text-brand-copy/50
Подробнее div.w-full > div.rounded-lg > div.w-full > a.font-semibold

These are opportunities to improve the legibility of your content.

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

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>`
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●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 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
○`<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
○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.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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
11 headings
PASS
11 headings
Info::
Single H1 present
  • H1 Повышайте доход вашего сайта с MOEVIDEO
  • H2 MoeVideo — рекламная сеть, которая позволяет вебмастерам зарабатывать на своем сайте с помощью размещения рекла
  • H3 Для паблишеров
  • H3 Для рекламодателей
  • H2 Наши главные преимущества
  • H2 Работаем в соответствии с требованиями федерального законодательства
  • H2 Отзывы партнеров
  • H2 Новости
  • H3 Какую видеорекламу выбрать: In-stream или Out-stream?
  • H3 Viewability рекламы: что это, как измерять и улучшать?
  • H3 Россияне всё активнее полагаются на пользовательский контент: новое исследование 2025 года
A+
Alt Text Quality
All 23 images OK
PASS
All 23 images OK
Info::
20 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
23 images 3 good alt text 20 decorative
All images have appropriate alt text.
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
h1 Повышайте …7.76:13.0:1
#000000
#00A5FA
Pass
h2 MoeVideo — рек…7.83:13.0:1
#000000
#00A6FA
Pass
h2 Наши главн…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Работаем в …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Отзывы пар…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Новости21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Для паблиш…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Для реклам…21.00:13.0:1
#000000
#FFFFFF
Pass
title MoeVideo - рекл…7.83:14.5:1
#000000
#00A6FA
Pass
a Рекламные …7.83:14.5:1
#000000
#00A6FA
Pass
a Рекламодат…7.76:14.5:1
#000000
#00A5FA
Pass
a Новости7.76:14.5:1
#000000
#00A5FA
Pass
a Команда7.76:14.5:1
#000000
#00A5FA
Pass
a Контакты7.76:14.5:1
#000000
#00A5FA
Pass
a Войти7.76:14.5:1
#000000
#00A5FA
Pass
p Монетизаци…7.83:14.5:1
#000000
#00A6FA
Pass
button Стать парт…7.83:14.5:1
#000000
#00A6FA
Pass
span 12+ лет7.83:14.5:1
#000000
#00A6FA
Pass
li на рынке digi…7.83:14.5:1
#000000
#00A6FA
Pass
span 90+ тыс7.83:14.5:1
#000000
#00A6FA
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