Skip to content
https://ukrspecsystems.ua

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
4
REVIEW
8
PASS
12
INFO
0
Checks
24
12 PASS 8 REVIEW 4 FIX
D
Mobile Keyboard & Autofill
Action
4/4 eligible field(s) missing autocomplete or inputmode
FIX
4/4 eligible field(s) missing autocomplete or inputmode
Warning::
2 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" id="64ff0e2752fab600160fffd6-contactForm_email">, <input type="email" id="64ff0e2752fab600160fffd6-contactForm_email">
Warning::
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: email.
Got: <input type="email" id="64ff0e2752fab600160fffd6-contactForm_email">, <input type="email" id="64ff0e2752fab600160fffd6-contactForm_email">
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
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::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
14 landmarks
REVIEW
14 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
6 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 navigation menu" MAIN (missing!) CONTENTINFO footer

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

B
Heading Hierarchy
12 headings
REVIEW
12 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Designed to excel, built to endure_
  • H2 MEET THE NEW UAS SHARK-M
  • H2 MEET THE NEW UAS SHARK-M
  • H2 What we offer
  • H2 Proud to be trusted by our users
  • H2 Customer voices
  • H2 News & blog
  • H2 UKRSPECSYSTEMS Unveils Combat-Proven RAM-2X for the First Time at MSPO 2026
  • H2 UMEX2026 in Abu Dhabi is complete!
  • H2 Exclusive Interview with Rory Chamberlain, Director of Ukrspecsystems UK, for Militarnyi
  • H2 Contact us
  • H3 We’re always glad to answer your questions!

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" id="64ff0e2752fab600160fffd6-contactForm_email">; <input type="email" id="64ff0e2752fab600160fffd6-contactForm_email">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#64ff0e2752fab600160fffd6-contactForm_emailemail(Email*)placeholder only
#64ff0e2752fab600160fffd6-contactForm_emailemail(Email*)placeholder only

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

<input type="email" id="64ff0e2752fab600160fffd6-contactForm_email">; <input type="email" id="64ff0e2752fab600160fffd6-contactForm_email">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Looks like this page does not exist yet ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light only
Info::
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: #00a0db
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta light only ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
title UKRSPECSYSTEMS
1.86:1
#000000
on
#373B3D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Get in touch with us
1.72:1
#000000
on
#323639
needs 4.5:1 (normal text)
16px · top of page (header area)
span +38 (063) 834-36-60
1.77:1
#000000
on
#34383B
needs 4.5:1 (normal text)
16px · top of page (header area)
span info@ukrspecsystems.com
1.75:1
#000000
on
#333739
needs 4.5:1 (normal text)
16px · top of page (header area)
span 56de1e2a-96ca-48a0-b1f0-85f62fa512e9
1.89:1
#000000
on
#393C3E
needs 4.5:1 (normal text)
16px · above the fold
span 3c3fb111-4faf-4b4e-8b0a-7449f0d43a8d
2.25:1
#000000
on
#454747
needs 4.5:1 (normal text)
16px · above the fold
span f7c27a87-f0f8-4ea4-bcc7-becf8c37269e
2.01:1
#000000
on
#3E4041
needs 4.5:1 (normal text)
16px · above the fold
span 69a11167-5731-47eb-b719-3a83423e0a1d
1.29:1
#000000
on
#1F2022
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span 7edf60b9-f9ab-411e-ac00-7e392d675131
1.16:1
#000000
on
#151617
needs 4.5:1 (normal text)
16px · above the fold
a Drones
1.23:1
#000000
on
#191C1F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a PD-2 UAS
1.57:1
#000000
on
#2A3034
needs 4.5:1 (normal text)
16px · above the fold
a SHARK-D UAS
1.56:1
#000000
on
#293033
needs 4.5:1 (normal text)
16px · above the fold
a SHARK-M UAS
1.51:1
#000000
on
#272D31
needs 4.5:1 (normal text)
16px · above the fold
a MINI SHARK UAS
1.48:1
#000000
on
#252C30
needs 4.5:1 (normal text)
16px · mid-page
a Gimbals
1.53:1
#000000
on
#282E31
needs 4.5:1 (normal text)
16px · mid-page
a USG-232 EO/IR/LRF
1.59:1
#000000
on
#2C3133
needs 4.5:1 (normal text)
16px · mid-page
a USG-405 EO/IR/LRF
1.64:1
#000000
on
#2F3334
needs 4.5:1 (normal text)
16px · mid-page

2 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 UKRSPECSYSTEMS1.86:14.5:1
#000000
#373B3D
Fail
span Get in touch with us1.72:14.5:1
#000000
#323639
Fail
span +38 (063) 834-36-601.77:14.5:1
#000000
#34383B
Fail
span info@ukrspecsystems.…1.75:14.5:1
#000000
#333739
Fail
span 56de1e2a-96ca-48a0-b…1.89:14.5:1
#000000
#393C3E
Fail
span 3c3fb111-4faf-4b4e-8…2.25:14.5:1
#000000
#454747
Fail
span f7c27a87-f0f8-4ea4-b…2.01:14.5:1
#000000
#3E4041
Fail
span 69a11167-5731-47eb-b…1.29:14.5:1
#000000
#1F2022
Fail
span 7edf60b9-f9ab-411e-a…1.16:14.5:1
#000000
#151617
Fail
a Drones1.23:14.5:1
#000000
#191C1F
Fail
a PD-2 UAS1.57:14.5:1
#000000
#2A3034
Fail
a SHARK-D UAS1.56:14.5:1
#000000
#293033
Fail
a SHARK-M UAS1.51:14.5:1
#000000
#272D31
Fail
a MINI SHARK UAS1.48:14.5:1
#000000
#252C30
Fail
a Gimbals1.53:14.5:1
#000000
#282E31
Fail
a USG-232 EO/IR/LRF1.59:14.5:1
#000000
#2C3133
Fail
a USG-405 EO/IR/LRF1.64:14.5:1
#000000
#2F3334
Fail
a USG-231 EO19.57:14.5:1
#000000
#F5F7FA
Pass
a USG-231T IR19.57:14.5:1
#000000
#F5F7FA
Pass
a USG-261 EO19.57:14.5:1
#000000
#F5F7FA
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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
2 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 2 all-caps heading(s)
A
Alt Text Quality
25 of 29 images have issues
PASS
25 of 29 images have issues
Warning::
25 image(s) with generic alt text
Info::
4 image(s) with good alt text
29 images 4 good alt text 25 generic
IssueCount
generic25 image(s)
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A
Tabindex Anti-Patterns
0 positive, 2 -1-on-focusable
PASS
0 positive, 2 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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 2 iframe(s) have descriptive titles
PASS
All 2 iframe(s) have descriptive titles
Info::
All 2 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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 72 visible text node(s) render at >= 12 CSS pixels
PASS
All 72 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Service worker registration detected
The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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 90/100 — 4 failing, 25 passed
PASS
90

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Video div.w-grid__item > div.w-grid__item-inner > div.w-picture-wrapper > div.w-picture
Video div.composition-wrapper_3ss > div.tablet-wrapper_H7w > div.picture-wrapper_1xA > div.picture_SAz

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.w-76f2b59143165ef59ef8258211870beb > div.server-render__collection-arrows_2Dv > div.server-render__collection-arrow_1yu > button.w-slider-arrow div.w-76f2b59143165ef59ef8258211870beb > div.server-render__collection-arrows_2Dv > div.server-render__collection-arrow_1yu > button.w-slider-arrow
div.w-76f2b59143165ef59ef8258211870beb > div.server-render__collection-arrows_2Dv > div.server-render__collection-arrow_1yu > button.w-slider-arrow div.w-76f2b59143165ef59ef8258211870beb > div.server-render__collection-arrows_2Dv > div.server-render__collection-arrow_1yu > button.w-slider-arrow

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

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.site-root html.site-root

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
Learn more div.w-grid__item-inner > div.w-btns-group > div.w-btns-group__inner > a.w-btns-group__item
Learn more div.w-grid__item-inner > div.w-btns-group > div.w-btns-group__inner > a.w-btns-group__item
Learn more div.w-grid__item-inner > div.w-btns-group > div.w-btns-group__inner > a.w-btns-group__item
Learn more div.w-grid__item-inner > div.w-btns-group > div.w-btns-group__inner > a.w-btns-group__item
Watch div.w-grid__item-inner > div.w-btns-group > div.w-btns-group__inner > a.w-btns-group__item
Read more news div.w-grid__item-inner > div.w-btns-group > div.w-btns-group__inner > a.w-btns-group__item
○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
●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
●Background and foreground colors have a sufficient contrast ratio
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●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
○`<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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback