Skip to content
https://omegait.ru

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
5
REVIEW
7
PASS
12
INFO
0
Checks
24
12 PASS 7 REVIEW 5 FIX
F
Heading Hierarchy
Action
50 headings, 5 skip(s)
FIX
50 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
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.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 маркетинговое агентство полного цикла
  • H4 мы честно оцениваем возможности, строго соблюдаем договор и доводим проекты до успешного завершения skipped
  • H2 что мы делаем
  • H4 Поможем выстроить систему лидогенерации, которая приносит прибыль skipped
  • H3 разработка сайтов
  • H3 контекстная реклама
  • H3 seo-оптимизация
  • H3 другое
  • H2 АКЦИИ
  • H3 SEO‑оптимизация
  • H3 Контекстная реклама + SEO‑оптимизация
  • H3 контекстная реклама
  • H2 ключевые сферы
  • H4 Сделаем сайт и привлечем клиентов в любой бизнес, но именно в этих сферах у нас больше всего успешно реализов� skipped
  • H3 bitrix
  • H3 tilda
  • H3 wordpress
  • H3 интернет-магазин
  • H3 консалтинг
  • H3 культура
  • H3 медицина
  • H3 недвижимость
  • H3 образование
  • H3 производство
  • H3 реклама
  • H3 строительство
  • H3 франшиза
  • H2 Оставьте заявку на бесплатную консультацию
  • H2 Кейсы
  • H2 делаем результатыот канады до китая
  • H2 отзывы
  • H4 Представители девелопера SD GROUP skipped
  • H4 Елизавета Насонова
  • H2 свяжитесь с нами
  • H4 позвоните skipped
  • H4 напишите
  • H4 приходите
  • H3 или оставьте свои данные и мы свяжемся с вами:
  • H2 ответы на частые вопросы
  • H3 Чем занимается рекламное digital-агенство it omega в новосибирске?
  • H3 Клиентов какой сферы продвигает ваша компания?
  • H3 Как происходит общение в процессе работы?
  • H3 Что делать, если я ничего не понимаю в продвижении и интернет-маркетинге?
  • H3 Почему я должен выбрать именно вас?
  • H3 Оставьте заявку на бесплатную консультацию
  • H3 Рассчитать стоимость разработки сайта
  • H3 Заказать аудит текущего сайта
  • H3 Подберем бюджет, который даст результат
  • H3 Бесплатно проанализируем вашу рекламу
  • H3 Настройка файлов cookie

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
39 of 39 images have issues
FIX
39 of 39 images have issues
Critical::
39 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
18 image-in-link without alt text
An image inside a link with no alt creates an empty link.
39 images 39 missing
IssueCount
missing39 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
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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 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

C
Form Accessibility
Action
7 of 53 controls have issues
REVIEW
7 of 53 controls have issues
Critical::
7 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">
Info::
46 control(s) properly labeled
53 controls
46 labeled
0 placeholder only
7 unlabeled
ControlTypeLabelMethod
your-nametextВаше имя*none
your-phonetel+7 999 999 99 99*none
your-emailtextEmailnone
your-servicestextИнтересующая услугаnone
checkedcheckboxnone
your-nametextВаше имя*none
your-phonetel+7 999 999 99 99*none
your-emailtextEmailnone
your-servicestextИнтересующая услугаnone
checkedcheckboxnone
your-nametextВаше имя*none
your-phonetel+7 999 999 99 99*none
your-emailtextEmailnone
your-servicestextИнтересующая услугаnone
checkedcheckboxnone
your-nametextВаше имя*none
your-phonetel+7 999 999 99 99*none
your-servicestextКакой сайт вам нужен?none
your-linktextСсылка на ваш текущий сайт (если есть)none
your-reftextКраткое описание задачи или ссылки на сайты, которые вам нравятсяnone
your-tzfileПрикрепить файл (ТЗ или бриф, если есть)none
checked-2checkboxnone
your-nametextВаше имя*none
your-phonetel+7 999 999 99 99*none
your-linktextСсылка на ваш текущий сайт (если есть)none
checkedcheckboxnone
your-nametextВаше имя*none
your-phonetel+7 999 999 99 99*none
your-linktextПрикрепите ссылку на ваш сайтnone
your-citiestextВ каких городах вы хотите продвигаться?none
your-producttextКакой продукт или услугу хотите продвигать?none
your-prev-exptextЗапускали контекстную рекламу ранее?none
your-budgettextКакой бюджет готовы выделить на продвижение?none
checkedcheckboxnone
your-nametextВаше имя*none
your-phonetel+7 999 999 99 99*none
your-linktextПрикрепите ссылку на ваш сайтnone
your-prev-exptextЗапускали контекстную рекламу ранее?none
your-prev-budgettextЕсли да, с каким бюджетом продвигались?none
your-prev-resulttextВас устраивал результат?none
your-leadstextСколько заявок хотите получать ежемесячно?none
your-future-budgettextКакой бюджет готовы выделить на продвижение?none
checkedcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">

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

C
Mobile-Readable Font Sizes
Action
72% of visible text renders at >= 12 CSS px (59 below threshold)
REVIEW
72% of visible text renders at >= 12 CSS px (59 below threshold)
Warning::
59 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 11.5px ("40 000 ₽/мес"); <a> 9.4px ("Оставить заявку"); <a> 9.4px ("Оставить заявку"); <p> 11.5px ("40 000 ₽/мес"); <a> 9.4px ("Оставить заявку").
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Страница не найдена - OmegaIT ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: MyWebSite
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name MyWebSite ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name MyWebSite Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
B
Lighthouse Accessibility Audits
Score 86/100 — 5 failing, 27 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, чтобы улучшить ваш опыт на сайте. Нажимая "Принять"… body.home > div.f152-banner

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
ЧТО МЫ ДЕЛАЕМ main#content > section > div.flex > h2.title-h2
ПОМОЖЕМ ВЫСТРОИТЬ СИСТЕМУ ЛИДОГЕНЕРАЦИИ, КОТОРАЯ ПРИНОСИТ ПРИБЫЛЬ section > div.flex > div.flex > h4.animation-text
АКЦИИ main#content > section > div.flex > h2.title-h2
Наружная реклама div.flex > div.flex > p > a
КЕЙСЫ main#content > section > div.flex > h2.title-h2
ДЕЛАЕМ РЕЗУЛЬТАТЫ ОТ КАНАДЫ ДО КИТАЯ main#content > section > div.flex > h2.title-h2
ПОЗВОНИТЕ div.flex > ul.flex > li.flex > h4.animation-text
+7 (383) 202-13-02 ul.flex > li.flex > div.flex > a.h3
НАПИШИТЕ div.flex > ul.flex > li.flex > h4.animation-text
POTEMINN@GMAIL.COM ul.flex > li.flex > div.flex > a.h3
МАХ ul.flex > li.flex > div.flex > a.h3
TELEGRAM ul.flex > li.flex > div.flex > a.h3
ПРИХОДИТЕ div.flex > ul.flex > li.flex > h4.animation-text
Г. НОВОСИБИРСК, УЛ. ДЕПУТАТСКАЯ, 2 ul.flex > li.flex > div.flex > p.h3
ПН-ПТ: 9:00 – 18:00 ul.flex > li.flex > div.flex > p.h4
ИЛИ ОСТАВЬТЕ СВОИ ДАННЫЕ И МЫ СВЯЖЕМСЯ С ВАМИ: div.flex > div.flex > div.flex > h3.animation-text
Наружная реклама div.flex > div.flex > p > a

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
МЫ ЧЕСТНО ОЦЕНИВАЕМ ВОЗМОЖНОСТИ, СТРОГО СОБЛЮДАЕМ ДОГОВОР И ДОВОДИМ ПРОЕКТЫ ДО … div.flex > div.flex > div.flex > h4
ПОМОЖЕМ ВЫСТРОИТЬ СИСТЕМУ ЛИДОГЕНЕРАЦИИ, КОТОРАЯ ПРИНОСИТ ПРИБЫЛЬ section > div.flex > div.flex > h4.animation-text
СДЕЛАЕМ САЙТ И ПРИВЛЕЧЕМ КЛИЕНТОВ В ЛЮБОЙ БИЗНЕС, НО ИМЕННО В ЭТИХ СФЕРАХ У НАС… section > div.flex > div.flex > h4
ПРЕДСТАВИТЕЛИ ДЕВЕЛОПЕРА SD GROUP div#swiper-wrapper-d4f96c4e571e8bee > div.flex > div.flex > h4
ПОЗВОНИТЕ div.flex > ul.flex > li.flex > h4.animation-text

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.flex > div.flex > a.header-social > img div.flex > div.flex > a.header-social > img
div.flex > div.flex > a.header-social > img div.flex > div.flex > a.header-social > img
div.flex > div.flex > a.header-social > img div.flex > div.flex > a.header-social > img
div.flex > div.flex > a.header-social > img div.flex > div.flex > a.header-social > img
div.flex > div.flex > div.flex > img div.flex > div.flex > div.flex > img
div.flex > div.flex > div.flex > img div.flex > div.flex > div.flex > img
div.flex > div.flex > div.flex > img div.flex > div.flex > div.flex > img
ul#keys-box > li.flex > a.keys-img-box > img ul#keys-box > li.flex > a.keys-img-box > img
ul#keys-box > li.flex > a.keys-img-box > img ul#keys-box > li.flex > a.keys-img-box > img
ul#keys-box > li.flex > a.keys-img-box > img ul#keys-box > li.flex > a.keys-img-box > img
ul#keys-box > li.flex > a.keys-img-box > img ul#keys-box > li.flex > a.keys-img-box > img
ul#keys-box > li.flex > a.keys-img-box > img ul#keys-box > li.flex > a.keys-img-box > img
ul#keys-box > li.flex > a.keys-img-box > img ul#keys-box > li.flex > a.keys-img-box > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img div.swiper > div#swiper-wrapper-4a8f59815be81026 > div.swiper-slide > img
div.flex > div.flex > a.footer-social > img div.flex > div.flex > a.footer-social > img
div.flex > div.flex > a.footer-social > img div.flex > div.flex > a.footer-social > img
div.flex > div.flex > a.footer-social > img div.flex > div.flex > a.footer-social > img
div.flex > div.flex > a.footer-social > img div.flex > div.flex > a.footer-social > 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
header.flex > div.flex > div.flex > a.header-phone header.flex > div.flex > div.flex > a.header-phone
div.flex > div.flex > div.flex > a.header-social div.flex > div.flex > div.flex > a.header-social
div.flex > div.flex > div.flex > a.header-social div.flex > div.flex > div.flex > a.header-social
div.flex > div.flex > div.flex > a.footer-social div.flex > div.flex > div.flex > a.footer-social
div.flex > div.flex > div.flex > a.footer-social div.flex > div.flex > div.flex > a.footer-social

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.

○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
●Input buttons have discernible text.
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<frame>` or `<iframe>` elements have a title
●`<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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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.
○`<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+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A
Form Input Types
3 input(s) using type=text where a specific type would help
PASS
3 input(s) using type=text where a specific type would help
Info::
Input "your-email" should use type="email" (currently type="text")
Field name "your-email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "your-email" should use type="email" (currently type="text")
Field name "your-email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "your-email" should use type="email" (currently type="text")
Field name "your-email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
53 form control(s) checked, no input-semantic issues
PASS
53 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "ru-RU"
PASS
Lang attribute set to "ru-RU"
Info::
<html lang="ru-RU"> is set and valid
Got: ru-RU
A+
Tabindex Anti-Patterns
10 explicit tabindex attribute(s) checked, no anti-patterns
PASS
10 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 14 iframe(s) have descriptive titles
PASS
All 14 iframe(s) have descriptive titles
Info::
All 14 iframe(s) have title attributes
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A
Favicon & Branding
10 icon(s) detected
PASS
10 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 Present
✓ Multiple Sizes Present
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
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 маркетинго…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 seo-оптимиза…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 другое21.00:13.0:1
#000000
#FFFFFF
Pass
h3 SEO‑оптимиз…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 bitrix21.00:13.0:1
#000000
#FFFFFF
Pass
h3 tilda21.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