Skip to content
https://elektrik-24.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
6
REVIEW
7
PASS
11
INFO
0
Checks
24
11 PASS 7 REVIEW 6 FIX
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.
D
Tabindex Anti-Patterns
Action
0 positive, 27 -1-on-focusable
FIX
0 positive, 27 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 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
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #t-main-content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO (missing!)

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

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

C
Form Accessibility
Action
30 of 31 controls have issues
REVIEW
30 of 31 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="t898__btn_input_2122315121">
Warning::
29 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="Email" id="input_1495810354468">; <input type="text" name="Name" id="input_1495810359387">; <textarea name="Textarea" id="input_1495810410810">; <input type="email" name="Email" id="input_1495810354468">; <input type="text" name="Name" id="input_1495810359387">; <textarea name="Textarea" id="input_1495810410810">; <input type="email" name="Email" id="input_1495810354468">; <input type="text" name="Name" id="input_1495810359387">; <textarea name="Textarea" id="input_1495810410810">; <input type="text" name="Name" id="input_1495810359387"> (+19 more)
Info::
1 control(s) properly labeled
31 controls
1 labeled
29 placeholder only
1 unlabeled
ControlTypeLabelMethod
Checkboxcheckboxnone
#input_1495810359387text(Имя)placeholder only
#input_1495810410810textarea(Напишите Ваш вопрос)placeholder only
#input_1495810354468email(Укажите Ваш E-mail)placeholder only
#input_1495810359387text(Имя)placeholder only
#input_1495810410810textarea(Напишите Ваш вопрос)placeholder only
#input_1495810354468email(Укажите Ваш E-mail)placeholder only
#input_1495810359387text(Имя)placeholder only
#input_1495810410810textarea(Напишите Ваш отзыв)placeholder only
#input_1495810359387text(Ваше имя)placeholder only
#input_1495810410810tel(Ваш телефон)placeholder only
#input_1495810359387text(Ваше имя)placeholder only
#input_1495810410810tel(Ваш телефон)placeholder only
#input_1496404991787tel(+7 (999) 999-9999)placeholder only
#input_1495810359387text(Ваше имя)placeholder only
#input_1495810410810tel(Ваш телефон)placeholder only
#input_1495810359387text(Ваше имя)placeholder only
#input_1495810410810tel(Ваш телефон)placeholder only
#input_1495810359387text(Ваше имя)placeholder only
#input_1495810410810tel(Ваш телефон)placeholder only
#input_1495810359387text(Ваше имя)placeholder only
#input_1495810410810tel(Ваш телефон)placeholder only
#input_1495810359387text(Ваше имя)placeholder only
#input_1495810410810tel(Ваш телефон)placeholder only
#input_1495810359387text(Ваше имя)placeholder only
#input_1495810410810tel(Ваш телефон)placeholder only
#input_1496404991787tel(+7 (999) 999-9999)placeholder only
#input_8758215262980tel((000) 000-00-00)placeholder only
#input_8758215262981text(Имя)placeholder only
#input_1495810354468email(Укажите Ваш E-mail)placeholder only
#t898__btn_input_2122315121checkbox(none)none

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

<input type="checkbox" id="t898__btn_input_2122315121">

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="email" name="Email" id="input_1495810354468">; <input type="text" name="Name" id="input_1495810359387">; <textarea name="Textarea" id="input_1495810410810">; <input type="email" name="Email" id="input_1495810354468">; <input type="text" name="Name" id="input_1495810359387">; <textarea name="Textarea" id="input_1495810410810">; <input type="email" name="Email" id="input_1495810354468">; <input type="text" name="Name" id="input_1495810359387">; <textarea name="Textarea" id="input_1495810410810">; <input type="text" name="Name" id="input_1495810359387"> (+19 more)

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

C
Mobile Keyboard & Autofill
Action
14/29 eligible field(s) missing autocomplete or inputmode
REVIEW
14/29 eligible field(s) missing autocomplete or inputmode
Warning::
14 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email, tel.
Got: <input type="email" name="Email" id="input_1495810354468">, <input type="email" name="Email" id="input_1495810354468">, <input type="email" name="Email" id="input_1495810354468">, <input type="tel" name="Phone" id="input_1495810410810">, <input type="tel" name="Phone" id="input_1495810410810">
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 error 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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 2 pass AA only
a To main content
3.74:1
#000000
on
#6A694C
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span УСЛУГИ
3.50:1
#000000
on
#206E6B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span ЭЛЕКТРИКИ
2.51:1
#000000
on
#1C5274
needs 4.5:1 (normal text)
16px · above the fold
span КОНТАКТЫ
2.01:1
#000000
on
#164362
needs 4.5:1 (normal text)
16px · above the fold
span 8 (926) 005-16-24
1.88:1
#000000
on
#153E5D
needs 4.5:1 (normal text)
16px · above the fold
span 8 (495) 070-76-37
3.09:1
#000000
on
#3F5E7A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span ЗАКАЗАТЬ
2.18:1
#000000
on
#26466C
needs 4.5:1 (normal text)
16px · above the fold
div Аварийный
2.38:1
#000000
on
#2F4B74
needs 4.5:1 (normal text)
16px · above the fold
div Услуги
2.47:1
#000000
on
#324D79
needs 4.5:1 (normal text)
16px · above the fold
div Срочно
2.72:1
#000000
on
#3B5282
needs 4.5:1 (normal text)
16px · above the fold
div Контакты
3.43:1
#000000
on
#6B5A86
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
div На верх
2.54:1
#000000
on
#3E4D79
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
h2 Какие зада…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 В каких слу…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Популярные…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Сопутствую…21.00:13.0:1
#000000
#FFFFFF
Pass
title Круглосуто…10.30:14.5:1
#000000
#A3B9C5
Pass
a To main content3.74:14.5:1
#000000
#6A694C
Fail
span УСЛУГИ3.50:14.5:1
#000000
#206E6B
Fail
span ПРАЙС6.72:14.5:1
#000000
#7696AB
Pass
span СРОЧНО5.63:14.5:1
#000000
#6489A0
Pass
span ЭЛЕКТРИКИ2.51:14.5:1
#000000
#1C5274
Fail
span КОНТАКТЫ2.01:14.5:1
#000000
#164362
Fail
span 8 (926) 005-16-241.88:14.5:1
#000000
#153E5D
Fail
span 8 (495) 070-76-373.09:14.5:1
#000000
#3F5E7A
Fail
span ЗАКАЗАТЬ2.18:14.5:1
#000000
#26466C
Fail
div Аварийный2.38:14.5:1
#000000
#2F4B74
Fail
div Услуги2.47:14.5:1
#000000
#324D79
Fail
div Срочно2.72:14.5:1
#000000
#3B5282
Fail
div Контакты3.43:14.5:1
#000000
#6B5A86
Fail
div На верх2.54:14.5:1
#000000
#3E4D79
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
8 headings
PASS
8 headings
Info::
Single H1 present
  • H1 ЭЛЕКТРИК КРУГЛОСУТОЧНО
  • H2 НАШИ УСЛУГИ
  • H2 ОБСЛУЖИВАЕМ МОСКВУ И МО
  • H2 Опытные электрики в Москве
  • H2 Какие задачи мы выполняем
  • H2 В каких случаях стоит круглосуточно вызывать электрика в Москве:
  • H2 Популярные вопросы
  • H2 Сопутствующие запросы
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 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: 3 all-caps heading(s)
A
Alt Text Quality
1 of 23 images have issues
PASS
1 of 23 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
22 decorative image(s) correctly marked
23 images 22 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+
Form Input Types
31 form control(s) checked, no type mismatches
PASS
31 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
31 form control(s) checked, no input-semantic issues
PASS
31 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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+
Mobile-Readable Font Sizes
All 25 visible text node(s) render at >= 12 CSS pixels
PASS
All 25 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 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.
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.
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 25 passed
PASS
93

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.t722__content > div.t722__textwrapper > div.t722__descr > a
Перезвоним div.t-form__inputsbox > div.t-form__submit > button.t-submit > span.t-btnflex__text
Прайс на ремонтные, монтажные и аварийные работы div.t812 > div.t-section__container > div.t-col > div.js-block-header-title
Вызвать срочно div.t-form__inputsbox > div.t-form__submit > button.t-submit > span.t-btnflex__text
ВЫЗВАТЬ ЭЛЕКТРИКА div.t-col > div.t-section__bottomwrapper > a.t-btn > span.t-btnflex__text
вызвать электрика div.t530__cell > div.t530__bubble > div.t530__text > a
Вызвал электрика на дом div.t530__cell > div.t530__bubble > div.t530__text > a
Перезвоним div.t-form__inputsbox > div.t-form__submit > button.t-submit > span.t-btnflex__text
АВАРИЙНЫЙ ЭЛЕКТРИК a.t405__link > div.t405__textwrapper > div.t405__uptitle > span.t405__tag
ВЫЗВАТЬ ЭЛЕКТРИКА a.t405__link > div.t405__textwrapper > div.t405__uptitle > span.t405__tag
ЭЛЕКТРИК НА ДОМ a.t405__link > div.t405__textwrapper > div.t405__uptitle > span.t405__tag
ЭЛЕКТРИК ПО МОСКВЕ a.t405__link > div.t405__textwrapper > div.t405__uptitle > span.t405__tag
УСЛУГИ ЭЛЕКТРИКА a.t405__link > div.t405__textwrapper > div.t405__uptitle > span.t405__tag
ЭЛЕКТРИК СРОЧНО a.t405__link > div.t405__textwrapper > div.t405__uptitle > span.t405__tag
Показать еще div.t405 > div.t405__buttonwrapper > div.t-btn > span.t-btnflex__text
© elektrik-24 div.t463__colwrapper > div.t463__col > div.t463__typo > div

These are opportunities to improve the legibility of your content.

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.

○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●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
●ARIA IDs are unique
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○`<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 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
○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
○`<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.
○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