Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 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-2w42n9

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://forbes.ru/manifest.json contains invalid JSON. Browsers cannot parse it.

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

Manifest contains invalid JSON.

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 ✗

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

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.

Page Structure — as a screen reader sees it

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

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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 decorative image(s) correctly marked

1 images 1 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.

A+

Link & Button Quality

3 links, 0 buttons — all OK

PASS

3 links, 0 buttons — all OK

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://yandex.com/support/smart-captcha/problems.html?form-unique_key=855976…

2 link(s) with descriptive text

3 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://yandex.com/support/smart-captcha…	feedback form	new tab	Add '(opens in new tab)' to text

2 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://yandex.com/support/smart-captcha/problems.html?form-unique_key=855976…

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Color Contrast (Screenshot)

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

8 pass

Show all checked elements (8)

Element	Ratio	Required	FG	BG	Result
title Are you not a robot?	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Please confirm that …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span We're sorry, but it …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Why might this happe…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span If you have any prob…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a feedback form	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 8559761640368114149	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 1776817829	21.00:1	4.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.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 24 passed

PASS

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.

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._-7TBD > div.gVGi4 > button._6IzgI`
Общество `div.igefR > header.nScqK > div._1RUTW > a.DmmQR`
Больше материалов `div > ul.NyKBv > li.hEHKS > button._6IzgI`
Карьера и свой бизнес `div.aesNj > header.nScqK > div._1RUTW > a.DmmQR`
Карьера и свой бизнес `div.aesNj > header.nScqK > div._1RUTW > a.DmmQR`
Больше материалов `div > ul.NyKBv > li.hEHKS > button._6IzgI`
Карьера и свой бизнес `div.aesNj > header.nScqK > div._1RUTW > a.DmmQR`
Больше материалов `div > ul.NyKBv > li.hEHKS > button._6IzgI`
Карьера и свой бизнес `div.aesNj > header.nScqK > div._1RUTW > a.DmmQR`
Больше материалов `div > ul.NyKBv > li.hEHKS > button._6IzgI`
Карьера и свой бизнес `div.aesNj > header.nScqK > div._1RUTW > a.DmmQR`
Карьера и свой бизнес `div.aesNj > header.nScqK > div._1RUTW > a.DmmQR`
Больше материалов `div > ul.NyKBv > li.hEHKS > button._6IzgI`
Карьера и свой бизнес `div.aesNj > header.nScqK > div._1RUTW > a.DmmQR`
Больше материалов `div > ul.NyKBv > li.hEHKS > button._6IzgI`
Карьера и свой бизнес `div.aesNj > header.nScqK > div._1RUTW > a.DmmQR`
Карьера и свой бизнес `div.aesNj > header.nScqK > div._1RUTW > a.DmmQR`
Больше материалов `div > ul.NyKBv > li.hEHKS > button._6IzgI`

These are opportunities to improve the legibility of your content.

Names and labels

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.lca683f6b > div.yd9c8e661 > div.h1559737f > a.g73a5bf50 `div.lca683f6b > div.yd9c8e661 > div.h1559737f > a.g73a5bf50`

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

●Image elements have `[alt]` attributes

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

○Heading elements appear in a sequentially-descending order

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

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

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