Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 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-yadrld

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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

Got: https://goodschina.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 ✗

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="email">; <input type="password">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
input	email	(name@company.com)	placeholder only
input	password	(••••••••)	placeholder only

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

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

Link & Button Quality

1 issue(s) across 2 links and 6 buttons

REVIEW

1 issue(s) across 2 links and 6 buttons

2 link(s) open in new tab without warning

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

Got: https://vk.me/goodschina1; https://t.me/GOODSCHINAMR

1 button(s) with no accessible text

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

Got: button.absolute (#47 on page)

2 links

0 empty

0 generic text

2 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://vk.me/goodschina1	ВКонтакте	new tab	Add '(opens in new tab)' to text
https://t.me/GOODSCHINAMR	Telegram	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

5 links and buttons have descriptive text

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

https://vk.me/goodschina1; https://t.me/GOODSCHINAMR

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.absolute (#47 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

Lighthouse Accessibility Audits

Action

Score 75/100 — 3 failing, 10 passed

REVIEW

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.

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
form.p-8 > div > div.relative > button.absolute `form.p-8 > div > div.relative > button.absolute`

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.

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
Проблемы со входом? ВКонтакте · Telegram `div.min-h-screen > div.w-full > div.bg-slate-50 > p.text-xs`
ВКонтакте `div.w-full > div.bg-slate-50 > p.text-xs > a.hover:text-slate-600`
Telegram `div.w-full > div.bg-slate-50 > p.text-xs > a.hover:text-slate-600`

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
form.p-8 > div > div.relative > button.absolute `form.p-8 > div > div.relative > button.absolute`

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-hidden="true"]` is not present on the document `<body>`

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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○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

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

○Identical links have the same purpose.

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

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 С возвращением!

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Color Contrast (Screenshot)

14 text elements analyzed, 0 fail WCAG AA

PASS

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

14 pass

Show all checked elements (14)

Element	Ratio	Required	FG	BG	Result
h1 С возвраще�…	20.07:1	3.0:1	#000000	#F8FAFC	Pass
title GOODS CHINA	20.07:1	4.5:1	#000000	#F8FAFC	Pass
p Войдите, чт…	20.07:1	4.5:1	#000000	#F8FAFC	Pass
button Войти	20.07:1	4.5:1	#000000	#F8FAFC	Pass
button Регистраци…	20.07:1	4.5:1	#000000	#F8FAFC	Pass
label Email	20.07:1	4.5:1	#000000	#F8FAFC	Pass
label Пароль	20.07:1	4.5:1	#000000	#F8FAFC	Pass
button Забыли пар�…	20.07:1	4.5:1	#000000	#F8FAFC	Pass
button Войти в акк…	19.90:1	4.5:1	#000000	#F7F9FB	Pass
p Нет аккаун�…	19.90:1	4.5:1	#000000	#F7F9FB	Pass
button Создать се�…	19.90:1	4.5:1	#000000	#F7F9FB	Pass
p Проблемы с�…	19.90:1	4.5:1	#000000	#F7F9FB	Pass
a ВКонтакте	19.90:1	4.5:1	#000000	#F7F9FB	Pass
a Telegram	19.90:1	4.5:1	#000000	#F7F9FB	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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.