Skip to content
https://drom.ru

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
3
REVIEW
8
PASS
2
INFO
0
Checks
13
2 PASS 8 REVIEW 3 FIX
D
Landmark Structure
Action
No landmarks
FIX
No 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
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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.
B
Heading Hierarchy
13 headings
REVIEW
13 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Продажа авто в России
  • H2 Поиск объявлений
  • H3 Новые автомобили от дилеров
  • H3 Отзывы владельцев авто
  • H3 Автоновости
  • H3 Тест-драйвы и статьи
  • H3 Автопутешествия
  • H3 Автоспорт
  • H3 Запчасти
  • H3 Шины
  • H3 Диски
  • H3 Сегодня на автофорумах
  • H3 Блоги «русских» машин на Дроме

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title ����������� ���� �������� �� ����������! ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✗ Multiple Sizes Missing
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Дром Авто
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Дром Авто ✓192×192 icon ✗512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name Дром Авто Display Mode standalone Icons 1 icon(s)
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 #000000 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

8 pass 12 fail WCAG AA 3 pass AA only
title Дром - цены на машины
1.04:1
#000000
on
#060606
needs 4.5:1 (normal text)
16px · top of page (header area)
span Сделка с Дромом на 3 000…
1.04:1
#000000
on
#060606
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Москва
1.04:1
#000000
on
#060606
needs 4.5:1 (normal text)
16px · top of page (header area)
a Автомобили
1.27:1
#000000
on
#1F1F1F
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Спецтехника
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
span Грузовики и спецтехни…
3.16:1
#000000
on
#6A5C16
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Мото
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Мотоциклы
1.04:1
#000000
on
#060606
needs 4.5:1 (normal text)
16px · above the fold
a Отзывы
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Каталог
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Автомобили из Китая
3.97:1
#000000
on
#8D5F67
needs 4.5:1 (normal text)
16px · mid-page
a Электромобили
3.49:1
#000000
on
#81585F
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

5 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Продажа ав…21.00:13.0:1
#000000
#FFFFFF
Pass
title Дром - цены …1.04:14.5:1
#000000
#060606
Fail
span Сделка с Др…1.04:14.5:1
#000000
#060606
Fail
a Москва1.04:14.5:1
#000000
#060606
Fail
a Автомобили1.27:14.5:1
#000000
#1F1F1F
Fail
span Спецтехник…1.66:14.5:1
#000000
#333333
Fail
span Грузовики …3.16:14.5:1
#000000
#6A5C16
Fail
span Мото1.13:14.5:1
#000000
#131313
Fail
span Мотоциклы1.04:14.5:1
#000000
#060606
Fail
a Запчасти4.98:14.5:1
#000000
#AD6776
Pass
a Отзывы1.00:14.5:1
#000000
#000000
Fail
a Каталог1.00:14.5:1
#000000
#000000
Fail
a Шины21.00:14.5:1
#000000
#FFFFFF
Pass
div Еще21.00:14.5:1
#000000
#FFFFFF
Pass
a Продажа ши…21.00:14.5:1
#000000
#FFFFFF
Pass
a Аукционы Я…21.00:14.5:1
#000000
#FFFFFF
Pass
a Автомобили…3.97:14.5:1
#000000
#8D5F67
Fail
a Автомобили…5.79:14.5:1
#000000
#8D857F
Pass
a Автомобили…6.04:14.5:1
#000000
#9E8385
Pass
a Электромоб…3.49:14.5:1
#000000
#81585F
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 82/100 — 5 failing, 18 passed
REVIEW
82

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.u41pni1 > a.u41pni0 > div.u41pni6 > div.u41pni7
Клин div.u41pni1 > a.u41pni0 > div.u41pni6 > div.u41pni7
Москва div.u41pni1 > a.u41pni0 > div.u41pni6 > div.u41pni7
Подольск div.u41pni1 > a.u41pni0 > div.u41pni6 > div.u41pni7
TENET T8, 2026 div.ahgfoy0 > div._807e4r0 > div.zau3b20 > a.vd61sn0
92 div._1juhary1 > div._1juhary0 > span.m39dp62 > span.m39dp66
14 апреля div.ahgfoy0 > div._807e4r0 > div._1juhary1 > div.x8i48c0
Kia Soul, 2009 div.ahgfoy0 > div._807e4r0 > div.zau3b20 > a.vd61sn0
27 div._1juhary1 > div._1juhary0 > span.m39dp62 > span.m39dp66
13 апреля div.ahgfoy0 > div._807e4r0 > div._1juhary1 > div.x8i48c0
13 апреля div.ahgfoy0 > div._807e4r0 > div._1juhary1 > div.x8i48c0
13 апреля div.ahgfoy0 > div._807e4r0 > div._1juhary1 > div.x8i48c0
Tiggo 9, 2025 div.ahgfoy0 > div._807e4r0 > div.zau3b20 > a.vd61sn0
19 div._1juhary1 > div._1juhary0 > span.m39dp62 > span.m39dp66
13 апреля div.ahgfoy0 > div._807e4r0 > div._1juhary1 > div.x8i48c0
Monjaro, 2023 div.ahgfoy0 > div._807e4r0 > div.zau3b20 > a.vd61sn0
29 div._1juhary1 > div._1juhary0 > span.m39dp62 > span.m39dp66
13 апреля div.ahgfoy0 > div._807e4r0 > div._1juhary1 > div.x8i48c0
172 div.css-rqz5qm > a._1ms9k6p0 > div._1ms9k6p3 > span._1dc88ze0
35 div.css-rqz5qm > a._1ms9k6p0 > div._1ms9k6p3 > span._1dc88ze0
265 div.css-rqz5qm > a._1ms9k6p0 > div._1ms9k6p3 > span._1dc88ze0
16 div.css-rqz5qm > a._1ms9k6p0 > div._1ms9k6p3 > span._1dc88ze0
19 div.css-rqz5qm > a._1ms9k6p0 > div._1ms9k6p3 > span._1dc88ze0
52 665 км div.css-16brga7 > a._1f0ewh10 > div.css-14hyps3 > div._1f0ewh14
38 500 км div.css-16brga7 > a._1f0ewh10 > div.css-14hyps3 > div._1f0ewh14
152 950 км div.css-16brga7 > a._1f0ewh10 > div.css-14hyps3 > div._1f0ewh14
Москва div.css-1vigsty > div.css-38l12z > a.g6gv8w4 > span.css-1qkltea
Перейти на полную версию div > div.css-1vigsty > div.css-uwmipf > button.g6gv8w4
Модели авто div > div.css-1vigsty > div.css-15dz9bv > button.css-19pqeow
О проекте div.css-1vigsty > div.css-fb6wtr > div.css-1h56t3v > a.g6gv8w4
Безопасность div.css-1vigsty > div.css-fb6wtr > div.css-1h56t3v > a.g6gv8w4
Помощь div.css-1vigsty > div.css-fb6wtr > div.css-1h56t3v > a.g6gv8w4
Размещение на Дроме div.css-1vigsty > div.css-fb6wtr > div.css-1h56t3v > a.g6gv8w4
Правила div.css-1vigsty > div.css-fb6wtr > div.css-1h56t3v > a.g6gv8w4
Для СМИ div.css-1vigsty > div.css-fb6wtr > div.css-1h56t3v > a.g6gv8w4
© 1999–2026 Дром body.page > div > div.css-1vigsty > div.css-7x0dcv

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.ftldj64 > div#candy_center_top > img div > div.ftldj64 > div#candy_center_top > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.ftldj64 > div#candy_center_top > iframe div > div.ftldj64 > div#candy_center_top > iframe

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

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.drom-touch html.drom-touch

These items highlight common accessibility best practices.

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
Продать div.drom-mobile > div._1lcc5ku6 > div._1lcc5kub > a._1lcc5ku3
Автомобили div > div.ftldj64 > div.css-1xn3edc > a._1jimdps5
Спецтехника div > div.ftldj64 > div.css-1xn3edc > a._1jimdps5
Мотоциклы div > div.ftldj64 > div.css-1xn3edc > a._1jimdps5
Запчасти div > div.ftldj64 > div.css-1xn3edc > a._1jimdps5
○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
●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
●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 have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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-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
○`[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
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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
○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
○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
Alt Text Quality
All 118 images OK
PASS
All 118 images OK
Info::
4 image(s) with alt text over 125 characters
Info::
70 decorative image(s) correctly marked
Info::
44 image(s) with good alt text
118 images 44 good alt text 70 decorative
IssueCount
too long4 image(s)
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input>
Info::
3 control(s) properly labeled
4 controls
3 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
Variant[]checkboxnone
Variant[]checkboxnone
Variant[]checkboxnone
inputinput(Госномер / VIN / № кузова)placeholder only

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

<input>

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

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

Send Feedback