Skip to content
https://mts.ru

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO (missing!)

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
Heading Hierarchy
Action
85 headings, 4 skip(s)
FIX
85 headings, 4 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Максимум возможностей на тарифе RED
  • H2 Тариф, которым хочется делиться
  • H2 А вы уже скачали Мой МТС?
  • H2 Премьера: «Отпечатки»
  • H2 МТС Проще
  • H2 Готовьтесь к новому уровню скорости от МТС
  • H2 Максимум возможностей на тарифе RED
  • H2 Тариф, которым хочется делиться
  • H2 А вы уже скачали Мой МТС?
  • H2 Премьера: «Отпечатки»
  • H2 МТС Проще
  • H2 Готовьтесь к новому уровню скорости от МТС
  • H3 Тарифы
  • H3 Домашний интернет
  • H3 Услуги и опции
  • H3 Секретарь+
  • H3 Технологии МТС
  • H3 Семейная группа
  • H3 eSIM
  • H3 Роуминг
  • H3 Магазин
  • H3 Акции
  • H3 Нас касается
  • H3 Premium
  • H3 Защитник+
  • H3 Фильмы и сериалы
  • H3 Музыка
  • H3 Афиша и билеты
  • H3 Книги
  • H3 ТВ
  • H3 Деньги
  • H3 Детям
  • H3 Страховки
  • H3 Инвестиции
  • H3 Тарифы
  • H3 Услуги и опции
  • H3 Домашний интернет
  • H3 Технологии МТС
  • H3 Premium
  • H3 Роуминг
  • H3 Секретарь+
  • H3 Семейная группа
  • H3 Акции
  • H2 Пополнение баланса
  • H2 Поддержка
  • H2 Переходите в МТС со своим номером
  • H4 Оформить eSIM skipped
  • H4 Выбрать красивый номер
  • H4 Заказать SIM-карту
  • H4 Оформить чистый номер
  • H2 Популярное в интернет-магазине МТСПопулярное в интернет-магазине МТС
  • H4 Акции skipped
  • H4 Смартфоны
  • H4 Наушники и колонки
  • H4 Часы и трекеры
  • H4 Планшеты
  • H4 Умный дом
  • H2 Создаём цифровые сервисы и продуктыдля жизни и бизнесаСоздаём цифровые сервисы и продуктыдля жизни и бизн
  • H4 Технологии МТС skipped
  • H4 Карта покрытиясети
  • H4 Карта салонов
  • H4 Вносим вкладв будущее
  • H4 О компании
  • H4 Работа в МТС
  • H3 MTC Web Services
  • H3 Бизнесу
  • H3 Госзаказчикам
  • H3 Партнёрам
  • H3 Поставщикам
  • H3 Акционерам
  • H3 MTC Web Services
  • H3 Бизнесу
  • H3 Госзаказчикам
  • H3 Партнёрам
  • H3 Поставщикам
  • H3 Акционерам
  • H2 Скачайте Мой МТС
  • H4 Тарифы skipped
  • H4 Услуги
  • H4 Тарифы
  • H4 Услуги
  • H4 Сервисы и развлечения
  • H4 Документы
  • H4 Сервисы и развлечения
  • H4 Документы

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

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

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

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

F
Alt Text Quality
Action
71 of 101 images have issues
FIX
71 of 101 images have issues
Critical::
71 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
47 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
11 decorative image(s) correctly marked
Info::
19 image(s) with good alt text
101 images 19 good alt text 11 decorative 71 missing
IssueCount
missing71 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

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::
4 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 4 <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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Страница не найдена - Москва ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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
B
Lighthouse Accessibility Audits
Score 86/100 — 3 failing, 21 passed
REVIEW
86

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Мы собираем файлы cookie и применяем рекомендательные технологии ПОДРОБНЕЕ ПРИН… div.cdk-overlay-container > div.cdk-global-overlay-wrapper > div#cdk-overlay-2 > cdk-dialog-container#ACCEPT_COOKIE_POPUP_MODAL_ID

These are opportunities to improve the usage of ARIA in your application which 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
Москва - Москва и Московская область div.header__container > div.header__top-links > div.header__top-item > div.header__top-text
ВОЙТИ mts-profile-widget > div#profile-widget-app > div.prp-profile-b2c-widget > a.prp-button-link
Новое div.mm-web-navigation-menu-card__badge > mm-web-badge > div.mm-web-badge > span.mm-web-badge__text
ПОПОЛНИТЬ div.mm-web-button-container > div.mm-web-button-container__content > button.mm-web-action-button > span.mm-web-button__label
ВОЙТИ div.mm-web-button-container > div.mm-web-button-container__content > button.mm-web-action-button > span.mm-web-button__label
ПЕРЕЙТИ В МТС div.mm-web-button-container > div.mm-web-button-container__content > a.mm-web-link-button > span.mm-web-button__label
Это МТС section.universal-title-with-text > div.universal-title-with-text__content > div.universal-title-with-text__label > span.universal-title-with-text__label-text
14.04.2026 ul.news__list > li.news__list-item > a.news__list-link > span.news__link-date
07.04.2026 ul.news__list > li.news__list-item > a.news__list-link > span.news__link-date
07.04.2026 ul.news__list > li.news__list-item > a.news__list-link > span.news__link-date
Интернет и связь div.news-media-articles__items > a.news-media-articles__item > div.news-media-articles__description > span.news-media-articles__theme
Технологии для жизни div.news-media-articles__items > a.news-media-articles__item > div.news-media-articles__description > span.news-media-articles__theme
Гаджеты div.news-media-articles__items > a.news-media-articles__item > div.news-media-articles__description > span.news-media-articles__theme
Гаджеты div.news-media-articles__items > a.news-media-articles__item > div.news-media-articles__description > span.news-media-articles__theme
Узнать больше о приложении mts-footer-apps.footer__apps > div.footer-apps > p.footer-apps__description > a
ПРИНЯТЬ div.mm-web-button-container > div.mm-web-button-container__content > button.mm-web-action-button > span.mm-web-button__label

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●The page contains a heading, skip link, or landmark region
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○`<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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○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.
○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.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(Поиск)placeholder only

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

<input type="text">

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)
ElementRatioRequiredFGBGResult
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
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
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
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
h3 Услуги и оп…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Секретарь+21.00:13.0: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