https://studioglass.ua/?srsltid=AfmBOorR_9oMrvnyWn3YEJOwuhmKA3daecu2_JGxPxX23K_k9dm-TCQT

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

10 PASS 5 REVIEW 9 FIX

Form Accessibility

Action

13 of 13 controls have issues

FIX

13 of 13 controls have issues

12 control(s) without accessible label

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

Got: <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="email" name="email">; <input type="text">; <input type="text">; <input type="text">; <input type="text"> (+2 more)

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="search">

13 controls

0 labeled

1 placeholder only

12 unlabeled

Control	Type	Label	Method
search	search	(Пошук)	placeholder only
input	text	(none)	none
input	text	(none)	none
input	text	(none)	none
input	text	(none)	none
input	text	(none)	none
email	email	(none)	none
input	text	(none)	none
input	text	(none)	none
input	text	(none)	none
input	text	(none)	none
input	text	(none)	none
input	text	(none)	none

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

<input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="email" name="email">; <input type="text">; <input type="text">; <input type="text">; <input type="text"> (+2 more)

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

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

Link & Button Quality

Action

30 issue(s) across 105 links and 20 buttons

FIX

30 issue(s) across 105 links and 20 buttons

17 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; /auth/login; /auth/login; /auth/login; a (#111 on page); https://www.instagram.com/studioglass.ua; viber://chat?number=+380954676913 ; https://t.me/StudioGlass; /dzerkalo-v-derev-yaniy-rami-studioglass-frost-wind-light-strap; /dzerkalo-v-derev-yaniy-rami-studioglass-red-fire-light-strap (+7 more)

2 link(s) open in new tab without warning

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

Got: https://maps.app.goo.gl/wbT9sq4JhYErpLFC8; https://studioglass.ua/privat-policy

13 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.search-button (#206 on page); button.search-close (#211 on page); button.btn-close (#1029 on page); button.btn-close (#1041 on page); button.btn-close (#1060 on page); button.btn-close (#1079 on page); button.btn-close (#1098 on page); button.btn-close (#1107 on page); button.btn-close (#1147 on page); button.btn-close (#1166 on page) (+3 more)

86 link(s) with descriptive text

105 links

17 empty

0 generic text

2 new tab

13 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/auth/login	(empty)	empty	Add link text or aria-label
/auth/login	(empty)	empty	Add link text or aria-label
/auth/login	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.instagram.com/studioglass.ua	(empty)	empty	Add link text or aria-label
viber://chat?number=+380954676913	(empty)	empty	Add link text or aria-label
https://t.me/StudioGlass	(empty)	empty	Add link text or aria-label
wood-mirrors	Wood Mirrors	img no alt	Add alt attribute to the image
dushovi-kabini	Shower Boxes	img no alt	Add alt attribute to the image
led-mirror	Led Mirrors	img no alt	Add alt attribute to the image
design-series	Design Series	img no alt	Add alt attribute to the image
iron-mirror	Iron Mirrors	img no alt	Add alt attribute to the image
amo-mirrors	Amo Mirrors	img no alt	Add alt attribute to the image
tovari-v-nayavnosti	Товари в наявнос…	img no alt	Add alt attribute to the image
mega-mirrors	Mega Mirrors	img no alt	Add alt attribute to the image
vanni-z-kamenyu	Ванни з каменю	img no alt	Add alt attribute to the image
/shtorka-dlya-vannoyi-liri-cr	ТОП продажів	img no alt	Add alt attribute to the image
/sklyani-dveri-dlya-dushu-colombo	ТОП продажів	img no alt	Add alt attribute to the image
/sklyani-dveri-dlya-dushu-stenli	ТОП продажів	img no alt	Add alt attribute to the image
/belfast-classic-aluminium-945	ТОП продажів	img no alt	Add alt attribute to the image
/dzerkalo-v-derev-yaniy-rami-studioglass…	(empty)	empty	Add link text or aria-label
/dzerkalo-v-derev-yaniy-rami-studioglass…	(empty)	empty	Add link text or aria-label
/dzerkalo-v-derev-yaniy-rami-studioglass…	(empty)	empty	Add link text or aria-label
/dzerkalo-v-derev-yaniy-rami-studioglass…	(empty)	empty	Add link text or aria-label
/vanna-z-litogo-kamenyu-studiostone-bari…	(empty)	empty	Add link text or aria-label
dzerkalni-instalyaciyi-studio-glass-dlya…	08.04.2025	img no alt	Add alt attribute to the image
yak-ne-vtratiti-garantiyu	28.03.2025	img no alt	Add alt attribute to the image
yak-doglyadati-za-dushovoyu-kabinoyu-shc…	26.03.2025	img no alt	Add alt attribute to the image
dzerkalni-instalyaciyi-studio-glass-dlya…	08.04.2025	img no alt	Add alt attribute to the image
yak-ne-vtratiti-garantiyu	28.03.2025	img no alt	Add alt attribute to the image
yak-doglyadati-za-dushovoyu-kabinoyu-shc…	26.03.2025	img no alt	Add alt attribute to the image
https://maps.app.goo.gl/wbT9sq4JhYErpLFC…	с. Сокільники, ву…	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://studioglass.ua/privat-policy	Політики конфід�…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

93 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; /auth/login; /auth/login; /auth/login; a (#111 on page); https://www.instagram.com/studioglass.ua; viber://chat?number=+380954676913 ; https://t.me/StudioGlass; /dzerkalo-v-derev-yaniy-rami-studioglass-frost-wind-light-strap; /dzerkalo-v-derev-yaniy-rami-studioglass-red-fire-light-strap (+7 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://maps.app.goo.gl/wbT9sq4JhYErpLFC8; https://studioglass.ua/privat-policy

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.search-button (#206 on page); button.search-close (#211 on page); button.btn-close (#1029 on page); button.btn-close (#1041 on page); button.btn-close (#1060 on page); button.btn-close (#1079 on page); button.btn-close (#1098 on page); button.btn-close (#1107 on page); button.btn-close (#1147 on page); button.btn-close (#1166 on page) (+3 more)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Mobile Keyboard & Autofill

Action

3/3 eligible field(s) missing autocomplete or inputmode

FIX

3/3 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: email.

Got: <input type="email" name="email">

2 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, email.

Got: <input type="search" name="search">, <input type="email" name="email">

Tap Target Adequacy

Action

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

FIX

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

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Heading Hierarchy

9 headings, 1 skip(s)

REVIEW

9 headings, 1 skip(s)

Multiple H1 headings (8 found)

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

Heading level skipped: H1 → H6 (missing H2)

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

H1 Ванни з литого каменю
H1 В наявності! duplicate H1
H1 Design series duplicate H1
H1 Wood mirror duplicate H1
H1 Led mirror duplicate H1
H1 Shower boxes duplicate H1
H1 Ванни з литого каменю duplicate H1
H1 В наявності! duplicate H1
H6 StudioGlass - Львівська Фабрика Дзеркал skipped

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

Alt Text Quality

4 of 54 images have issues

REVIEW

4 of 54 images have issues

4 image(s) with filename as alt text

50 decorative image(s) correctly marked

54 images 50 decorative 4 generic

Issue	Count
filename	4 image(s)

Iframe Accessibility

2/2 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/2 iframe(s) missing title; 0 placeholder(s)

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.

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.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA 10 pass AA only

title ➤ Studio Glass • Львівська …

1.83:1

#000000

#47362A

needs 4.5:1 (normal text)

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

b Меню

2.06:1

#000000

#543C2B

needs 3.0:1 (large text)

16px · top of page (header area)

a Оферта

2.13:1

#000000

#4A4238

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Питання та відповіді

1.28:1

#000000

#231F1A

needs 4.5:1 (normal text)

16px · above the fold

div Ваш список побажань п�…

1.59:1

#000000

#352F28

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div Наповніть його товара…

1.69:1

#000000

#393331

needs 4.5:1 (normal text)

16px · above the fold

div Ваш шопер порожній

1.47:1

#000000

#332823

needs 4.5:1 (normal text)

16px · above the fold

div Наповніть його товара…

1.33:1

#000000

#29211B

needs 4.5:1 (normal text)

16px · above the fold

a Mirrors

1.22:1

#000000

#1F1A14

needs 4.5:1 (normal text)

16px · above the fold

3 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 Ванни з лит…	3.78:1	3.0:1	#000000	#AE4A09	Pass
h1 В наявност�…	3.78:1	3.0:1	#000000	#AE4A09	Pass
h1 Design series	3.78:1	3.0:1	#000000	#AE4A09	Pass
h1 Wood mirror	3.78:1	3.0:1	#000000	#AE4A09	Pass
h1 Led mirror	3.78:1	3.0:1	#000000	#AE4A09	Pass
h1 Shower boxes	3.78:1	3.0:1	#000000	#AE4A09	Pass
h1 Ванни з лит…	3.78:1	3.0:1	#000000	#AE4A09	Pass
h1 В наявност�…	3.78:1	3.0:1	#000000	#AE4A09	Pass
title ➤ Studio Glass •…	1.83:1	4.5:1	#000000	#47362A	Fail
b Меню	2.06:1	3.0:1	#000000	#543C2B	Fail
b 0800 33 08 36	3.86:1	3.0:1	#000000	#76675A	Pass
a Головна	5.81:1	4.5:1	#000000	#978373	Pass
a Колекції т�…	13.93:1	4.5:1	#000000	#DDD0C8	Pass
a Оферта	2.13:1	4.5:1	#000000	#4A4238	Fail
a Питання та …	1.28:1	4.5:1	#000000	#231F1A	Fail
div Ваш список …	1.59:1	4.5:1	#000000	#352F28	Fail
div Наповніть �…	1.69:1	4.5:1	#000000	#393331	Fail
div Ваш шопер п…	1.47:1	4.5:1	#000000	#332823	Fail
div Наповніть �…	1.33:1	4.5:1	#000000	#29211B	Fail
a Mirrors	1.22:1	4.5:1	#000000	#1F1A14	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.

Lighthouse Accessibility Audits

Action

Score 73/100 — 8 failing, 20 passed

REVIEW

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.search-wrapper > div.search-inner > form.search-form > button.search-close `div.search-wrapper > div.search-inner > form.search-form > button.search-close`
body.loaded > div.cart > button.btn-close `body.loaded > div.cart > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`
div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close `div.popup-wrapper > div.popup-content > div.popup-container > button.btn-close`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`
div.popup-align > form.popup-form > div.input-field-wrapper > input.input `div.popup-align > form.popup-form > div.input-field-wrapper > input.input`

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
div.video-popup-container > div.video-popup-align > div.embed-responsive > iframe.embed-responsive-item `div.video-popup-container > div.video-popup-align > div.embed-responsive > iframe.embed-responsive-item`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header > div.header-wrapper > div.header-inner > a.header-logo `header > div.header-wrapper > div.header-inner > a.header-logo`
header > div.header-wrapper > div.header-inner > a.header-phone `header > div.header-wrapper > div.header-inner > a.header-phone`
div.header-inner > div.header-btn-wrap > div.user-menu > a `div.header-inner > div.header-btn-wrap > div.user-menu > a`
div.side-menu > ul.social > li > a `div.side-menu > ul.social > li > a`
div.side-menu > ul.social > li > a `div.side-menu > ul.social > li > a`
div.side-menu > ul.social > li > a `div.side-menu > ul.social > li > a`
div.swiper-slide > div.product > div.product_image-wrap > a.product_image `div.swiper-slide > div.product > div.product_image-wrap > a.product_image`
div.swiper-slide > div.product > div.product_image-wrap > a.product_image `div.swiper-slide > div.product > div.product_image-wrap > a.product_image`
div.swiper-slide > div.product > div.product_image-wrap > a.product_image `div.swiper-slide > div.product > div.product_image-wrap > a.product_image`
div.swiper-slide > div.product > div.product_image-wrap > a.product_image `div.swiper-slide > div.product > div.product_image-wrap > a.product_image`
div.swiper-slide > div.product > div.product_image-wrap > a.product_image `div.swiper-slide > div.product > div.product_image-wrap > a.product_image`
div.footer-company > ul > li > a.footer-company-item `div.footer-company > ul > li > a.footer-company-item`
div.footer-company > ul > li > a.footer-company-item `div.footer-company > ul > li > a.footer-company-item`
div.footer-company > ul > li > a.footer-company-item `div.footer-company > ul > li > a.footer-company-item`
div.footer-company > ul > li > a.footer-company-item `div.footer-company > ul > li > a.footer-company-item`

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
StudioGlass - Львівська Фабрика Дзеркал `div.col-xl-10 > div.seo-text-block > div.text > h6`

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Go to slide 1 `div.swiper-entry > div.swiper-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.swiper-entry > div.swiper-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.swiper-entry > div.swiper-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.swiper-entry > div.swiper-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.swiper-entry > div.swiper-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div.swiper-entry > div.swiper-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 7 `div.swiper-entry > div.swiper-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 8 `div.swiper-entry > div.swiper-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 1 `div.swiper-entry > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.swiper-entry > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.swiper-entry > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`

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
Замовити дзвінок `body.loaded > bwchat#bwc-wrap > div#bwc-widget-action > button.bwc-get-call`

○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

●Image elements have `[alt]` attributes

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

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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 Text Quality

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

PASS

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

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

A+

Form Input Types

13 form control(s) checked, no type mismatches

PASS

13 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "uk"

PASS

Lang attribute set to "uk"

<html lang="uk"> is set and valid

Got: uk

A+

Tabindex Anti-Patterns

22 explicit tabindex attribute(s) checked, no anti-patterns

PASS

22 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Mobile-Readable Font Sizes

All 59 visible text node(s) render at >= 12 CSS pixels

PASS

All 59 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

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

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.

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