Skip to content
https://apcsro.ru

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 REVIEW 7 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark 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 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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ 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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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 Вступление в СРО прое…
1.37:1
#000000
on
#0E234D
needs 3.0:1 (large text)
32px · above the fold
h2 Узнаёте себя?
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Почему выбор СРО — эт…
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Почему вступают в АПЦ
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Вступление в АПЦ: 3 шаг…
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ваша компания уже
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 в реестре СРО
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Как это было у наших ч…
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Прозрачные условия — …
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Отвечаем честно на гл…
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Почему АПЦ — правильн…
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Не упускайте новые во…
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Вступите в СРО
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 за 4 часа — без рисков
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Членство в СРО — это и…
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Типичное СРО
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 АПЦ
1.24:1
#000000
on
#0D1B3E
needs 3.0:1 (large text)
19px · bottom of viewport
title Вступить в СРО проект…
1.37:1
#000000
on
#152446
needs 4.5:1 (normal text)
16px · top of page (header area)
span Академический Проект…
1.43:1
#000000
on
#17274B
needs 4.5:1 (normal text)
16px · top of page (header area)
span СРО-П-119-18012010 · с 2010 год…
1.39:1
#000000
on
#162548
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Вступление…1.37:13.0:1
#000000
#0E234D
Fail
h2 Узнаёте се…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Почему выб…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Почему вст…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Вступление…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Ваша компа…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 в реестре С…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Как это был…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Прозрачные…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Отвечаем ч…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Почему АПЦ …1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Не упускай…1.24:13.0:1
#000000
#0D1B3E
Fail
h2 Вступите в …1.24:13.0:1
#000000
#0D1B3E
Fail
h2 за 4 часа — …1.24:13.0:1
#000000
#0D1B3E
Fail
h3 Членство в …1.24:13.0:1
#000000
#0D1B3E
Fail
h3 Типичное С…1.24:13.0:1
#000000
#0D1B3E
Fail
h3 АПЦ1.24:13.0:1
#000000
#0D1B3E
Fail
title Вступить в …1.37:14.5:1
#000000
#152446
Fail
span Академичес…1.43:14.5:1
#000000
#17274B
Fail
span СРО-П-119-180120…1.39:14.5:1
#000000
#162548
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.

A+
Heading Hierarchy
15 headings
PASS
15 headings
Info::
Single H1 present
  • H1 Вступление в СРО проектировщиков за 4 часа
  • H2 Узнаёте себя?
  • H2 Почему выбор СРО — это решение на годы
  • H2 Почему вступают в АПЦ
  • H2 Вступление в АПЦ: 3 шага
  • H2 Ваша компания ужев реестре СРО
  • H2 Как это было у наших членов
  • H2 Прозрачные условия — всё включено в одну сумму
  • H3 Членство в СРО — это инвестиция, а не расход
  • H2 Отвечаем честно на главные опасения
  • H2 Почему АПЦ — правильный выбор
  • H3 Типичное СРО
  • H3 АПЦ
  • H2 Не упускайте новые возможности для вашего бизнеса
  • H2 Вступите в СРОза 4 часа — без рисков
A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
5 image(s) with good alt text
5 images 5 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#nametextВаше имя *for/id
#phonetelТелефон *for/id
#companytextКомпанияfor/id
consentcheckboxnone
#modal-nametextВаше имя *for/id
#modal-phonetelТелефон *for/id
#modal-companytextНазвание организацииfor/id
consentcheckboxnone
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 20 passed
PASS
94

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.compare-grid > div.compare-col > div.compare-col__header > h3
Вступительный взнос 30 000–90 000 ₽ div.compare-grid > div.compare-col > ul.compare-list > li
Страховка до 50 000 ₽ div.compare-grid > div.compare-col > ul.compare-list > li
Членский взнос 7 000–12 000 ₽/мес. div.compare-grid > div.compare-col > ul.compare-list > li
Нужно приехать в офис с документами div.compare-grid > div.compare-col > ul.compare-list > li
Первый месяц — за ваш счёт div.compare-grid > div.compare-col > ul.compare-list > li
Скрытые платежи возможны div.compare-grid > div.compare-col > ul.compare-list > li
Дата в реестре — неизвестно div.compare-grid > div.compare-col > ul.compare-list > li
Узнайте, как быстро и выгодно вступить в СРО и начать выигрывать крупные контра… div.container > div.cta-inner > div > p.cta-sub
Консультация ни к чему не обязывает div.cta-inner > div > ul > li
Ответим за 15 минут div.cta-inner > div > ul > li
Вступительный взнос 0 ₽ — начнёте без больших затрат div.cta-inner > div > ul > li
Ассоциация «Академический Проектный Центр» div.container > div.footer__inner > div.footer__reqs > span
ОГРН 1097799013982 div.container > div.footer__inner > div.footer__reqs > span
ИНН 7701054960 div.container > div.footer__inner > div.footer__reqs > span
КПП 773601001 div.container > div.footer__inner > div.footer__reqs > span
119331, г. Москва, пр-кт Вернадского, д. 29, помещ. 1/4 footer.footer > div.container > div.footer__inner > div
Режим работы: Пн–Чт 9:00–18:00, Пт 9:00–17:00 footer.footer > div.container > div.footer__inner > div
АПЦ · СРО-П-119-18012010 · © 2026 div.container > div.footer__inner > div.footer__bottom > span.footer__copy
Политика конфиденциальности div.container > div.footer__inner > div.footer__bottom > a

These are opportunities to improve the legibility of your content.

Best practices

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>`
●`[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.
●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.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[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
○`<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
○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.
○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.

Send Feedback