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

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
5
REVIEW
3
PASS
16
INFO
0
Checks
24
16 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 508, bare page
FIX
HTTP 508, bare page
Warning::
Unexpected status code: HTTP 508
Expected HTTP 404 but received 508. This may confuse search engine crawlers.
Got: HTTP 508
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 508 ✗Page Title 508 Resource Limit Is Reached ✓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::
3 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 3 <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
Mobile-Readable Font Sizes
96% of visible text renders at >= 12 CSS px (4 below threshold)
REVIEW
96% of visible text renders at >= 12 CSS px (4 below threshold)
Info::
4 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <small> 10.0px ("Тактичний ігровий портал"); <small> 10.0px ("Тактичний ігровий портал"); <span> 11.0px ("© StrategyHub.com.ua"); <span> 11.0px ("Створено для тих, хто любить думати на к...").
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 Все про RTS, Grand Strategy та …
1.07:1
#000000
on
#070B13
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Знайти матеріал
1.07:1
#000000
on
#070B12
needs 3.0:1 (large text)
24px · mid-page
h2 Останні новини
1.07:1
#000000
on
#070B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Нові огляди
1.07:1
#000000
on
#070B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Останні гайди та такт…
1.07:1
#000000
on
#070B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Авторські добірки та …
1.07:1
#000000
on
#070B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Український портал пр…
1.07:1
#000000
on
#070B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Категорії
1.07:1
#000000
on
#070B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Сторінки
1.07:1
#000000
on
#070B13
needs 3.0:1 (large text)
24px · bottom of viewport
title StrategyHub — новини, огляд…
1.07:1
#000000
on
#080C14
needs 4.5:1 (normal text)
16px · top of page (header area)
a Перейти до основного …
1.07:1
#000000
on
#080C14
needs 4.5:1 (normal text)
16px · top of page (header area)
span ♞
1.07:1
#000000
on
#070B13
needs 4.5:1 (normal text)
16px · top of page (header area)
strong Strategy
1.07:1
#000000
on
#070B13
needs 3.0:1 (large text)
16px · top of page (header area)
span Hub
1.07:1
#000000
on
#070B12
needs 4.5:1 (normal text)
16px · above the fold
small Тактичний ігровий пор…
1.07:1
#000000
on
#070B12
needs 4.5:1 (normal text)
16px · above the fold
a Головна
1.07:1
#000000
on
#070B12
needs 4.5:1 (normal text)
16px · above the fold
a Новини
1.07:1
#000000
on
#070B12
needs 4.5:1 (normal text)
16px · above the fold
a Гайди
1.07:1
#000000
on
#070B12
needs 4.5:1 (normal text)
16px · above the fold
a Ігри
1.07:1
#000000
on
#070B12
needs 4.5:1 (normal text)
16px · above the fold
a Топи та добірки
1.07:1
#000000
on
#070B12
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Все про RTS, G…1.07:13.0:1
#000000
#070B13
Fail
h2 Знайти мат…1.07:13.0:1
#000000
#070B12
Fail
h2 Останні но…1.07:13.0:1
#000000
#070B13
Fail
h2 Нові огляд…1.07:13.0:1
#000000
#070B13
Fail
h2 Останні га…1.07:13.0:1
#000000
#070B13
Fail
h2 Авторські …1.07:13.0:1
#000000
#070B13
Fail
h2 Українськи…1.07:13.0:1
#000000
#070B13
Fail
h2 Категорії1.07:13.0:1
#000000
#070B13
Fail
h2 Сторінки1.07:13.0:1
#000000
#070B13
Fail
title StrategyHub — но…1.07:14.5:1
#000000
#080C14
Fail
a Перейти до …1.07:14.5:1
#000000
#080C14
Fail
span ♞1.07:14.5:1
#000000
#070B13
Fail
strong Strategy1.07:13.0:1
#000000
#070B13
Fail
span Hub1.07:14.5:1
#000000
#070B12
Fail
small Тактичний …1.07:14.5:1
#000000
#070B12
Fail
a Головна1.07:14.5:1
#000000
#070B12
Fail
a Новини1.07:14.5:1
#000000
#070B12
Fail
a Гайди1.07:14.5:1
#000000
#070B12
Fail
a Ігри1.07:14.5:1
#000000
#070B12
Fail
a Топи та доб…1.07:14.5:1
#000000
#070B12
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::
3 <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 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
28 headings
PASS
28 headings
Info::
Single H1 present
  • H2 Знайти матеріал
  • H1 Все про RTS, Grand Strategy та тактичні ігри. Аналізуй. Плануй. Перемагай.
  • H2 Останні новини
  • H3 Victoria 3: State and Revolution — доповнення про Російську імперію вже вийшло
  • H3 Age of Wonders 4 отримує доповнення The Silver Seas: вихід сьогодні, 3 листопада
  • H3 Manor Lords отримала оновлення 0.8.117: фермерство стало глибшим
  • H3 Olden Era отримала патч 0.82.06: нова формула шкоди, сильніший ШІ та ребаланс фракцій
  • H3 Hearts of Iron IV отримала патч 1.19.4: торгівля, інтерфейс і баланс
  • H3 Warhammer 40,000: Dawn of War IV показала понад 70 місій у трейлері Game Overview
  • H2 Священна Римська імперія в Europa Universalis V: князі, імператор і реформи
  • H2 Нові огляди
  • H3 Company of Heroes 3: Final Stand — огляд режиму виживання
  • H3 Traits and Some Magic для Becastled: як нові риси змінюють гру
  • H3 StarCraft II: огляд легендарної космічної стратегії
  • H2 Останні гайди та тактики
  • H3 Civilization VII українською: чи є мова в грі та як встановити українізатор
  • H3 Як змінити Factory і Starport місцями під Reactor у StarCraft II
  • H3 Спорядження лорда у Total War: Warhammer III: як вибрати найкращі предмети
  • H3 Як використовувати ядра у Frostpunk 2: де знайти та на що витрачати
  • H3 Як перемогти кризу Кінця Часів у Total War: Warhammer III
  • H3 Найкращі реформи в Europa Universalis V: що обрати для своєї держави
  • H2 Авторські добірки та топи
  • H3 Найкращі містобудівні стратегії 2026 року: топ-10 ігор про будівництво міст
  • H3 Найочікуваніші стратегії 2026–2027 років: топ-10 ігор, які варто чекати
  • H3 Топ-10 найкращих RTS-ігор 2026 року
  • H2 Український портал про стратегічні відеоігри. Тактика. Геймплей.
  • H2 Категорії
  • H2 Сторінки
A+
Heading Text Quality
All 28 heading(s) have substantive, well-formed text
PASS
All 28 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
All 20 images OK
PASS
All 20 images OK
Info::
4 image(s) with alt text over 125 characters
Info::
16 image(s) with good alt text
20 images 16 good alt text
IssueCount
too long4 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#sht-live-searchsearchПошуковий запитfor/id
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 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"
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
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 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+
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 100/100 — 1 failing, 22 passed
PASS
100

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.

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
♞ StrategyHub Тактичний ігровий портал header.sht-header > div.sht-container > div.sht-brand > a.sht-brand-link
○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>`
●`[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.
●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
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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.
○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.
○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