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 6 REVIEW 4 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

Got: https://vkontakte.ru/manifest.json

Manifest contains invalid JSON.

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 ✗

Heading Hierarchy

1 headings

REVIEW

1 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Sign in to VK

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Link & Button Quality

1 issue(s) across 8 links and 4 buttons

REVIEW

1 issue(s) across 8 links and 4 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://id.vk.com/about/faq/users/registration_and_login/login/QR/20313 ("Learn more")

6 link(s) open in new tab without warning

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

Got: https://id.vk.com/about/faq/users/registration_and_login/login?utm_source=aut…; /about; /terms; https://id.vk.com/about/id; https://ads.vk.com/promo/firstbonus; https://dev.vk.com/

1 link(s) with descriptive text

8 links

0 empty

1 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://id.vk.com/about/faq/users/regist…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: 20313
https://id.vk.com/about/faq/users/regist…	Help	new tab	Add '(opens in new tab)' to text
/about	VK © 2006–2026	new tab	Add '(opens in new tab)' to text
/terms	Terms	new tab	Add '(opens in new tab)' to text
https://id.vk.com/about/id	Learn more about VK ID	new tab	Add '(opens in new tab)' to text
https://ads.vk.com/promo/firstbonus	VK Ads	new tab	Add '(opens in new tab)' to text
https://dev.vk.com/	Developers	new tab	Add '(opens in new tab)' to text

5 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://id.vk.com/about/faq/users/registration_and_login/login/QR/20313 ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://id.vk.com/about/faq/users/registration_and_login/login?utm_source=aut…; /about; /terms; https://id.vk.com/about/id; https://ads.vk.com/promo/firstbonus; https://dev.vk.com/

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

19 text elements analyzed, 0 fail WCAG AA

REVIEW

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

19 pass 15 pass AA only

Show all checked elements (19)

Element	Ratio	Required	FG	BG	Result
h2 Sign in to VK	6.42:1	3.0:1	#000000	#368FF6	Pass
title VK \| Welcome!	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Загружаетс…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Go up	10.96:1	4.5:1	#000000	#8EBFF8	Pass
label Search VK	6.69:1	4.5:1	#000000	#3F93F4	Pass
span Очистить	6.61:1	4.5:1	#000000	#3C92F4	Pass
span Create business page	6.54:1	4.5:1	#000000	#3991F5	Pass
span Scan the QR code wi…	6.34:1	4.5:1	#000000	#338EF6	Pass
span Learn more	6.22:1	4.5:1	#000000	#308CF7	Pass
span Other sign-in option…	6.15:1	4.5:1	#000000	#2D8BF7	Pass
span Sign up	6.08:1	4.5:1	#000000	#2A8AF7	Pass
span Help	5.96:1	4.5:1	#000000	#2788F8	Pass
a VK © 2006–2026	5.90:1	4.5:1	#000000	#2487F8	Pass
div Information about c…	5.84:1	4.5:1	#000000	#2186F9	Pass
a Terms	6.52:1	4.5:1	#000000	#3490FA	Pass
a Learn more about VK…	5.68:1	4.5:1	#000000	#1C83FA	Pass
a VK Ads	5.61:1	4.5:1	#000000	#1982FA	Pass
a Developers	5.57:1	4.5:1	#000000	#1681FB	Pass
span English	5.46:1	4.5:1	#000000	#137FFB	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.

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 20 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.

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
Sign in `form.vkui--vkAccessibility--light > button.vkuiInternalTappable > span.vkuiButton__in > span.vkuiButton__content`
By pressing Sign in, you agree to the Terms of Service and Privacy Policy `div.vkitPageWrapper__after--r61ue > div.vkitPageWrapper__container--lzy2M > div > span.Policies__root--MitF1`
Help `div.IndexMobile__footer--Zb8QE > div.vkuiFlex__host > a.vkitLink__link--b0dQw > span.vkuiSubhead__host`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms of Service `div.vkitPageWrapper__container--lzy2M > div > span.Policies__root--MitF1 > a.vkitLink__link--b0dQw`
Privacy Policy `div.vkitPageWrapper__container--lzy2M > div > span.Policies__root--MitF1 > a.vkitLink__link--b0dQw`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●Form elements have associated labels

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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○Heading elements appear in a sequentially-descending order

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

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

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-:r0:	search	Search VK	for/id

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta light ✓Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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