Accessibility

· 12 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 1 REVIEW 8 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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-s817uj

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://nic.ru/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://nic.ru/manifest.json

Manifest contains invalid JSON.

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 ✗

Lighthouse Accessibility Audits

Action

Score 58/100 — 9 failing, 14 passed

FIX

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
0 `div > div._1i6PI > header._0_30_27_header__base___3Fr94 > div`

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.

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
aside._0_30_27_sidebar__sidebar___1_8rg > div > div._0_30_27_sidebar__login___fwlnx > button._0_30_27_sidebar__close-button___E_7oU `aside._0_30_27_sidebar__sidebar___1_8rg > div > div._0_30_27_sidebar__login___fwlnx > button._0_30_27_sidebar__close-button___E_7oU`
div._2qdsy > div._1Ytsl > div._2EfQA > button._3Yf8U `div._2qdsy > div._1Ytsl > div._2EfQA > button._3Yf8U`
div._2qdsy > div._1Ytsl > div._2EfQA > button._3Yf8U `div._2qdsy > div._1Ytsl > div._2EfQA > button._3Yf8U`
div._3IfJk > div._32FFz > div._2EfQA > button._3Yf8U `div._3IfJk > div._32FFz > div._2EfQA > button._3Yf8U`
div._3IfJk > div._32FFz > div._2EfQA > button._3Yf8U `div._3IfJk > div._32FFz > div._2EfQA > button._3Yf8U`
div#inform-notification > div._0_2_10_informNotification__container___BSfub > div._0_2_10_informNotification__notification___24XG9 > button._0_2_10_informNotification__close___2_hRI `div#inform-notification > div._0_2_10_informNotification__container___BSfub > div._0_2_10_informNotification__notification___24XG9 > button._0_2_10_informNotification__close___2_hRI`

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._1RoO9 > a._3UiZZ > div.EGcGd > img `div._1RoO9 > a._3UiZZ > div.EGcGd > img`
div._1RoO9 > a._3UiZZ > div.EGcGd > img `div._1RoO9 > a._3UiZZ > div.EGcGd > img`
div._1RoO9 > a._3UiZZ > div.EGcGd > img `div._1RoO9 > a._3UiZZ > div.EGcGd > img`
div._1RoO9 > a._3UiZZ > div.EGcGd > img `div._1RoO9 > a._3UiZZ > div.EGcGd > img`

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 > iframe `body > 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
div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx `div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx`
div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx `div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx`
div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx `div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx`
div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx `div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx`
div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx `div._0_18_0_footer__display-mobile___3GFj- > ul._0_18_0_partnersSection__partners___nFyF2 > li > a._1sexx`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Сообщить о нарушениях Обработка персональных данных Правила применения рекоменд… `div._0_18_0_businessPanel__panel___JESEg > div._0_18_0_businessPanel__container___1h8bW > nav > ul._0_18_0_businessPanel__list___2h8br`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Сообщить о нарушениях `nav > ul._0_18_0_businessPanel__list___2h8br > a._1sexx > li`
Обработка персональных данных `nav > ul._0_18_0_businessPanel__list___2h8br > a._1sexx > li`
Правила применения рекомендательных технологий `nav > ul._0_18_0_businessPanel__list___2h8br > a._1sexx > li`
Политика конфиденциальности Руцентр `nav > ul._0_18_0_businessPanel__list___2h8br > a._1sexx > li`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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`

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Выбрать тариф `div.gj_Qp > div._2vrpl > div > a.rX4yD`
Выбрать тариф `div.gj_Qp > div._2vrpl > div > a.rX4yD`
Выбрать тариф `div.gj_Qp > div._2vrpl > div > a.rX4yD`
Выбрать тариф `div.gj_Qp > div._2vrpl > div > a.rX4yD`
Выбрать сервер `div.gj_Qp > div._2vrpl > div > a.rX4yD`
Создать сайт `div.gj_Qp > div._2vrpl > div > a.rX4yD`

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

●Form elements have associated labels

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

○Links are distinguishable without relying on color.

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

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Alt Text Quality

1 of 1 images have issues

PASS

1 of 1 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 images 1 missing

Issue	Count
missing	1 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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

No links or buttons

PASS

No links or buttons

No links or buttons on this page

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

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