Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 6 REVIEW 5 FIX

Mobile Keyboard & Autofill

Action

4/5 eligible field(s) missing autocomplete or inputmode

FIX

4/5 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name.

Got: <input type="text" name="name" id="callback_name">

3 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: search.

Got: <input type="search" name="s" id="woocommerce-product-search-field-0">, <input type="search" name="s" id="woocommerce-product-search-field-1">, <input type="search" name="s" id="woocommerce-product-search-field-2">

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Tap Target Adequacy

3 tap target(s) too small or too close together

REVIEW

3 tap target(s) too small or too close together

3 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

92% of visible text renders at >= 12 CSS px (13 below threshold)

REVIEW

92% of visible text renders at >= 12 CSS px (13 below threshold)

13 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: <span> 11.0px ("8 (906) 056-00-55"); <a> 11.0px ("Заказать звонок"); <span> 10.5px ("Доставка"); <span> 10.5px ("и оплата"); <a> 11.0px ("Смотреть все →").

404 Error Page

Action

Could not test

REVIEW

Could not test

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.

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA 1 pass AA only

title Кубачинское серебро к…

2.06:1

#000000

#414141

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.71:1

#000000

#353535

needs 4.5:1 (normal text)

16px · top of page (header area)

span перед приездом звонок…

1.18:1

#000000

#181818

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span 8 (906) 056-00-55

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

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)

Element	Ratio	Required	FG	BG	Result
h1 Кубачинско…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Серебряная…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Серебряные…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Столовое с�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Все раздел�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Кубачинско…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ассортимен…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Почему выб�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Как купить …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Популярные…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Уход за сер…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Заказать о�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Столовое с�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Серебряная…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Подарки из …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Кубачинско…	2.06:1	4.5:1	#000000	#414141	Fail
a Skip to content	1.71:1	4.5:1	#000000	#353535	Fail
span перед прие�…	1.18:1	4.5:1	#000000	#181818	Fail
span 8 (906) 056-00-55	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span Заказать з�…	6.99:1	4.5:1	#000000	#939598	Pass

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

18 headings

PASS

18 headings

Single H1 present

H2 Серебряная посуда
H2 Серебряные подарки
H2 Столовое серебро
H2 Все разделы
H3 Серебряная посуда
H3 Серебряные подарки
H3 Столовое серебро
H1 Кубачинское серебро ручной работы, посуда, подарки и украшения из серебра 925 пробы
H2 Кубачинское серебро традиции ручной работы из Дагестана
H2 Ассортимент магазина: столовое серебро, посуда, подарки
H3 Столовое серебро 925 пробы
H3 Серебряная посуда 875 пробы
H3 Подарки из серебра на любой повод
H2 Почему выбирают SerebroKubachi.ru
H2 Как купить кубачинское серебро в Москве
H2 Популярные категории товаров
H2 Уход за серебром: как сохранить красоту на десятилетия
H2 Заказать обратный звонок

A+

Heading Text Quality

All 18 heading(s) have substantive, well-formed text

PASS

All 18 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 48 images OK

PASS

All 48 images OK

10 decorative image(s) correctly marked

38 image(s) with good alt text

48 images 38 good alt text 10 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#woocommerce-product-search-field-0	search	Искать:	for/id
#woocommerce-product-search-field-1	search	Искать:	for/id
#woocommerce-product-search-field-2	search	Искать:	for/id
#callback_name	text	Имя *	for/id
#callback_phone	tel	Телефон *	for/id

A+

Link & Button Quality

161 links, 8 buttons — all OK

PASS

161 links, 8 buttons — all OK

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://maps.google.com/?q=55°46'00.5,37°36'09.2

160 link(s) with descriptive text

161 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://maps.google.com/?q=55°46'00.5,3…	Магазин серебра …	new tab	Add '(opens in new tab)' to text
/	Фильтр по цене	img no alt	Add alt attribute to the image
/catalog/stolovoe-serebro/serebryanye-st…	Серебряные ложк�…	img no alt	Add alt attribute to the image
/catalog/serebryanaya-posuda/serebryanye…	Бокалы и кубки	img no alt	Add alt attribute to the image
/catalog/serebryanaya-posuda/vazy-konfet…	Вазы и сахарницы	img no alt	Add alt attribute to the image
/catalog/podarki/muzhchine/	Подарки мужчине	img no alt	Add alt attribute to the image

168 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://maps.google.com/?q=55°46'00.5,37°36'09.2

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

5 form control(s) checked, no input-semantic issues

PASS

5 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "ru-RU"

PASS

Lang attribute set to "ru-RU"

<html lang="ru-RU"> is set and valid

Got: ru-RU

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 24 passed

PASS

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
8 (906) 056-00-55 `div.header-block-block-1 > div.sk-topbar-actions > a.sk-phone-btn > span.sk-phone-text`
СМОТРЕТЬ ВСЕ → `div.kubachi-main-builder-v19 > div.kb-section-v19 > div.kb-header-v19 > a.kb-view-all-v19`
СМОТРЕТЬ ВСЕ → `div.kubachi-main-builder-v19 > div.kb-section-v19 > div.kb-header-v19 > a.kb-view-all-v19`
СМОТРЕТЬ ВСЕ → `div.kubachi-main-builder-v19 > div.kb-section-v19 > div.kb-header-v19 > a.kb-view-all-v19`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
БЛОГ `div.menu-menyu-futera-container > ul#menu-menyu-futera-1 > li.menu-item > a`
ОТЗЫВЫ `div.menu-menyu-futera-container > ul#menu-menyu-futera-1 > li.menu-item > a`
ДОСТАВКА И ОПЛАТА `div.menu-menyu-futera-container > ul#menu-menyu-futera-1 > li.menu-item > a`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
МЕНЮ `ul.mobile-nav > li.nav-icon > div.header-button > a.icon`
0 `div.flex-col > ul.mobile-nav > li.cart-item > a.header-cart-link`

○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

●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.

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○`<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

○`<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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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