Skip to content
https://albastor.ru

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
F
Form Accessibility
Action
37 of 39 controls have issues
FIX
37 of 39 controls have issues
Critical::
35 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">; <input type="checkbox" name="favItem6592369" id="favItem6592369">; <input type="number" name="count">; <input type="checkbox" name="favItem4890034" id="favItem4890034">; <input type="number" name="count">; <input type="checkbox" name="favItem4890391" id="favItem4890391">; <input type="number" name="count">; <input type="checkbox" name="favItem7365360" id="favItem7365360">; <input type="number" name="count"> (+25 more)
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="find">; <input type="text" name="find">
Info::
2 control(s) properly labeled
39 controls
2 labeled
2 placeholder only
35 unlabeled
ControlTypeLabelMethod
#soglas1066385checkboxОтправляя форму, я соглашаюсь c политикой конфиденциальностиfor/id
#second_soglas_1066385checkboxОтправляя форму, я даю согласие на обработку персональных данныхfor/id
findtext(Искать товары)placeholder only
findtext(Поиск по каталогу)placeholder only
#favItem6592369checkbox(none)none
countnumber(none)none
#favItem4890034checkbox(none)none
countnumber(none)none
#favItem4890391checkbox(none)none
countnumber(none)none
#favItem7365360checkbox(none)none
countnumber(none)none
#favItem4889536checkbox(none)none
countnumber(none)none
#favItem4925605checkbox(none)none
countnumber(none)none
#favItem6592366checkbox(none)none
countnumber(none)none
#favItem6592369checkbox(none)none
countnumber(none)none
#favItem4890034checkbox(none)none
countnumber(none)none
#favItem4890391checkbox(none)none
countnumber(none)none
#favItem7365360checkbox(none)none
countnumber(none)none
#favItem4889536checkbox(none)none
countnumber(none)none
#favItem4925605checkbox(none)none
countnumber(none)none
#favItem6592366checkbox(none)none
countnumber(none)none
#favItem6592369checkbox(none)none
countnumber(none)none
customf[name][value]text(none)none
customf[phone][value]text(none)none
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">; <input type="checkbox" name="favItem6592369" id="favItem6592369">; <input type="number" name="count">; <input type="checkbox" name="favItem4890034" id="favItem4890034">; <input type="number" name="count">; <input type="checkbox" name="favItem4890391" id="favItem4890391">; <input type="number" name="count">; <input type="checkbox" name="favItem7365360" id="favItem7365360">; <input type="number" name="count"> (+25 more)

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="find">; <input type="text" name="find">

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

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #005494
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 ModePartial Dark Mode
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
7 landmarks
REVIEW
7 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

B
Mobile-Readable Font Sizes
95% of visible text renders at >= 12 CSS px (8 below threshold)
REVIEW
95% of visible text renders at >= 12 CSS px (8 below threshold)
Info::
8 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: <div> 11.0px ("Альбастор · Набережные Челны"); <span> 11.0px ("● Принимаем заявки"); <div> 11.0px ("Что делаем"); <div> 11.0px ("Порядок работ"); <span> 11.0px ("Распродажа").
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 Страница не найдена (ошибка 404) / Оригинальные запчасти для грузовой техники | Газовые системы (метан, СПГ, КПГ) – Альбастор ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA 1 pass AA only
h1 Метан для грузовой
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
32px · bottom of viewport
h1 техники
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Всё для метановой сисÑ…
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
24px · bottom of viewport
h2 грузовой техники
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Прозрачный процесс — …
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Переоборудовать технÐ…
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Переоборудование на м…
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Установка метанового …
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Выездная заправка мет…
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Переосвидетельствова…
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Комплектующие для КПГ
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Экспертиза и документ…
2.38:1
#000000
on
#004C86
needs 3.0:1 (large text)
19px · bottom of viewport
title Обслуживание и запчас…
2.70:1
#000000
on
#005494
needs 4.5:1 (normal text)
16px · top of page (header area)
span меню
2.70:1
#000000
on
#005494
needs 4.5:1 (normal text)
16px · top of page (header area)
div Республика Татарстан,…
2.16:1
#000000
on
#00467B
needs 4.5:1 (normal text)
16px · above the fold
a Напишите нам
2.17:1
#000000
on
#00467C
needs 4.5:1 (normal text)
16px · above the fold
a Обратный звонок
2.20:1
#000000
on
#00477D
needs 4.5:1 (normal text)
16px · above the fold
p Avtoerachelny@bk.ru
2.20:1
#000000
on
#00477E
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Метан для г…2.38:13.0:1
#000000
#004C86
Fail
h1 техники2.38:13.0:1
#000000
#004C86
Fail
h2 Всё для мет…2.38:13.0:1
#000000
#004C86
Fail
h2 грузовой тÐ…2.38:13.0:1
#000000
#004C86
Fail
h2 Прозрачный…2.38:13.0:1
#000000
#004C86
Fail
h2 Переоборуд…2.38:13.0:1
#000000
#004C86
Fail
h3 Переоборуд…2.38:13.0:1
#000000
#004C86
Fail
h3 Установка Ð…2.38:13.0:1
#000000
#004C86
Fail
h3 Выездная зÐ…2.38:13.0:1
#000000
#004C86
Fail
h3 Переосвиде…2.38:13.0:1
#000000
#004C86
Fail
h3 Комплектую…2.38:13.0:1
#000000
#004C86
Fail
h3 Экспертиза…2.38:13.0:1
#000000
#004C86
Fail
title Обслуживан…2.70:14.5:1
#000000
#005494
Fail
span меню2.70:14.5:1
#000000
#005494
Fail
div ✕21.00:14.5:1
#000000
#FFFFFF
Pass
div ✕6.19:14.5:1
#000000
#6790AF
Pass
div Республика…2.16:14.5:1
#000000
#00467B
Fail
a Напишите нÐ…2.17:14.5:1
#000000
#00467C
Fail
a Обратный зÐ…2.20:14.5:1
#000000
#00477D
Fail
p Avtoerachelny@bk.ru2.20:14.5:1
#000000
#00477E
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.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 5 failing, 15 passed
REVIEW
75

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.abx-wrap > div.abx-process > div.abx-process-info > span
Артикул: div.blk_info > div.blk_first > div.blk_art > span.art_title
202V09100-7848 div.blk_info > div.blk_first > div.blk_art > span.art_value
В корзину div.block_incard > div.cart-btn > a.incart-js > span
Артикул: div.blk_info > div.blk_first > div.blk_art > span.art_title
202V25803-792 div.blk_info > div.blk_first > div.blk_art > span.art_value
В корзину div.block_incard > div.cart-btn > a.incart-js > span
Мы в контакте div.blk_body_wrap > div.blockText > p > a

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form.ajax2 > div.userline > div.input-field-standart > input.inp form.ajax2 > div.userline > div.input-field-standart > input.inp
form.ajax2 > div.userline > div.input-field-standart > input.inp form.ajax2 > div.userline > div.input-field-standart > input.inp

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
body.shema1 > a#adm body.shema1 > a#adm

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Республика Татарстан, г. Набережные Челны, Ресурсный проезд, 4А Посмотреть на к… section#block84 > article.cb > div.blk_body_wrap > ul.contacts-items

These are opportunities to improve the experience of reading tabular or list data using 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 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-hidden="true"]` is not present on the document `<body>`
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●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
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○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
○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
10 headings
PASS
10 headings
Info::
Single H1 present
  • H1 Метан для грузовойтехники под ключ
  • H2 Всё для метановой системыгрузовой техники
  • H3 Переоборудование на метан
  • H3 Установка метанового оборудования
  • H3 Выездная заправка метаном
  • H3 Переосвидетельствование баллонов
  • H3 Комплектующие для КПГ
  • H3 Экспертиза и документы
  • H2 Прозрачный процесс — понятный результат
  • H2 Переоборудовать технику, установить метан или заправить автопарк?
A+
Heading Text Quality
All 10 heading(s) have substantive, well-formed text
PASS
All 10 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
13 image(s) with good alt text
16 images 13 good alt text
IssueCount
too long3 image(s)
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "customf[phone][value]" should use type="tel" (currently type="text")
Field name "customf[phone][value]" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
A+
Form Input Quality
39 form control(s) checked, no input-semantic issues
PASS
39 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
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
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+
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback