Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

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

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.

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: MAX – быстрое и легкое приложение для общения

No 192x192 icon

A 192px icon is required for PWA installation.

PWA Install Criteria Not Installable

Name MAX – быстрое и легкое приложение для общения ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗

Name MAX – быстрое и легкое приложение для общения Icons 2 icon(s)

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

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

Link & Button Quality

2 issue(s) across 19 links and 1 buttons

REVIEW

2 issue(s) across 19 links and 1 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://max.ru/

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.menuButton (#84 on page)

18 link(s) with descriptive text

19 links

1 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://max.ru/	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

18 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://max.ru/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Icon-only buttons need an aria-label so screen readers can announce them.

button.menuButton (#84 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA

h1 возможностей

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

32px · above the fold

h1 для

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

32px · above the fold

h3 Общайтесь без ограни�…

1.13:1

#000000

#171021

needs 3.0:1 (large text)

19px · mid-page

h3 Звоните в высоком кач…

1.19:1

#000000

#1E1332

needs 3.0:1 (large text)

19px · mid-page

h3 Читайте любимых автор…

1.27:1

#000000

#251543

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Будьте в безопасност�…

1.10:1

#000000

#110E18

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Пользуйтесь уникальн�…

1.10:1

#000000

#110E18

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Скачайте MAX

1.10:1

#000000

#110E18

needs 3.0:1 (large text)

19px · bottom of viewport

h3 на любое устройство

1.10:1

#000000

#110E18

needs 3.0:1 (large text)

19px · bottom of viewport

title MAX – быстрое и легкое �…

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Для бизнеса

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Скачать приложение

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Цифровой ID

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Открыть веб-версию

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

span Максимум

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

span общения

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

span общения

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

div Быстрое и лёгкое прил…

1.07:1

#000000

#0C0C0D

needs 4.5:1 (normal text)

16px · above the fold

a App Store

1.08:1

#000000

#0D0C0D

needs 4.5:1 (normal text)

16px · above the fold

a Google Play

1.08:1

#000000

#0E0D0F

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 возможност…	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h1 для	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h3 Общайтесь �…	1.13:1	3.0:1	#000000	#171021	Fail
h3 Звоните в �…	1.19:1	3.0:1	#000000	#1E1332	Fail
h3 Читайте лю�…	1.27:1	3.0:1	#000000	#251543	Fail
h3 Будьте в б�…	1.10:1	3.0:1	#000000	#110E18	Fail
h3 Пользуйтес…	1.10:1	3.0:1	#000000	#110E18	Fail
h3 Скачайте MAX	1.10:1	3.0:1	#000000	#110E18	Fail
h3 на любое у�…	1.10:1	3.0:1	#000000	#110E18	Fail
title MAX – быстро…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
a Для бизнес�…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
a Скачать пр�…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
a Цифровой ID	1.08:1	4.5:1	#000000	#0D0D0D	Fail
a Открыть ве�…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
span Максимум	1.08:1	4.5:1	#000000	#0D0D0D	Fail
span общения	1.08:1	4.5:1	#000000	#0D0D0D	Fail
span общения	1.08:1	4.5:1	#000000	#0D0D0D	Fail
div Быстрое и �…	1.07:1	4.5:1	#000000	#0C0C0D	Fail
a App Store	1.08:1	4.5:1	#000000	#0D0C0D	Fail
a Google Play	1.08:1	4.5:1	#000000	#0E0D0F	Fail

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.

Lighthouse Accessibility Audits

Score 85/100 — 3 failing, 15 passed

REVIEW

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
header.header > div.headerTop > nav.actions > button.menuButton `header.header > div.headerTop > nav.actions > button.menuButton`

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.header > div.headerTop > div.logo > a.logoLink `header.header > div.headerTop > div.logo > a.logoLink`

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.

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.content > div > div.contentFx > h3.title`

These are opportunities to improve keyboard navigation in your application.

○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

●Image elements have `[alt]` attributes

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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[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-hidden="true"]` elements do not contain focusable descendents

○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

○`<frame>` or `<iframe>` elements have a title

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

○Form elements have associated labels

○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

○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

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

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

Heading Hierarchy

7 headings, 1 skip(s)

PASS

7 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Максимум возможностей для общения общения
H3 Общайтесь без ограничений skipped
H3 Звоните в высоком качестве
H3 Читайте любимых авторов
H3 Будьте в безопасности
H3 Пользуйтесь уникальными сервисами
H3 Скачайте MAX на любое устройство

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

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 decorative image(s) correctly marked

7 images 7 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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