Skip to content
https://glad.art-stroy-company.ru/v2

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
2
PASS
17
INFO
0
Checks
24
17 PASS 2 REVIEW 5 FIX
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 ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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
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.
C
Mobile-Readable Font Sizes
Action
73% of visible text renders at >= 12 CSS px (104 below threshold)
REVIEW
73% of visible text renders at >= 12 CSS px (104 below threshold)
Warning::
104 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <figcaption> 11.0px ("Вид с террасы · август 2026"); <figcaption> 11.0px ("Ряды у посёлка"); <figcaption> 11.0px ("Июль 2026"); <figcaption> 11.0px ("Водоём рядом с посёлком · март 2026"); <span> 9.0px ("Визуализация").
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 #f3eee7 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Landmark Structure
18 landmarks
PASS
18 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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

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

A+
Heading Hierarchy
23 headings
PASS
23 headings
Info::
Single H1 present
  • H2 Выравниваем участок
  • H2 Ленточный фундамент
  • H2 Блок и кирпич
  • H2 Крыша
  • H2 Окна и двери
  • H2 Отделка white box
  • H2 Забор, ворота, дорожки
  • H2 Ключи
  • H1 Виноградная Долина, коттеджный посёлок ВИНОГРАДНАЯ ДОЛИНАДОЛИНА
  • H2 Из чего строим Усадьбу
  • H2 «Маленькая Швейцария» на юге России
  • H2 Шесть проектов, от 70 до 140 м²
  • H2 Так выглядит готовая Усадьба в посёлке
  • H3 Видеообзоры домов в посёлке
  • H2 Выберите участок на плане
  • H3 Свободные участки
  • H2 Рассрочка 0 % на 3 года
  • H2 Час до моря в Анапе, 20 минут до Крымска
  • H2 Новосёлы рассказывают сами
  • H2 Отвечаем прямо
  • H2 Приезжайте посмотреть посёлок, дома и озеро
  • H3 Записаться на экскурсию
  • H2 Участок
A+
Heading Text Quality
All 23 heading(s) have substantive, well-formed text
PASS
All 23 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 33 images OK
PASS
All 33 images OK
Info::
16 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
33 images 17 good alt text 16 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 13 controls labeled
PASS
All 13 controls labeled
Info::
13 control(s) properly labeled
13 controls
13 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
cmradionone
cmradionone
cmradionone
cmradionone
cmradionone
ctradionone
ctradionone
ctradionone
ctradionone
ctradionone
#f-nameinputКак вас зовутfor/id
#f-teltelТелефонfor/id
#f-okcheckboxnone
A+
Form Input Types
13 form control(s) checked, no type mismatches
PASS
13 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
13 form control(s) checked, no input-semantic issues
PASS
13 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
All 3 eligible field(s) carry autocomplete/inputmode
PASS
All 3 eligible field(s) carry autocomplete/inputmode
Info::
All 3 eligible field(s) carry autocomplete/inputmode
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, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input id="f-site">
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+
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+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
3 mobile-depth signal(s) detected
PASS
3 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.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
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
h2 Выравнивае…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Ленточный Ñ…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Блок и кирп…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Крыша18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Окна и двер…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Отделка white…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Забор, воро…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Ключи18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Из чего стр…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 «Маленькая…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Шесть проеÐ…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Так выглядÐ…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Выберите уÑ…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Рассрочка 0…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Час до моря…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Новосёлы рÐ…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Отвечаем пÑ…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Приезжайте…18.19:13.0:1
#000000
#F3EEE7
Pass
h2 Участок18.19:13.0:1
#000000
#F3EEE7
Pass
h3 Видеообзор…18.19:13.0:1
#000000
#F3EEE7
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.

A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 29 passed
PASS
100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ВИЗУАЛИЗАЦИЯ КОМПАКТ 70 м² · 2 спальни · 1 этаж от 6 682 000 ₽ section#houses > ul#models > li > button.model
ВИЗУАЛИЗАЦИЯ КОМФОРТ 90 м² · 3 спальни · 1 этаж АКЦИЯ от 6 040 000 ₽ section#houses > ul#models > li > button.model
ВИЗУАЛИЗАЦИЯ ЭРКЕР ИЗУМРУДНЫЙ 104 м² · 3 спальни · 1 этаж от 7 068 000 ₽ section#houses > ul#models > li > button.model
ВИЗУАЛИЗАЦИЯ МАНХЭТТЕН 106 м² · 3 спальни · 1 этаж Под заказ section#houses > ul#models > li > button.model
ВИЗУАЛИЗАЦИЯ УСАДЬБА 110 м² · 3 спальни · 1 этаж от 7 196 000 ₽ section#houses > ul#models > li > button.model
ВИЗУАЛИЗАЦИЯ ЭЛЕГАНТ 140 м² · 4 спальни · 2 этажа от 9 824 000 ₽ section#houses > ul#models > li > button.model
План отдела продаж от 26.09 section#plan > div.plan-meta > p.note > button.linkbtn
○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.
●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
●Background and foreground colors have a sufficient contrast ratio
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○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.
○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