Skip to content
https://techex.com.ua

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
F
Form Accessibility
Action
11 of 11 controls have issues
FIX
11 of 11 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="toggle">; <input type="submit">; <input type="submit">
Warning::
8 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="your-name">; <input type="tel" name="your-phone">; <input type="text" name="your-sender">; <input type="text" name="your-contact">; <input type="text" name="your-name">; <input type="tel" name="your-phone">; <input type="text" name="your-sender">; <input type="text" name="your-contact">
11 controls
0 labeled
8 placeholder only
3 unlabeled
ControlTypeLabelMethod
your-nametext(Ваше ім’я)placeholder only
your-phonetel(Номер телефону)placeholder only
your-sendertext(Від імені кого звертаєтесь?)placeholder only
your-contacttext(Де з вами краще зв’язатись?)placeholder only
your-nametext(Ваше ім’я)placeholder only
your-phonetel(Номер телефону)placeholder only
your-sendertext(Від імені кого звертаєтесь?)placeholder only
your-contacttext(Де з вами краще зв’язатись?)placeholder only
#togglecheckbox(none)none
inputsubmit(none)none
inputsubmit(none)none

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

<input type="checkbox" id="toggle">; <input type="submit">; <input type="submit">

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.

<input type="text" name="your-name">; <input type="tel" name="your-phone">; <input type="text" name="your-sender">; <input type="text" name="your-contact">; <input type="text" name="your-name">; <input type="tel" name="your-phone">; <input type="text" name="your-sender">; <input type="text" name="your-contact">

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

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
Heading Hierarchy
19 headings, 2 skip(s)
REVIEW
19 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Передові безпілотні системи оборони Бачити. Вистежувати. Вражати.
  • H4 Stalker XO-15 MAX skipped
  • H4 Stalker XO-10 MAX
  • H4 Stalker XO-15
  • H4 Stalker XO-10
  • H4 Striker Mini
  • H2 ТехЕкс: Інженерна точність. Масштабне виробництво. Перевірено в бою.
  • H3 Стійкість до РЕБ
  • H3 Рекордно низька вага оптоволоконної котушки
  • H3 Перевірені на полі бою
  • H3 Модифікація під ваш запит
  • H3 Універсальне місце кріплення бойової частини
  • H2 Наша команда об’єднує досвід інженерів, операторів БПЛА та фахівців у сфері оборонних технологій
  • H2 Нам довіряють
  • H2 Новини
  • H5 TechEx на IDEB 2026: БПЛА та протидронові рішення для НАТО skipped
  • H5 TechEx представляє лінійку НАТО-кодифікованих дронів на XPONENTIAL Europe 2026
  • H5 TechEx долучилась до Finland-Ukraine Tech Bridge 2026
  • H2 Зв'яжіться з нами

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

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
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.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) 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::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Бачити. Вистежувати. В…
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
32px · bottom of viewport
h2 ТехЕкс: Інженерна точ…
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Наша команда об’єдну…
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Нам довіряють
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Новини
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Зв'яжіться з нами
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Стійкість до РЕБ
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Рекордно низька вага …
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Перевірені на полі бо…
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Модифікація під ваш з…
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Універсальне місце кр…
1.11:1
#000000
on
#12110F
needs 3.0:1 (large text)
19px · bottom of viewport
title TechEx – український вир…
1.11:1
#000000
on
#12110F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Продукти
1.11:1
#000000
on
#12110F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Переваги
1.11:1
#000000
on
#12110F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Про нас
1.11:1
#000000
on
#12110F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Партнери
1.11:1
#000000
on
#12110F
needs 4.5:1 (normal text)
16px · above the fold
div Клієнтський відділ
1.11:1
#000000
on
#12110F
needs 4.5:1 (normal text)
16px · above the fold
a +38 093 853 00 00
1.11:1
#000000
on
#12110F
needs 4.5:1 (normal text)
16px · above the fold
div Електронна пошта
1.11:1
#000000
on
#12110F
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Передові б…1.11:13.0:1
#000000
#12110F
Fail
h1 Бачити. Вис…1.11:13.0:1
#000000
#12110F
Fail
h2 ТехЕкс: Інж…1.11:13.0:1
#000000
#12110F
Fail
h2 Наша коман…1.11:13.0:1
#000000
#12110F
Fail
h2 Нам довіря…1.11:13.0:1
#000000
#12110F
Fail
h2 Новини1.11:13.0:1
#000000
#12110F
Fail
h2 Зв'яжіться …1.11:13.0:1
#000000
#12110F
Fail
h3 Стійкість …1.11:13.0:1
#000000
#12110F
Fail
h3 Рекордно н…1.11:13.0:1
#000000
#12110F
Fail
h3 Перевірені…1.11:13.0:1
#000000
#12110F
Fail
h3 Модифікаці…1.11:13.0:1
#000000
#12110F
Fail
h3 Універсаль…1.11:13.0:1
#000000
#12110F
Fail
title TechEx – укра…1.11:14.5:1
#000000
#12110F
Fail
a Продукти1.11:14.5:1
#000000
#12110F
Fail
a Переваги1.11:14.5:1
#000000
#12110F
Fail
a Про нас1.11:14.5:1
#000000
#12110F
Fail
a Партнери1.11:14.5:1
#000000
#12110F
Fail
div Клієнтськи…1.11:14.5:1
#000000
#12110F
Fail
a +38 093 853 00 001.11:14.5:1
#000000
#12110F
Fail
div Електронна…1.11:14.5:1
#000000
#12110F
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
6 landmarks
PASS
6 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 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 Text Quality
All 19 heading(s) have substantive, well-formed text
PASS
All 19 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
9 of 88 images have issues
PASS
9 of 88 images have issues
Warning::
9 image(s) with generic alt text
Info::
79 image(s) with good alt text
88 images 79 good alt text 9 generic
IssueCount
generic9 image(s)
A+
Form Input Types
11 form control(s) checked, no type mismatches
PASS
11 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
11 form control(s) checked, no input-semantic issues
PASS
11 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "uk-UA"
PASS
Lang attribute set to "uk-UA"
Info::
<html lang="uk-UA"> is set and valid
Got: uk-UA
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
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+
Mobile-Readable Font Sizes
All 87 visible text node(s) render at >= 12 CSS pixels
PASS
All 87 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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 92/100 — 3 failing, 25 passed
PASS
92

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
15.05.2026 div.news > div.news-item > div.labels > time.label
Новини div.news > div.news-item > div.labels > div.label
27.03.2026 div.news > div.news-item > div.labels > time.label
Новини div.news > div.news-item > div.labels > div.label
19.03.2026 div.news > div.news-item > div.labels > time.label
Новини div.news > div.news-item > div.labels > div.label
+38 067 853 00 00 div.footer-support-messenger > div.contacts-messenger > a > div.contacts-header
+38 099 287 38 96 div.footer-support-messenger > div.contacts-messenger > a > div.contacts-header
+38 067 853 00 00 div.footer-support-messenger > div.contacts-messenger > a > div.contacts-header
+38 099 287 38 96 div.footer-support-messenger > div.contacts-messenger > a > div.contacts-header

These are opportunities to improve the legibility of your content.

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
Stalker XO-15 MAX div.card-slider > div.card > div.card-item > h4
TechEx на IDEB 2026: БПЛА та протидронові рішення для НАТО section.news-section > div.news > div.news-item > h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.footer > div.footer-contacts > div.contacts-social > a div.footer > div.footer-contacts > div.contacts-social > a
div.footer > div.footer-contacts > div.contacts-social > a div.footer > div.footer-contacts > div.contacts-social > a
div.footer > div.footer-contacts > div.contacts-social > a div.footer > div.footer-contacts > div.contacts-social > a
div.footer > div.footer-contacts > div.contacts-social > a div.footer > div.footer-contacts > div.contacts-social > a
div.footer > div.footer-contacts > div.contacts-social > a div.footer > div.footer-contacts > div.contacts-social > a
div.footer > div.footer-contacts > div.contacts-social > a div.footer > div.footer-contacts > div.contacts-social > 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.

○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
●Input buttons have discernible text.
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○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.
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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