Skip to content
https://master-220v.ru

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
8
REVIEW
4
PASS
12
INFO
0
Checks
24
12 PASS 4 REVIEW 8 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

F
Document Language
Action
Missing <html lang> attribute (WCAG 3.1.1)
FIX
Missing <html lang> attribute (WCAG 3.1.1)
Critical::
Missing <html lang> attribute (WCAG 3.1.1)
Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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::
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.
D
Lighthouse Accessibility Audits
Action
Score 65/100 — 9 failing, 11 passed
FIX
65

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
Ремонт электрики td > font > strong > a.dot
Энергоучет td > font > strong > a.dot
Электрификация td > font > strong > a.dot
Аварийная td > font > strong > a.dot
Электромонтажные работы ul.ul-1 > font.strong > li > a.dot
Ремонт электрооборудования ul.ul-1 > font.strong > li > a.dot
Срочный ремонт электрики ul.ul-1 > font.strong > li > a.dot
Ремонт воздушных линий ul.ul-1 > font.strong > li > a.dot
Ремонт и замена электропроводки ul.ul-1 > font.strong > li > a.dot
Трансформаторные подстанции ul.ul-1 > font.strong > li > a.dot
Установка трубостоек ul.ul-1 > font.strong > li > a.dot
Проектирование и расчеты ul.ul-1 > font.strong > li > a.dot
Заземление ul.ul-1 > font.strong > li > a.dot
Молниезащита ul.ul-1 > font.strong > li > a.dot
Испытания кабельных линий ul.ul-1 > font.strong > li > a.dot
Зарядные станции для электромобилей ul.ul-1 > font.strong > li > a.dot
HOME div > font > h4 > a.dot

These are opportunities to improve the legibility of your content.

Names and labels

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
td.radius2 > div > div > iframe td.radius2 > div > div > 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Москва / Московская область td > div > font > h3
Электромонтажные работы под ключ в Москве и Московской области td.radius1 > div > font > h4

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
На главную Master-220v.Ru Аварийная служба электрики Электромонтажные работы … tbody > tr > td > ul.ul-1

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
На главную Master-220v.Ru td > ul.ul-1 > font.strong > li
Аварийная служба электрики td > ul.ul-1 > font.strong > li
Электромонтажные работы td > ul.ul-1 > font.strong > li
Обустройство систем освещения td > ul.ul-1 > font.strong > li
Ремонт электрооборудования td > ul.ul-1 > font.strong > li
Обслуживание электроустановок td > ul.ul-1 > font.strong > li
Электрификация объектов td > ul.ul-1 > font.strong > li
Срочный ремонт электрики td > ul.ul-1 > font.strong > li
Установка опор ЛЭП и освещения td > ul.ul-1 > font.strong > li
Ремонт воздушных линий td > ul.ul-1 > font.strong > li
Автономное электроснабжение td > ul.ul-1 > font.strong > li
Ремонт и замена электропроводки td > ul.ul-1 > font.strong > li
Установка стабилизатора напряжения td > ul.ul-1 > font.strong > li
Трансформаторные подстанции td > ul.ul-1 > font.strong > li
Уличное освещение td > ul.ul-1 > font.strong > li
Установка трубостоек td > ul.ul-1 > font.strong > li
Ввод электричества td > ul.ul-1 > font.strong > li
Проектирование и расчеты td > ul.ul-1 > font.strong > li
Промышленный электромонтаж td > ul.ul-1 > font.strong > li
Заземление и Молниезащита td > ul.ul-1 > font.strong > li
Испытания кабельных линий td > ul.ul-1 > font.strong > li
Электролаборатория td > ul.ul-1 > font.strong > li
Зарядные станции для электромобилей td > ul.ul-1 > font.strong > li
Автовышка для электромонтажных работ td > ul.ul-1 > font.strong > li
Допуски - Свидетельства - Разрешения td > ul.ul-1 > font.strong > li

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.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
«ПрофЭлектро - 220/380» Комплексные услуги – электромонтажные работы, ремонт … tbody > tr > td > table
Установка трубостойки Аварийная электрика Ремонт воздушных линий Э… tbody > tr > td > table

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
«ПрофЭлектро - 220/380» Комплексные услуги – электромонтажные работы, ремонт … tbody > tr > td > table
Установка трубостойки Аварийная электрика Ремонт воздушных линий Э… tbody > tr > td > table
○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Image elements do not have `[alt]` attributes that are redundant text.
●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-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 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
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has a valid value for its `[lang]` attribute
○`<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
○Form elements have associated labels
○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
○`<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
○Elements with visible text labels have matching accessible names.
C
Heading Hierarchy
Action
13 headings, 2 skip(s)
REVIEW
13 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Электрик срочно
  • H2 Экстренные выезды круглосуточно. Все виды работ.
  • H2 +7 (925) 671-02-25
  • H1 Услуги электромонтажа в Москве и Московской области duplicate H1
  • H3 Москва / Московская область skipped
  • H2 +7 (925) 671-02-25
  • H3 Оценка наших услуг:
  • H2 ПРОИЗВОДИМ - ПРОЕКТИРУЕМ - РЕМОНТИРУЕМ РЕШЕНИЕ ПРОБЛЕМ С ЭЛЕКТРИЧЕСТВОМ
  • H3 Работаем с физическими и юридическими лицами, УСН и НДС Оплата: Наличные, безналичная оплата, перевод. Авари�
  • H2 Производим работы по всей Москве и области (до ЦКАД) в жилых и нежилых помещениях. Обслуживаем СНТ, ДНП, КП, Ч�
  • H4 Электромонтажные работы под ключ в Москве и Московской области skipped
  • H4 Срочные услуги электрика - Срочный вызов электрика - Частная платная аварийная электрика [HOME]
  • H4 Срочные услуги по решению проблем с электроснабжением жилых и коммерческих объектов !!!

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

B
Mobile-Readable Font Sizes
99% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
99% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 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: <a> 10.0px ("ПрофЭлектро - 220/380 на карте Ступино —...").
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

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

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

10 pass 10 fail WCAG AA
h2 ПРОИЗВОДИМ - ПРОЕКТИР…
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 РЕШЕНИЕ ПРОБЛЕМ С ЭЛЕ…
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Работаем с физическим…
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Оплата: Наличные, безн…
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 , диагностика, поиск и …
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
a Электромонтаж
3.46:1
#FF0000
on
#EFEFE6
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Освещение
2.92:1
#FF0000
on
#DCDCDC
needs 4.5:1 (normal text)
16px · above the fold
a Ремонт электрики
2.92:1
#FF0000
on
#DCDCDC
needs 4.5:1 (normal text)
16px · above the fold
a Энергоучет
2.92:1
#FF0000
on
#DCDCDC
needs 4.5:1 (normal text)
16px · mid-page
a Электрификация
3.29:1
#FF0000
on
#E7E9ED
needs 4.5:1 (normal text)
16px · mid-page

1 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 ПРОИЗВОДИМ…1.18:13.0:1
#000000
#181818
Fail
h2 РЕШЕНИЕ ПР…1.18:13.0:1
#000000
#181818
Fail
h3 Работаем с …1.18:13.0:1
#000000
#181818
Fail
h3 Оплата: Нал…1.18:13.0:1
#000000
#181818
Fail
h3 , диагности…1.18:13.0:1
#000000
#181818
Fail
title Электрик с…17.24:14.5:1
#000000
#E6E9ED
Pass
strong Электрик с…17.59:13.0:1
#000000
#E9EBEF
Pass
strong Экстренные…17.57:13.0:1
#000000
#E9EBED
Pass
a +7 (925) 671-02-2513.18:14.5:1
#00008B
#EEEEEE
Pass
u ПрофЭлектр…17.90:14.5:1
#000000
#F0ECEB
Pass
u Комплексны…17.75:14.5:1
#000000
#F3EAE8
Pass
strong –18.17:13.0:1
#000000
#F8ECE9
Pass
a электромон…12.94:14.5:1
#290870
#F4E9E5
Pass
a ремонт эле…12.17:14.5:1
#290870
#E7E4E2
Pass
a обслуживан…13.61:14.5:1
#290870
#F6F0E8
Pass
a Электромон…3.46:14.5:1
#FF0000
#EFEFE6
Fail
a Освещение2.92:14.5:1
#FF0000
#DCDCDC
Fail
a Ремонт эле…2.92:14.5:1
#FF0000
#DCDCDC
Fail
a Энергоучет2.92:14.5:1
#FF0000
#DCDCDC
Fail
a Электрифик…3.29:14.5:1
#FF0000
#E7E9ED
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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
All 46 images OK
PASS
All 46 images OK
Info::
46 image(s) with good alt text
46 images 46 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://yandex.ru/maps-reviews-widget/24294371076?comments")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback