Skip to content
https://selectel.ru

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
8
REVIEW
2
PASS
3
INFO
0
Checks
13
3 PASS 2 REVIEW 8 FIX
F
Heading Hierarchy
Action
31 headings, 5 skip(s)
FIX
31 headings, 5 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 → H5 (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: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Создавайте и развивайте цифровые продукты на базе нашей надежной IT-инфраструктуры
  • H2 Выгодные условия для старта
  • H4 GPU для ваших AI задач skipped
  • H4 Аукцион выделенных серверов
  • H4 Начислим до 30 000 бонусов на тестирование облака
  • H4 Перенесите ваши проекты в Selectel бесплатно
  • H2 Начните пользоваться продуктами сейчас
  • H2 Кейсы
  • H5 Как перейти на модель «ЦОД как сервис» skipped
  • H5 Как организовать бесперебойную работу платформы с 11 млн пользователей
  • H5 Как развернуть корпоративные сервисы в облаке
  • H5 Как снизить стоимость инфраструктуры компании на 30%
  • H2 Постройте отказоустойчивую инфраструктуру
  • H2 Ваши данные — в безопасности
  • H4 Встроенная безопасность и сертификаты skipped
  • H4 Резервирование сетей N+1 и защита от DDoS-атак
  • H4 Аттестованная инфраструктура и сервисы безопасности
  • H2 Инфраструктурой удобно и легко управлять в панели
  • H3 Для разработчиков
  • H2 За ответами — в документацию и службу технической поддержки
  • H3 Круглосуточная техподдержка
  • H3 Подробная документация
  • H2 Начните пользоваться продуктами сейчас
  • H2 Присоединяйтесь к комьюнити в Академии Selectel
  • H4 Участвуйте в мероприятиях skipped
  • H4 Разбирайтесь с технологиями по курсам и инструкциям
  • H4 Прокачайте карьеру
  • H3 Новости Selectel
  • H3 Нужна помощь?
  • H5 Сообщество skipped
  • H5 Мы используем Cookies

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

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
17 of 32 images have issues
FIX
17 of 32 images have issues
Critical::
17 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
9 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
32 images 6 good alt text 9 decorative 17 missing
IssueCount
missing17 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
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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::
2 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 2 <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
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 CONTENTINFO (missing!)

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

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 6 failing, 20 passed
REVIEW
77

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.container > div.top-banner > div.top-banner__close > button div.container > div.top-banner > div.top-banner__close > button
div.header-main__container > div.header-main__inner > div.global-search > button.global-search__btn div.header-main__container > div.header-main__inner > div.global-search > button.global-search__btn
ol > li > div.cookies > button.button ol > li > div.cookies > button.button
body.popmechanic-mobile > div#__nuxt > div.layout > button.up-button body.popmechanic-mobile > div#__nuxt > div.layout > button.up-button

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
a.flex > div.absolute > picture.absolute > img a.flex > div.absolute > picture.absolute > img
div.security-data__cards > div.security-data__cards-card > picture.security-data-card__picture > img div.security-data__cards > div.security-data__cards-card > picture.security-data-card__picture > img
div.security-data__cards > div.security-data__cards-card > picture.security-data-card__picture > img div.security-data__cards > div.security-data__cards-card > picture.security-data-card__picture > img
div.security-data__cards > div.security-data__cards-card > picture.security-data-card__picture > img div.security-data__cards > div.security-data__cards-card > picture.security-data-card__picture > img
div.management-presentation__views > div.management-presentation__views-item > picture > img div.management-presentation__views > div.management-presentation__views-item > picture > img
div.image-call-to-action > div.image-call-to-action__block-image > picture.image-call-to-action__block > img div.image-call-to-action > div.image-call-to-action__block-image > picture.image-call-to-action__block > img
a.card__material > div.material__img-wrap > picture > img a.card__material > div.material__img-wrap > picture > img
a.card__material > div.material__img-wrap > picture > img a.card__material > div.material__img-wrap > picture > img
a.card__material > div.material__img-wrap > picture > img a.card__material > div.material__img-wrap > picture > img
a.card__material > div.material__img-wrap > picture > img a.card__material > div.material__img-wrap > picture > img
a.card__material > div.material__img-wrap > picture > img a.card__material > div.material__img-wrap > picture > img
a.card__material > div.material__img-wrap > picture > img a.card__material > div.material__img-wrap > picture > 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.header-main > div.header-main__container > div.header-main__inner > a.router-link-active div.header-main > div.header-main__container > div.header-main__inner > a.router-link-active
div.footer__container > div.footer__inner > div.footer__promo > a.footer__promo-logo div.footer__container > div.footer__inner > div.footer__promo > a.footer__promo-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.

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
Рассчитайте стоимость инфраструктуры a.flex > div.flex > div.flex > div.h4
AI div.profitable-start__inner > div.flex > a.main-card > div.main-card__tag
скидка div.flex > div.xl:col-start-[14] > a.item-card > div.item-card__tag
грант div.flex > div.xl:col-start-[14] > a.item-card > div.item-card__tag
бесплатная миграция div.flex > div.xl:col-start-[14] > a.item-card > div.item-card__tag
Ответ за 15 минут div.support__cards > div.support-card > div.support-card__promo > span.py-[2px]
Бесплатно div.support__cards > div.support-card > div.support-card__promo > span.support-card__promo-note
Русская и английская версии div.support__cards > div.support-card > div.support-card__promo > span.py-[2px]
Удобный поиск div.support__cards > div.support-card > div.support-card__promo > span.support-card__promo-note

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
GPU для ваших AI задач div.profitable-start__inner > div.flex > a.main-card > h4
Как перейти на модель «ЦОД как сервис» ul#splide01-list > li#splide01-slide01 > a.case-card > h5.pr-4
Встроенная безопасность и сертификаты div.security-data__cards-card > div.security-data-card__main-info > div.security-data-card__info-wrapper > h4.security-data-card__title
Участвуйте в мероприятиях div.academy > div.academy__grid > div.call-to-action__card > h4.card__title
Сообщество div.footer__container > div.footer__inner > div.footer-socials > h5.footer-socials__title

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.popmechanic-android html.popmechanic-android

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

○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
●Form elements have associated labels
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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
●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
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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
○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
All 11 controls labeled
PASS
All 11 controls labeled
Info::
11 control(s) properly labeled
11 controls
11 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
searchsearchnone
searchsearchnone
searchsearchnone
searchsearchnone
searchsearchnone
emailemailЭлектронная почтаnone
passwordpasswordПридумайте пароль Сгенерироватьnone
checkboxcheckboxnone
emailemailЭлектронная почтаnone
passwordpasswordПридумайте пароль Сгенерироватьnone
checkboxcheckboxnone
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Ошибка 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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
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 Новости Selec…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Нужна помо…21.00:13.0:1
#000000
#FFFFFF
Pass
title IT-инфрастр…21.00:14.5:1
#000000
#FFFFFF
Pass
div Москва, 22 а…21.00:14.5:1
#000000
#FFFFFF
Pass
span МЛечный пу…21.00:14.5:1
#000000
#FFFFFF
Pass
a Зарегистри…21.00:14.5:1
#000000
#FFFFFF
Pass
span ENG21.00:14.5:1
#000000
#FFFFFF
Pass
span Скорость с…21.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