Skip to content
https://coachmentor.ru

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
5
REVIEW
6
PASS
13
INFO
0
Checks
24
13 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
1 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 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) 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 NAV MAIN (missing!) CONTENTINFO footer

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

C
Form Accessibility
Action
7 of 7 controls have issues
REVIEW
7 of 7 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="name">; <input type="tel" name="tel">; <input type="text" name="name">; <input type="email" name="email">; <textarea name="message">; <input name="inputHuman">
7 controls
0 labeled
6 placeholder only
1 unlabeled
ControlTypeLabelMethod
nametext(Ваше ФИО)placeholder only
teltel(Контактный телефон)placeholder only
nametext(Ваше имя)placeholder only
emailemail(Электронная почта)placeholder only
messagetextarea(Ваш комментарий)placeholder only
inputHumaninput(Задать вопрос)placeholder only
inputsubmit(none)none

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

<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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="name">; <input type="tel" name="tel">; <input type="text" name="name">; <input type="email" name="email">; <textarea name="message">; <input name="inputHuman">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
Mobile Keyboard & Autofill
Action
4/6 eligible field(s) missing autocomplete or inputmode
REVIEW
4/6 eligible field(s) missing autocomplete or inputmode
Warning::
4 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name, tel, email.
Got: <input type="text" name="name">, <input type="tel" name="tel">, <input type="text" name="name">, <input type="email" name="email">
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 Страница не найдена - НФПМК ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 20 passed
REVIEW
85

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.fs__right-side > a.front-fs-btn > div.ds-flex > div.front-fs-btn__text
Процесс профессионального сопровождения, направленного на развитие управленческ… div.wrapper > div.front-about-items > div.fa-item > div.fa-item__text
Деятельность направлена на углубление компетенций коучей и менторов, а также на… div.wrapper > div.front-about-items > div.fa-item > div.fa-item__text
100+ коучей div.info-block > div.info > div.ds-flex > div.like-h4
День рождения НФПМК-2026 div.event-card > div.event-card__main > div.event-card__text > b
НФПМК Gala: Коучинг и менторинг как бизнес и для бизнеса div.event-card > div.event-card__main > div.event-card__text > i
Профессиональная сертификация подтверждает ваше ответственное отношение к профе… div.front-offers > div.front-offer > div.front-offer__info > div.text-content
Клиенты видят в профессиональной сертификации доказательство вашего серьезного … div.front-offers > div.front-offer > div.front-offer__info > div.text-content
Пройдите сертификацию в НФПМК и подтвердите свой уровень квалификации бизнес и … div.front-offers > div.front-offer > div.front-offer__info > div.text-content
Нажимая на кнопку, вы подтверждаете ознакомление с политикой конфиденциальности… div.wrapper > form.contacts-form > div.contacts-form__inputs > div.form-notice
08 сентября 2026 a.sticky-news > div.sticky-news__main > div.sticky-news__meta > div.date
28 июля 2026 a.sticky-news > div.sticky-news__main > div.sticky-news__meta > div.date
12 мая 2026 a.sticky-news > div.sticky-news__main > div.sticky-news__meta > div.date
16 апреля 2026 a.sticky-news > div.sticky-news__main > div.sticky-news__meta > div.date

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
header#page-header > div.wrapper > div.header-wrap > a.logo-link header#page-header > div.wrapper > div.header-wrap > a.logo-link
div.wrapper > div.front-events > div.event-card > a.image-wrap div.wrapper > div.front-events > div.event-card > a.image-wrap
div.default-grid-3 > div.catalog-card > div.catalog-card__main > a.image-wrap div.default-grid-3 > div.catalog-card > div.catalog-card__main > a.image-wrap
div.default-grid-3 > div.catalog-card > div.catalog-card__main > a.image-wrap div.default-grid-3 > div.catalog-card > div.catalog-card__main > a.image-wrap
div.default-grid-3 > div.catalog-card > div.catalog-card__main > a.image-wrap div.default-grid-3 > div.catalog-card > div.catalog-card__main > a.image-wrap
div.footer-info > div.footer-info__top > div.ds-flex > a.like-h6 div.footer-info > div.footer-info__top > div.ds-flex > a.like-h6
div.footer-grid > div.footer-col > div.social-circles > a.social-circle div.footer-grid > div.footer-col > div.social-circles > a.social-circle
div.footer-grid > div.footer-col > div.social-circles > a.social-circle div.footer-grid > div.footer-col > div.social-circles > a.social-circle

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.

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●`[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
●Input buttons have discernible text.
●Form elements have associated labels
●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
●Links are distinguishable without relying on color.
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○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
○`<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 Hierarchy
6 headings
PASS
6 headings
Info::
Single H1 present
  • H1 Вместе задаём тренды в коучинге и менторинге
  • H2 Мероприятия и вебинары
  • H2 Мы предлагаем
  • H2 Каталог специалистов
  • H2 Публикации в СМИ
  • H2 Пишем просто о сложном
A+
Heading Text Quality
All 6 heading(s) have substantive, well-formed text
PASS
All 6 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 25 images OK
PASS
All 25 images OK
Info::
23 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
25 images 2 good alt text 23 decorative
All images have appropriate alt text.
A+
Form Input Types
7 form control(s) checked, no type mismatches
PASS
7 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
7 form control(s) checked, no input-semantic issues
PASS
7 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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+
Mobile-Readable Font Sizes
All 147 visible text node(s) render at >= 12 CSS pixels
PASS
All 147 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::
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 Вместе зад…18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Мероприяти…18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Мы предлаг…18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Каталог сп…18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Публикации…18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Пишем прос…18.76:13.0:1
#000000
#F2F2F2
Pass
title Вместе зад…21.00:14.5:1
#000000
#FFFFFF
Pass
span Войти21.00:14.5:1
#000000
#FFFFFF
Pass
a НФПМК Gala: К…16.59:14.5:1
#000000
#CEF18D
Pass
div 03 октября16.59:14.5:1
#000000
#CEF18D
Pass
span Все програ…19.26:14.5:1
#000000
#F5F5F5
Pass
a О Федераци…19.26:14.5:1
#000000
#F5F5F5
Pass
a Миссия Фед…19.26:14.5:1
#000000
#F5F5F5
Pass
a Экспертный…19.26:14.5:1
#000000
#F5F5F5
Pass
a Совет дире…19.26:14.5:1
#000000
#F5F5F5
Pass
a Уставные д…19.26:14.5:1
#000000
#F5F5F5
Pass
a Стандарты19.26:14.5:1
#000000
#F5F5F5
Pass
a Дивизионы19.26:14.5:1
#000000
#F5F5F5
Pass
a Блог19.26:14.5:1
#000000
#F5F5F5
Pass
a Контакты19.26:14.5:1
#000000
#F5F5F5
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