https://courageous-pithivier-1ca553.netlify.app/?fbclid=fbclid

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 3 REVIEW 6 FIX

Landmark Structure

Action

2 landmarks

FIX

2 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark 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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 2.4.1

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

✓ 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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #0a0a0a

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 ModePartial Dark Mode

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 ✗

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (6 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (6 below threshold)

6 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: <small> 11.0px ("годин"); <small> 11.0px ("хвилин"); <small> 11.0px ("секунд"); <small> 11.0px ("годин"); <small> 11.0px ("хвилин").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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.52:1

#000000

#2A2D33

needs 3.0:1 (large text)

32px · above the fold

h2 Тепла. Зручна. Без зай�…

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Характеристики

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Чому її беруть на зиму

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Як вона виглядає в жит…

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Обери свій колір

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Доставка та оплата

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Оформити замовлення

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Тепло і захист

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Зручність

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Вигляд і вибір

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Чорна

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Червона

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Синя

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Хакі

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Підібрати розмір за 20 …

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Розмірна сітка

1.07:1

#000000

#0A0C11

needs 3.0:1 (large text)

19px · bottom of viewport

title Чоловіча зимова куртк…

1.52:1

#000000

#2A2D33

needs 4.5:1 (normal text)

16px · top of page (header area)

span Акція −

1.52:1

#000000

#2A2D33

needs 4.5:1 (normal text)

16px · top of page (header area)

span 29%

1.52:1

#000000

#2A2D33

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Чоловіча з�…	1.52:1	3.0:1	#000000	#2A2D33	Fail
h2 Тепла. Зруч…	1.07:1	3.0:1	#000000	#0A0C11	Fail
h2 Характерис…	1.07:1	3.0:1	#000000	#0A0C11	Fail
h2 Чому її бер…	1.07:1	3.0:1	#000000	#0A0C11	Fail
h2 Як вона виг…	1.07:1	3.0:1	#000000	#0A0C11	Fail
h2 Обери свій …	1.07:1	3.0:1	#000000	#0A0C11	Fail
h2 Доставка т�…	1.07:1	3.0:1	#000000	#0A0C11	Fail
h2 Оформити з�…	1.07:1	3.0:1	#000000	#0A0C11	Fail
h3 Тепло і зах…	1.07:1	3.0:1	#000000	#0A0C11	Fail
h3 Зручність	1.07:1	3.0:1	#000000	#0A0C11	Fail
h3 Вигляд і ви…	1.07:1	3.0:1	#000000	#0A0C11	Fail
h3 Чорна	1.07:1	3.0:1	#000000	#0A0C11	Fail
h3 Червона	1.07:1	3.0:1	#000000	#0A0C11	Fail
h3 Синя	1.07:1	3.0:1	#000000	#0A0C11	Fail
h3 Хакі	1.07:1	3.0:1	#000000	#0A0C11	Fail
h3 Підібрати �…	1.07:1	3.0:1	#000000	#0A0C11	Fail
h3 Розмірна с�…	1.07:1	3.0:1	#000000	#0A0C11	Fail
title Чоловіча з�…	1.52:1	4.5:1	#000000	#2A2D33	Fail
span Акція −	1.52:1	4.5:1	#000000	#2A2D33	Fail
span 29%	1.52:1	4.5:1	#000000	#2A2D33	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

17 headings

PASS

17 headings

Single H1 present

H1 Чоловіча зимова куртка Frost
H2 Тепла. Зручна. Без зайвого.
H2 Характеристики
H2 Чому її беруть на зиму
H3 Тепло і захист
H3 Зручність
H3 Вигляд і вибір
H2 Як вона виглядає в житті
H2 Обери свій колір
H3 Чорна
H3 Червона
H3 Синя
H3 Хакі
H3 Підібрати розмір за 20 секунд
H3 Розмірна сітка
H2 Доставка та оплата
H2 Оформити замовлення

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 14 images OK

PASS

All 14 images OK

1 image(s) with alt text over 125 characters

13 image(s) with good alt text

14 images 13 good alt text

Issue	Count
too long	1 image(s)

A+

Form Accessibility

All 18 controls labeled

PASS

All 18 controls labeled

18 control(s) properly labeled

18 controls

18 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#fit-h	number	Зріст, см	none
#fit-w	number	Вага, кг	none
#fit-c	number	Обхват грудей, см (необов’язково, але точніше)	none
fitpref	radio		none
fitpref	radio		none
fitpref	radio		none
color	radio		none
color	radio		none
color	radio		none
color	radio		none
size	radio		none
size	radio		none
size	radio		none
size	radio		none
size	radio		none
size	radio		none
#f-name	text	Ім’я	aria-label
#f-phone	tel	Телефон	aria-label

A+

Link & Button Quality

11 links, 3 buttons — all OK

PASS

11 links, 3 buttons — all OK

1 link(s) open in new tab without warning

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

Got: /politics

10 link(s) with descriptive text

11 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/politics	Політика конфід�…	new tab	Add '(opens in new tab)' to text

13 links and buttons have descriptive text

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

/politics

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

18 form control(s) checked, no type mismatches

PASS

18 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

All 5 eligible field(s) carry autocomplete/inputmode

PASS

All 5 eligible field(s) carry autocomplete/inputmode

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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

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

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 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
Акція −29% на всі кольори `body > div.wrap > div.topbar > span`
29% `div.wrap > div.topbar > span > span.js-off`
Закінчується через 23:57:24 `body > div.wrap > div.topbar > span`
НОВИНКА ЗИМИ `div.wrap > header.hero > div.hero__body > span.hero__badge`
3 500 `article.color > div.color__body > div.color__price > s.js-onum`
3 500 `article.color > div.color__body > div.color__price > s.js-onum`
3 500 `article.color > div.color__body > div.color__price > s.js-onum`
3 500 `article.color > div.color__body > div.color__price > s.js-onum`
3 500 грн `div.order__card > form#order_form > div.total > s.total__old`

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

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

●`[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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

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

●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

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

●Touch targets have sufficient size and spacing.

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

●Heading elements appear in a sequentially-descending order

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

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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