Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-54yqjr

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://ark-russia.ru/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://ark-russia.ru/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Link & Button Quality

Action

3 issue(s) across 52 links and 6 buttons

REVIEW

3 issue(s) across 52 links and 6 buttons

6 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://discord.gg/VpvCFyE; https://vk.com/ark.russia; https://t.me/arksrussia; https://discord.gg/VpvCFyE; https://t.me/arksrussia; https://vk.com/ark.russia

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.px-4 (#386 on page); button.px-4 (#433 on page); button.px-4 (#473 on page)

46 link(s) with descriptive text

52 links

0 empty

0 generic text

6 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://discord.gg/VpvCFyE	Вступить в Discord	new tab	Add '(opens in new tab)' to text
https://vk.com/ark.russia	VKВступить в груп…	new tab	Add '(opens in new tab)' to text
https://t.me/arksrussia	Telegram-канал	new tab	Add '(opens in new tab)' to text
https://discord.gg/VpvCFyE	Discord	new tab	Add '(opens in new tab)' to text
https://t.me/arksrussia	Telegram	new tab	Add '(opens in new tab)' to text
https://vk.com/ark.russia	VK	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

49 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://discord.gg/VpvCFyE; https://vk.com/ark.russia; https://t.me/arksrussia; https://discord.gg/VpvCFyE; https://t.me/arksrussia; https://vk.com/ark.russia

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.px-4 (#386 on page); button.px-4 (#433 on page); button.px-4 (#473 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (9 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (9 below threshold)

9 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: <span> 11.0px ("Evolved"); <span> 11.0px ("Текстовый гайд"); <span> 11.0px ("Evolved"); <span> 11.0px ("Текстовый гайд"); <span> 11.0px ("Evolved").

Favicon & Branding

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA 1 pass AA only

h2 Последние новости

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Наши сервера ARK

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Популярные гайды

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Популярное за неделю

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Присоединяйся к комью…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Новое событие в ARK: что…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Лучшие динозавры для �…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Как выбрать PvE или PvP с�…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ARK RU Official #1

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ARK PvP Arena

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ARK Modded Paradise

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Как быстро начать игр�…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Как приручить первого…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Как выжить на PvP серве�…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Как выбрать PvE или PvP с�…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Лучшие динозавры для �…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Новое событие в ARK: что…

1.10:1

#000000

#0B0F1A

needs 3.0:1 (large text)

19px · bottom of viewport

title ARK - RUSSIA: русская вики, �…

1.09:1

#000000

#0A0D1A

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 ARK: Survival Evolve…	4.92:1	3.0:1	#000000	#817974	Pass
h2 База знани�…	3.18:1	3.0:1	#000000	#5E5D56	Pass
h2 Последние �…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h2 Наши серве�…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h2 Популярные…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h2 Популярное…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h2 Присоединя…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 Новое собы�…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 Лучшие дин�…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 Как выбрат�…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 ARK RU Official #1	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 ARK PvP Arena	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 ARK Modded Paradise	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 Как быстро …	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 Как прируч�…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 Как выжить …	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 Как выбрат�…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 Лучшие дин�…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
h3 Новое собы�…	1.10:1	3.0:1	#000000	#0B0F1A	Fail
title ARK - RUSSIA: рус…	1.09:1	4.5:1	#000000	#0A0D1A	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

Heading Hierarchy

22 headings, 1 skip(s)

PASS

22 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 ARK: Survival Evolved — новости, гайды и лучшие сервера
H2 База знаний
H2 Последние новости
H3 Новое событие в ARK: что изменилось на серверах
H3 Лучшие динозавры для старта в ARK
H3 Как выбрать PvE или PvP сервер
H2 Наши сервера ARK
H3 ARK RU Official #1
H3 ARK PvP Arena
H3 ARK Modded Paradise
H2 Популярные гайды
H3 Как быстро начать играть в ARK
H3 Как приручить первого динозавра
H3 Как выжить на PvP сервере
H2 Популярное за неделю
H3 Как выбрать PvE или PvP сервер
H3 Лучшие динозавры для старта в ARK
H3 Новое событие в ARK: что изменилось на серверах
H2 Присоединяйся к комьюнити
H4 Навигация skipped
H4 Информация
H4 Комьюнити

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

A+

Heading Text Quality

All 22 heading(s) have substantive, well-formed text

PASS

All 22 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

10 image(s) with good alt text

10 images 10 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input>

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	input	(Поиск по вики, существам, картам и предметам...)	placeholder only

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

<input>

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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "ru"

PASS

Lang attribute set to "ru"

<html lang="ru"> is set and valid

Got: ru

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 21 passed

PASS

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
© 2026 ARK - RUSSIA `div.container > div.ark-footer-bottom > div.flex > p.text-xs`
ARK: Survival Evolved является зарегистрированной торговой маркой Studio Wildca… `footer.ark-footer > div.container > div.ark-footer-bottom > p.text-xs`

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
НАВИГАЦИЯ `div.container > div.grid > div.md:col-span-3 > h4.ark-footer-group-title`

These are opportunities to improve keyboard navigation in your application.

○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

●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

●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

●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.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[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

○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.

○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.