Skip to content
https://kharkov.ua

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
6
REVIEW
7
PASS
0
INFO
0
Checks
13
7 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Alt Text Quality
4 of 23 images have issues
REVIEW
4 of 23 images have issues
Warning::
4 image(s) with filename as alt text
Info::
12 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
23 images 7 good alt text 12 decorative 4 generic
IssueCount
filename4 image(s)
C
Form Accessibility
Action
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="yeart">; <select name="month">; <select name="dat">; <input type="image">
4 controls
0 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
yeartselect(none)none
monthselect(none)none
datselect(none)none
inputimage(none)none

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

<select name="yeart">; <select name="month">; <select name="dat">; <input type="image">

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

B
Favicon & Branding
7 icon(s) detected
REVIEW
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA 1 pass AA only
marquee Українськомовна верс…
1.92:1
#000000
on
#234240
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
font https://www.kharkiv.ua
1.49:1
#000000
on
#16302A
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
font *****
2.52:1
#000000
on
#395256
needs 4.5:1 (normal text)
16px · top of page (header area)
font https://coordinator.ua
2.38:1
#000000
on
#324F52
needs 4.5:1 (normal text)
16px · above the fold
font *****
1.79:1
#000000
on
#223D36
needs 4.5:1 (normal text)
16px · above the fold
div Наш QR-Код
2.08:1
#000000
on
#334730
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div Медиа партнер
1.38:1
#000000
on
#212722
needs 4.5:1 (normal text)
16px · above the fold
div Погода
1.81:1
#000000
on
#283E25
needs 4.5:1 (normal text)
16px · above the fold
span Четверг 23.04.26, ночь
2.00:1
#000000
on
#2C452F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div Харьков
2.48:1
#000000
on
#37524D
needs 4.5:1 (normal text)
16px · above the fold
div +3°
2.48:1
#000000
on
#37524D
needs 4.5:1 (normal text)
16px · above the fold
p влажн.:
2.48:1
#000000
on
#37524D
needs 4.5:1 (normal text)
16px · mid-page
span 68%
2.48:1
#000000
on
#37524D
needs 4.5:1 (normal text)
16px · mid-page
p давл.:
2.48:1
#000000
on
#37524D
needs 4.5:1 (normal text)
16px · mid-page
span 743 мм
2.48:1
#000000
on
#37524D
needs 4.5:1 (normal text)
16px · mid-page
span 0 м/с
2.48:1
#000000
on
#37524D
needs 4.5:1 (normal text)
16px · mid-page
div Курсы валют
2.48:1
#000000
on
#37524D
needs 4.5:1 (normal text)
16px · mid-page
div ГОРОДСКИЕ НОВОСТИ
2.48:1
#000000
on
#37524D
needs 4.5:1 (normal text)
16px · mid-page

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
title Харьков - Х…6.03:14.5:1
#000000
#868B83
Pass
marquee Українсько…1.92:14.5:1
#000000
#234240
Fail
font https://www.kharkiv.…1.49:14.5:1
#000000
#16302A
Fail
font *****2.52:14.5:1
#000000
#395256
Fail
marquee Регламент …9.07:14.5:1
#000000
#A7ACA2
Pass
font https://coordinator.…2.38:14.5:1
#000000
#324F52
Fail
font *****1.79:14.5:1
#000000
#223D36
Fail
div Наш QR-Код2.08:14.5:1
#000000
#334730
Fail
div Медиа парт…1.38:14.5:1
#000000
#212722
Fail
div Погода1.81:14.5:1
#000000
#283E25
Fail
span Четверг 23.04…2.00:14.5:1
#000000
#2C452F
Fail
div Харьков2.48:14.5:1
#000000
#37524D
Fail
div +3°2.48:14.5:1
#000000
#37524D
Fail
p влажн.:2.48:14.5:1
#000000
#37524D
Fail
span 68%2.48:14.5:1
#000000
#37524D
Fail
p давл.:2.48:14.5:1
#000000
#37524D
Fail
span 743 мм2.48:14.5:1
#000000
#37524D
Fail
span 0 м/с2.48:14.5:1
#000000
#37524D
Fail
div Курсы валю…2.48:14.5:1
#000000
#37524D
Fail
div ГОРОДСКИЕ …2.48:14.5:1
#000000
#37524D
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.

C
Lighthouse Accessibility Audits
Action
Score 71/100 — 5 failing, 13 passed
REVIEW
71

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
49346018 div.thumb_wrapper > div.thumbd3 > div > font

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016… div > form > div.numpd > select.navform
Январь Февраль Март Апрель Май Июнь Июль Август Сентябрь Октябрь Ноябрь Декабрь div > form > div.numpd > select.navform
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 3… div > form > div.numpd > select.navform

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
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.wrap > div.sixt > div > a.nob div.wrap > div.sixt > div > a.nob
div.thumb_wrapper > div.thumbd3 > div > a div.thumb_wrapper > div.thumbd3 > div > a

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.

Best practices

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●`<input type="image">` elements have `[alt]` text
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●The page contains a heading, skip link, or landmark region
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○`<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
○Heading elements appear in a sequentially-descending order
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○Form elements have associated labels
○`<object>` elements have alternate text
○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
○Image elements do not have `[alt]` attributes that are redundant text.
○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