Skip to content
https://kp.ru

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
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 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
1 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 1 <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.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 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 1 fail WCAG AA 4 pass AA only
a Здоровье
4.15:1
#000000
on
#5D69B5
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Новости17.24:13.0:1
#000000
#E7E9EA
Pass
h3 Ваш регион…17.24:13.0:1
#000000
#E7E9EA
Pass
title Новости Ро…21.00:14.5:1
#000000
#FFFFFF
Pass
button Меню19.87:14.5:1
#000000
#F7F9F9
Pass
div Россия18.18:14.5:1
#000000
#ECEFF1
Pass
a Фото18.18:14.5:1
#000000
#ECEFF1
Pass
a Видео8.90:14.5:1
#000000
#98A8D5
Pass
a Спецоперац…8.46:14.5:1
#000000
#8FA4D7
Pass
a Политика5.36:14.5:1
#000000
#667DCB
Pass
a Общество5.79:14.5:1
#000000
#7083CA
Pass
a Экономика5.37:14.5:1
#000000
#697DC8
Pass
a В мире4.98:14.5:1
#000000
#6677C2
Pass
a Звезды7.10:14.5:1
#000000
#8694CA
Pass
a Здоровье4.15:14.5:1
#000000
#5D69B5
Fail
a Соцподдерж…21.00:14.5:1
#000000
#FFFFFF
Pass
a Наука21.00:14.5:1
#000000
#FFFFFF
Pass
a Спорт21.00:14.5:1
#000000
#FFFFFF
Pass
a Колумнисты21.00:14.5:1
#000000
#FFFFFF
Pass
a Происшеств…21.00:14.5:1
#000000
#FFFFFF
Pass
a Национальн…21.00:14.5:1
#000000
#FFFFFF
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 3 failing, 11 passed
REVIEW
82

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
ВИДЕО div.sc-1tputnk-12 > div.sc-1tputnk-0 > a.sc-1tputnk-2 > span.sc-1rckosc-0
21 час назад div.sc-1tputnk-12 > div.sc-1tputnk-0 > div.sc-1tputnk-8 > span.sc-1tputnk-9
день назад div.sc-1tputnk-12 > div.sc-1tputnk-0 > div.sc-1tputnk-8 > span.sc-1tputnk-9
10 часов назад div.sc-1tputnk-12 > div.sc-1tputnk-0 > div.sc-1tputnk-8 > span.sc-1tputnk-9
11 часов назад div.sc-1tputnk-12 > div.sc-1tputnk-0 > div.sc-1tputnk-8 > span.sc-1tputnk-9
12 часов назад div.sc-1tputnk-12 > div.sc-1tputnk-0 > div.sc-1tputnk-8 > span.sc-1tputnk-9
9 часов назад div.sc-1tputnk-12 > div.sc-1tputnk-0 > div.sc-1tputnk-8 > span.sc-1tputnk-9
день назад div.sc-1tputnk-12 > div.sc-1tputnk-0 > div.sc-1tputnk-8 > span.sc-1tputnk-9
18 часов назад div.sc-1tputnk-12 > div.sc-1tputnk-0 > div.sc-1tputnk-8 > span.sc-1tputnk-9
ЗАВТРА div.sc-10r6yic-2 > div.sc-ldhp0k-0 > div.sc-ldhp0k-3 > div.sc-ldhp0k-4
Днем div.sc-ldhp0k-5 > div.sc-ldhp0k-9 > div.sc-ldhp0k-11 > div.sc-ldhp0k-12
Вечером div.sc-ldhp0k-5 > div.sc-ldhp0k-9 > div.sc-ldhp0k-11 > div.sc-ldhp0k-12

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
ПОЛИТИКА div.sc-k5zf9p-13 > div.sc-k5zf9p-1 > div.sc-k5zf9p-11 > a.sc-n7hj2k-0
ПОЛИТИКА div.sc-k5zf9p-13 > div.sc-k5zf9p-1 > div.sc-k5zf9p-11 > a.sc-n7hj2k-0

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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>`
●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.
●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
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[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.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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.
○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
2 headings
PASS
2 headings
Info::
Single H1 present
  • H3 Ваш регион — Россия
  • H1 Новости
A
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
13 image(s) with alt text over 125 characters
Info::
3 image(s) with good alt text
16 images 3 good alt text
IssueCount
too long13 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Favicon & Branding
20 icon(s) detected
PASS
20 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: KP.RU - Комсомольская правда
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name KP.RU - Комсомольская правда ✓192×192 icon ✓512×512 icon ✓Start URL https://www.kp.ru/ ✓Display Mode standalone ✓
Name KP.RU - Комсомольская правда Display Mode standalone Theme Color #f2f2f2 Background Color #ffffff Icons 10 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback