Skip to content
https://mpzorro.ru

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
7
REVIEW
2
PASS
15
INFO
0
Checks
24
15 PASS 2 REVIEW 7 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 12 -1-on-focusable
FIX
0 positive, 12 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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 <a>
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 <a>
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 <a>
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 <a>
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 <a>
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 <a>
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 <a>
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 <a>
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 <a>
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 <a>
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 <a>
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
Mobile-Readable Font Sizes
Action
68% of visible text renders at >= 12 CSS px (88 below threshold)
FIX
68% of visible text renders at >= 12 CSS px (88 below threshold)
Warning::
88 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> 10.0px ("ПРОВЕРКА ВСЕГО ПЕРИОДА"); <span> 10.0px ("Первая поставка"); <strong> 10.0px ("Сегодня"); <span> 10.0px ("01"); <small> 9.0px ("Все операции по\u00a0артикулам").
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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::
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.
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 Компенсация за утерянные товары Wildberries | MPZORRO ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 теряет товары. Как най…
1.05:1
#000000
on
#070716
needs 3.0:1 (large text)
32px · above the fold
h2 Как мы оцениваем поте…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Как проходит проверка…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Какими данными подтве…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Какие результаты полу…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Официальные ответы Wild…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Как получить компенса…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Как начать проверку б…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Как оплачивается пров…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Что продавцы спрашива…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Остались ли у Wildberries н…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Сверяем вход
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Прослеживаем путь
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Фиксируем разрыв
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Забираем данные за ве…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Восстанавливаем движ…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Находим некомпенсиро…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Готовим и сопровождае…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Максимальная компенс…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Три кабинета — официа…
1.04:1
#000000
on
#060615
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 теряет тов…1.05:13.0:1
#000000
#070716
Fail
h2 Как мы оцен…1.04:13.0:1
#000000
#060615
Fail
h2 Как проход…1.04:13.0:1
#000000
#060615
Fail
h2 Какими дан…1.04:13.0:1
#000000
#060615
Fail
h2 Какие резу…1.04:13.0:1
#000000
#060615
Fail
h2 Официальны…1.04:13.0:1
#000000
#060615
Fail
h2 Как получи…1.04:13.0:1
#000000
#060615
Fail
h2 Как начать …1.04:13.0:1
#000000
#060615
Fail
h2 Как оплачи…1.04:13.0:1
#000000
#060615
Fail
h2 Что продав…1.04:13.0:1
#000000
#060615
Fail
h2 Остались л…1.04:13.0:1
#000000
#060615
Fail
h3 Сверяем вх…1.04:13.0:1
#000000
#060615
Fail
h3 Прослежива…1.04:13.0:1
#000000
#060615
Fail
h3 Фиксируем …1.04:13.0:1
#000000
#060615
Fail
h3 Забираем д…1.04:13.0:1
#000000
#060615
Fail
h3 Восстанавл…1.04:13.0:1
#000000
#060615
Fail
h3 Находим не…1.04:13.0:1
#000000
#060615
Fail
h3 Готовим и с…1.04:13.0:1
#000000
#060615
Fail
h3 Максимальн…1.04:13.0:1
#000000
#060615
Fail
h3 Три кабине…1.04:13.0:1
#000000
#060615
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
Landmark Structure
21 landmarks
PASS
21 landmarks
Info::
<main> landmark present
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 ASIDE CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+
Heading Hierarchy
37 headings
PASS
37 headings
Info::
Single H1 present
  • H1 Wildberries теряет товары. Как найти их в данных и добиться компенсации?
  • H2 Как мы оцениваем потери товара на маркетплейсе Wildberries?
  • H3 Сверяем вход
  • H3 Прослеживаем путь
  • H3 Фиксируем разрыв
  • H2 Как проходит проверка потерь на маркетплейсе Wildberries?
  • H3 Забираем данные за весь период
  • H3 Восстанавливаем движение товара
  • H3 Находим некомпенсированные потери
  • H3 Готовим и сопровождаем претензию
  • H2 Какими данными подтверждается потеря товара на Wildberries?
  • H2 Какие результаты получают продавцы Wildberries?
  • H3 Максимальная компенсация по одной претензии
  • H3 Три кабинета — официальные ответы Wildberries
  • H3 Компенсация за 164 единицы товара
  • H2 Официальные ответы Wildberries по претензиям
  • H2 Как получить компенсацию за товар после пожара на складе?
  • H2 Как начать проверку без риска для кабинета Wildberries?
  • H3 Бесплатная первичная оценка
  • H3 Договор через ЭДО
  • H3 Безопасный аналитический доступ
  • H3 Претензия и сопровождение
  • H2 Как оплачивается проверка потерь на Wildberries?
  • H2 Что продавцы спрашивают о проверке потерь на Wildberries?
  • H3 Что именно вы ищете?
  • H3 За какой период можно провести проверку?
  • H3 Нужно заранее знать, где потерялся товар?
  • H3 Вы работаете с потерями после пожаров?
  • H3 Как оплачивается работа?
  • H3 Вы гарантируете выплату?
  • H3 Нужен ли доступ к кабинету Wildberries?
  • H3 Заблокируют ли кабинет из-за претензии?
  • H3 Можно ли потерять повышенную СПП после претензии?
  • H3 Что входит в стартовый платёж 5 000 ₽?
  • H3 Что происходит, если Wildberries отказывает?
  • H3 Сколько времени занимает выплата?
  • H2 Остались ли у Wildberries некомпенсированные потери вашего товара?
A+
Heading Text Quality
All 37 heading(s) have substantive, well-formed text
PASS
All 37 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 15 images OK
PASS
All 15 images OK
Info::
15 image(s) with good alt text
15 images 15 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+
Document Language
Lang attribute set to "ru"
PASS
Lang attribute set to "ru"
Info::
<html lang="ru"> is set and valid
Got: ru
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
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.
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 25 passed
PASS
100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●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
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback