Skip to content
https://sbs.army

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
7
REVIEW
3
PASS
14
INFO
0
Checks
24
14 PASS 3 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
6/8 eligible field(s) missing autocomplete or inputmode
FIX
6/8 eligible field(s) missing autocomplete or inputmode
Warning::
4 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: name, email.
Got: <input type="text" name="name" id="name-d9e5eb50-16ee-4f2a-b4a0-e7e8d54762b1">, <input type="text" name="email" id="email">, <input type="text" name="name" id="name-eb5434d1-c5ec-4adf-aaea-9232d3b00647">, <input type="text" name="email" id="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: tel.
Got: <input type="tel" id="phone-31efcbbf-dbf1-4591-b6e7-d0631419044d">, <input type="tel" id="phone-2590fab8-d13a-4559-8787-080b1ad6c4bf">
D
Tabindex Anti-Patterns
Action
0 positive, 16 -1-on-focusable
FIX
0 positive, 16 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <select>
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 <button id="status-civil-9ddbbea4-a187-406b-93d7-2dff9a39cae9">
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 <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.)
Info::
tabindex="-1" on naturally-focusable <button id="status-soldier-9ddbbea4-a187-406b-93d7-2dff9a39cae9">
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 <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.)
Info::
tabindex="-1" on naturally-focusable <button id="status-szch-9ddbbea4-a187-406b-93d7-2dff9a39cae9">
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 <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.)
Info::
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.)
Info::
tabindex="-1" on naturally-focusable <select>
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 <button id="status-civil-b5474c82-0750-44d2-abdc-ecc5bf5c3124">
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 <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.)
Info::
tabindex="-1" on naturally-focusable <button id="status-soldier-b5474c82-0750-44d2-abdc-ecc5bf5c3124">
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 <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.)
Info::
tabindex="-1" on naturally-focusable <button id="status-szch-b5474c82-0750-44d2-abdc-ecc5bf5c3124">
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 <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.)
Info::
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.)
D
Tap Target Adequacy
Action
13 tap target(s) too small or too close together
FIX
13 tap target(s) too small or too close together
Warning::
13 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.
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 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: US Forces
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name US Forces ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name US Forces Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA 6 pass AA only
title Сили безпілотних сист…
3.74:1
#000000
on
#0168C0
needs 4.5:1 (normal text)
16px · top of page (header area)
span Про СБС
4.05:1
#000000
on
#016EC6
needs 4.5:1 (normal text)
16px · top of page (header area)
span Новини
4.45:1
#000000
on
#0176CA
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Обирай з 15 0…8.94:13.0:1
#000000
#56B2E9
Pass
h2 Робота на в…20.57:13.0:1
#000000
#FBFDFD
Pass
h2 СБС здійсн…20.57:13.0:1
#000000
#FBFDFD
Pass
h2 5 підрозділ…20.57:13.0:1
#000000
#FBFDFD
Pass
h2 Ми будуємо …20.57:13.0:1
#000000
#FBFDFD
Pass
h2 Вакансії, я…20.57:13.0:1
#000000
#FBFDFD
Pass
h2 Підрозділи…20.57:13.0:1
#000000
#FBFDFD
Pass
h2 Контракт 18-…20.57:13.0:1
#000000
#FBFDFD
Pass
h2 Так вигляд…20.57:13.0:1
#000000
#FBFDFD
Pass
h2 Запитання …20.57:13.0:1
#000000
#FBFDFD
Pass
h2 Приєднуйся…20.57:13.0:1
#000000
#FBFDFD
Pass
title Сили безпі…3.74:14.5:1
#000000
#0168C0
Fail
span Про СБС4.05:14.5:1
#000000
#016EC6
Fail
span Новини4.45:14.5:1
#000000
#0176CA
Fail
span Вакансії4.77:14.5:1
#000000
#047CCD
Pass
span Підрозділи4.89:14.5:1
#000000
#027ECF
Pass
span Підготовка5.54:14.5:1
#000000
#0289D5
Pass
span Рекрутинг6.03:14.5:1
#000000
#0291D7
Pass
span Контракт 18-…5.93:14.5:1
#000000
#038FD9
Pass
span Eng6.33:14.5:1
#000000
#0495DB
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
Landmark Structure
15 landmarks
PASS
15 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" 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 Hierarchy
20 headings
PASS
20 headings
Info::
Single H1 present
  • H1 Обирай з 15 000 вакансій у Силах безпілотних систем
  • H2 Робота на відстані та суворі протоколи безпеки зводять людські втрати в СБС до мінімуму.
  • H2 СБС здійснює понад 35% від усіх верифікованих уражень Сил оборони України. Кожен третій ворог — знищений СБС.
  • H2 5 підрозділів Угруповання СБС стабільно у топ-10 найефективніших БпЛА підрозділів Сил оборони України.
  • H2 Ми будуємо системне військо сучасності
  • H2 Вакансії, які можуть тебе зацікавити
  • H2 Підрозділи в системі СБС
  • H2 Контракт 18-24: Дрони
  • H2 Так виглядатиме твій шлях до Сил безпілотних систем.
  • H2 Запитання та відповіді
  • H3 Як я можу бути впевненим, що потраплю до СБС?
  • H3 Чи можу я обрати підрозділ або спеціальність під час вступу?
  • H3 Які мінімальні вимоги для вступу в СБС?
  • H3 Чи приймаєте ви жінок? Які для них є напрямки служби?
  • H3 Чи пройду я БЗВП, якщо у мене посередня фізична підготовка?
  • H3 Які етапи вступу для офіцерів запасу?
  • H3 Я в статусі СЗЧ — як мені долучитись до СБС?
  • H3 Чи приймаєте ви військових за переведенням і що для цього потрібно?
  • H3 Чи можна перевестися з ДПСУ, НГУ, ДССТ? Як щодо прикордонників у статусі СЗЧ?
  • H2 Приєднуйся зараз
A+
Heading Text Quality
All 20 heading(s) have substantive, well-formed text
PASS
All 20 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 49 images OK
PASS
All 49 images OK
Info::
28 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
49 images 21 good alt text 28 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 10 controls labeled
PASS
All 10 controls labeled
Info::
10 control(s) properly labeled
10 controls
10 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#name-d9e5eb50-16ee-4f2a-b4a0-e7e8d54762b1textІмʼя(required)for/id
#surname-44cb69e0-1b71-427c-925e-d6b55c3fa214textПрізвище(required)for/id
selectselectCountryaria-label
#phone-31efcbbf-dbf1-4591-b6e7-d0631419044dtelНомер телефону* (required)for/id
#emailtext(required)for/id
#name-eb5434d1-c5ec-4adf-aaea-9232d3b00647textІмʼя(required)for/id
#surname-9264d8ea-1792-461d-ba79-f6dbe440cc3btextПрізвище(required)for/id
selectselectCountryaria-label
#phone-2590fab8-d13a-4559-8787-080b1ad6c4bftelНомер телефону* (required)for/id
#emailtext(required)for/id
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
10 form control(s) checked, no input-semantic issues
PASS
10 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "uk"
PASS
Lang attribute set to "uk"
Info::
<html lang="uk"> is set and valid
Got: uk
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 150 visible text node(s) render at >= 12 CSS pixels
PASS
All 150 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
Favicon & Branding
7 icon(s) detected
PASS
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
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 93/100 — 2 failing, 25 passed
PASS
93

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
Крок 1 div.relative > div.flex > div.relative > span.inline-block
Крок 2 div.relative > div.flex > div.relative > span.inline-block
Крок 3 div.relative > div.flex > div.relative > span.inline-block
Крок 4 div.relative > div.flex > div.relative > span.inline-block
Крок 5 div.relative > div.flex > div.relative > span.inline-block
Крок 6 div.relative > div.flex > div.relative > span.inline-block

These are opportunities to improve the legibility of your content.

Best practices

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
Instagram ↘ div.grid > div.grid > div.flex > a.text-white/90
Telegram ↘ div.grid > div.grid > div.flex > a.text-white/90
YouTube ↘ div.grid > div.grid > div.flex > a.text-white/90
TikTok ↘ div.grid > div.grid > div.flex > a.text-white/90
Facebook ↘ div.grid > div.grid > div.flex > a.text-white/90
X ↘ div.grid > div.grid > div.flex > a.text-white/90
Про СБС div.grid > div.grid > div.flex > a.text-white/90
Новини div.grid > div.grid > div.flex > a.text-white/90
Вакансії div.grid > div.grid > div.flex > a.text-white/90
Підрозділи div.grid > div.grid > div.flex > a.text-white/90
Підготовка div.grid > div.grid > div.flex > a.text-white/90
Рекрутинг div.grid > div.grid > div.flex > a.text-white/90
Контракт 18-24 div.grid > div.grid > div.flex > a.text-white/90

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>`
●`[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
●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.
●Select elements have associated label elements.
●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
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○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