Skip to content
https://firepoint.technology

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
5
REVIEW
4
PASS
15
INFO
0
Checks
24
15 PASS 4 REVIEW 5 FIX
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::
7 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 7 <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.
B
Heading Hierarchy
7 headings, 2 skip(s)
REVIEW
7 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 QUIS NISI NOS
  • H3 хто, як не ми skipped
  • H2 FIRE POINT
  • H2 МЕДІА ПРО НАС
  • H4 Fire Point на DALO Industry Days 2026 skipped
  • H4 Fire Point виступає архітектором нової пан-європейської системи протиракетної оборони FREYJA
  • H4 Fire Point та HENSOLDT підписали угоду про співпрацю

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, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA
title Fire Point
1.50:1
#000000
on
#162D48
needs 4.5:1 (normal text)
16px · top of page (header area)
a Головна
1.61:1
#000000
on
#18324E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Про нас
1.69:1
#000000
on
#193652
needs 4.5:1 (normal text)
16px · top of page (header area)
a Вражаємо
1.70:1
#000000
on
#1B3654
needs 4.5:1 (normal text)
16px · top of page (header area)
a Продукти
1.46:1
#000000
on
#152B45
needs 4.5:1 (normal text)
16px · above the fold
a Новини
1.53:1
#000000
on
#1A2E4A
needs 4.5:1 (normal text)
16px · above the fold
a Контакти
1.40:1
#000000
on
#142742
needs 4.5:1 (normal text)
16px · above the fold
div ПРОДУКТИ
1.43:1
#000000
on
#152943
needs 4.5:1 (normal text)
16px · above the fold
a БпЛА СИСТЕМИ FP-1 / FP-2
1.29:1
#000000
on
#112038
needs 4.5:1 (normal text)
16px · above the fold
a БпЛА СИСТЕМА FP-5 "ФЛАМІ…
1.27:1
#000000
on
#101F35
needs 4.5:1 (normal text)
16px · above the fold
a БАЛІСТИЧНА РАКЕТА FP-7
1.27:1
#000000
on
#111F36
needs 4.5:1 (normal text)
16px · above the fold
a БАЛІСТИЧНА РАКЕТА FP-9
1.43:1
#000000
on
#162943
needs 4.5:1 (normal text)
16px · above the fold
p Ударні БпЛА у модифік…
1.50:1
#000000
on
#172D47
needs 4.5:1 (normal text)
16px · above the fold
p Сучасна безпілотна ав…
1.31:1
#000000
on
#11223A
needs 4.5:1 (normal text)
16px · mid-page
p Балістична ракета, пр…
1.32:1
#000000
on
#13223B
needs 4.5:1 (normal text)
16px · mid-page
p Балістична ракета, пр…
1.30:1
#000000
on
#12213A
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 QUIS19.09:13.0:1
#000000
#F4F4F4
Pass
h1 NISI NOS19.09:13.0:1
#000000
#F4F4F4
Pass
h2 FIRE POINT19.09:13.0:1
#000000
#F4F4F4
Pass
h2 МЕДІА ПРО Н…19.09:13.0:1
#000000
#F4F4F4
Pass
title Fire Point1.50:14.5:1
#000000
#162D48
Fail
a Головна1.61:14.5:1
#000000
#18324E
Fail
a Про нас1.69:14.5:1
#000000
#193652
Fail
a Вражаємо1.70:14.5:1
#000000
#1B3654
Fail
a Продукти1.46:14.5:1
#000000
#152B45
Fail
a Новини1.53:14.5:1
#000000
#1A2E4A
Fail
a Контакти1.40:14.5:1
#000000
#142742
Fail
div ПРОДУКТИ1.43:14.5:1
#000000
#152943
Fail
a БпЛА СИСТЕ…1.29:14.5:1
#000000
#112038
Fail
a БпЛА СИСТЕ…1.27:14.5:1
#000000
#101F35
Fail
a БАЛІСТИЧНА…1.27:14.5:1
#000000
#111F36
Fail
a БАЛІСТИЧНА…1.43:14.5:1
#000000
#162943
Fail
p Ударні БпЛ…1.50:14.5:1
#000000
#172D47
Fail
p Сучасна бе…1.31:14.5:1
#000000
#11223A
Fail
p Балістична…1.32:14.5:1
#000000
#13223B
Fail
p Балістична…1.30:14.5:1
#000000
#12213A
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
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
7 <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 "Primary navigation" 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
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 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: 3 all-caps heading(s)
A+
Alt Text Quality
All 12 images OK
PASS
All 12 images OK
Info::
11 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
12 images 1 good alt text 11 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
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+
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 44 visible text node(s) render at >= 12 CSS pixels
PASS
All 44 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 94/100 — 2 failing, 24 passed
PASS
94

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.

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
хто, як не ми section.firepoint-hero > div.firepoint-hero__content > div.firepoint-hero__title > h3
Fire Point на DALO Industry Days 2026 article.fp-blogs__item > div.fp-blogs__content > div > h4.fp-blogs__heading

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
header.header > div.header__menus > div.u-flex > a.header__logo header.header > div.header__menus > div.u-flex > a.header__logo
body.home > div#sideNav > div.mobile-titles > a.header__logo body.home > div#sideNav > div.mobile-titles > a.header__logo
div.u-container > div.fp-blogs__grid > article.fp-blogs__item > a.fp-blogs__image-link div.u-container > div.fp-blogs__grid > article.fp-blogs__item > a.fp-blogs__image-link
div.u-container > div.fp-blogs__grid > article.fp-blogs__item > a.fp-blogs__image-link div.u-container > div.fp-blogs__grid > article.fp-blogs__item > a.fp-blogs__image-link
div.u-container > div.fp-blogs__grid > article.fp-blogs__item > a.fp-blogs__image-link div.u-container > div.fp-blogs__grid > article.fp-blogs__item > a.fp-blogs__image-link

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
●`[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
●Background and foreground colors have a sufficient contrast ratio
●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>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○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.
○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