Skip to content
https://cognitivelens.ru

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
4
REVIEW
7
PASS
13
INFO
0
Checks
24
13 PASS 7 REVIEW 4 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-pzoee2
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.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://cognitivelens.ru/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://cognitivelens.ru/manifest.json

Manifest contains invalid JSON.

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

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

B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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 Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 #0f0f11 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
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 Look at your text
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
32px · above the fold
h2 See Analysis in Action
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Everything for Deep Text Analysis
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What can be analyzed
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready-Made Specialists at Your Service
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get Started in 1 Minute
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
24px · bottom of viewport
h2 from 10 RUB per analysis
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to Start?
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Blended Role Analysis
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 10+ Experts
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Custom Roles
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Image Recognition
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Detailed Scoring
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bilingual Interface
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Business Letter
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Resume
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Article or Post
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Negotiation Prep
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Client Feedback
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sign Up
1.07:1
#000000
on
#0E0817
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Look at your text1.07:13.0:1
#000000
#0E0817
Fail
h2 See Analysis in Acti…1.07:13.0:1
#000000
#0E0817
Fail
h2 Everything for Deep …1.07:13.0:1
#000000
#0E0817
Fail
h2 What can be analyzed1.07:13.0:1
#000000
#0E0817
Fail
h2 Ready-Made Specialis…1.07:13.0:1
#000000
#0E0817
Fail
h2 Get Started in 1 Min…1.07:13.0:1
#000000
#0E0817
Fail
h2 from 10 RUB per anal…1.07:13.0:1
#000000
#0E0817
Fail
h2 Ready to Start?1.07:13.0:1
#000000
#0E0817
Fail
h3 Blended Role Analysi…1.07:13.0:1
#000000
#0E0817
Fail
h3 10+ Experts1.07:13.0:1
#000000
#0E0817
Fail
h3 Custom Roles1.07:13.0:1
#000000
#0E0817
Fail
h3 Image Recognition1.07:13.0:1
#000000
#0E0817
Fail
h3 Detailed Scoring1.07:13.0:1
#000000
#0E0817
Fail
h3 Bilingual Interface1.07:13.0:1
#000000
#0E0817
Fail
h3 Business Letter1.07:13.0:1
#000000
#0E0817
Fail
h3 Resume1.07:13.0:1
#000000
#0E0817
Fail
h3 Article or Post1.07:13.0:1
#000000
#0E0817
Fail
h3 Negotiation Prep1.07:13.0:1
#000000
#0E0817
Fail
h3 Client Feedback1.07:13.0:1
#000000
#0E0817
Fail
h3 Sign Up1.07:13.0:1
#000000
#0E0817
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 4 failing, 20 passed
REVIEW
83

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.sticky > div.container > div.md:hidden > button.cursor-pointer header.sticky > div.container > div.md:hidden > button.cursor-pointer

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.relative > header.sticky > div.container > a.flex div.relative > header.sticky > div.container > a.flex

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
Letter → Persuasiveness check div.space-y-24 > section.relative > ul.mt-4 > li
Resume → Competency analysis div.space-y-24 > section.relative > ul.mt-4 > li
Article → Argumentation breakdown div.space-y-24 > section.relative > ul.mt-4 > li
Get Started div.space-y-24 > section.relative > div.mt-10 > a.cursor-pointer
Бизнес-тренер div.w-full > div.flex > div.inline-flex > button#radix-_r_3_-trigger-bc
Маркетолог div.w-full > div.flex > div.inline-flex > button#radix-_r_3_-trigger-mkt
Analyze div#radix-_r_3_-content-hr > div.rounded-xl > div.p-4 > button.cursor-pointer
Create Account div.space-y-6 > div.rounded-xl > div.p-6 > a.cursor-pointer
Create Account section.relative > div.rounded-xl > div.relative > a.cursor-pointer

These are opportunities to improve the legibility of your content.

Best practices

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
Terms of Service div.relative > footer.border-t > div.container > a.underline
Privacy Policy div.relative > footer.border-t > div.container > a.underline

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>`
●`[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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○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.
A+
Heading Hierarchy
22 headings
PASS
22 headings
Info::
Single H1 present
  • H1 Look at your textthrough the eyes of AI experts
  • H2 See Analysis in Action
  • H2 Everything for Deep Text Analysis
  • H3 Blended Role Analysis
  • H3 10+ Experts
  • H3 Custom Roles
  • H3 Image Recognition
  • H3 Detailed Scoring
  • H3 Bilingual Interface
  • H2 What can be analyzed
  • H3 Business Letter
  • H3 Resume
  • H3 Article or Post
  • H3 Negotiation Prep
  • H3 Client Feedback
  • H2 Ready-Made Specialists at Your Service
  • H2 Get Started in 1 Minute
  • H3 Sign Up
  • H3 Upload Text
  • H3 Get Analysis
  • H2 from 10 RUB per analysis
  • H2 Ready to Start?
A+
Heading Text Quality
All 22 heading(s) have substantive, well-formed text
PASS
All 22 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "ru"
PASS
Lang attribute set to "ru"
Info::
<html lang="ru"> is set and valid
Got: ru
A
Tabindex Anti-Patterns
0 positive, 3 -1-on-focusable
PASS
0 positive, 3 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="radix-_r_3_-trigger-hr">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="radix-_r_3_-trigger-bc">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="radix-_r_3_-trigger-mkt">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 107 visible text node(s) render at >= 12 CSS pixels
PASS
All 107 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback