Skip to content
https://liveinternet.ru

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
8
REVIEW
5
PASS
0
INFO
0
Checks
13
5 REVIEW 8 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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
Alt Text Quality
Action
4 of 21 images have issues
FIX
4 of 21 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
4 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
12 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
21 images 5 good alt text 12 decorative 4 missing
IssueCount
missing4 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 63/100 — 7 failing, 13 passed
FIX
63

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.allpageinner > div.leftcolumn > b.highlight > a
Всего 346 тыс. сайтов, сегодня 1.00 млрд. просмотров, вчера - 1.05 млрд. div.allpage > div.allpageinner > div.leftcolumn > div.statisticbox
Завести дневник div.rightcolumn > h2 > b.highlight > a
4 997 303 дневников, 71 293 сообществ, 762 сообщений за последний час div.allpageinner > div.float100 > div.rightcolumn > div.statisticbox

These are opportunities to improve the legibility of your content.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Артрозы Рак крови и беременность: Как работает фонд борьбы с лейкемией Фермен… div.leftcolumn > ul.advertisement > li > dl

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.search > form#GlobalSrcForm > div.textbox > input#searcharea div.search > form#GlobalSrcForm > div.textbox > input#searcharea

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.float100 > div.rightcolumn > h2 > a.icon div.float100 > div.rightcolumn > h2 > a.icon
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
ul.bloglist > li > div.user > a ul.bloglist > li > div.user > a
body > div.footer > div.footerinner > a body > div.footer > div.footerinner > a

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.

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.rating > ul > li > a
Дом и семья div.rating > ul > li > a
Игры div.rating > ul > li > a
Интернет div.rating > ul > li > a
Кино div.rating > ul > li > a
Компьютеры div.rating > ul > li > a
Литература div.rating > ul > li > a
Музыка div.rating > ul > li > a
MP3 div.rating > ul > li > a
Новости, СМИ div.rating > ul > li > a
Обучение div.rating > ul > li > a
Погода div.rating > ul > li > a
Софт div.rating > ul > li > a
Спорт div.rating > ul > li > a
div.float100 > div.rightcolumn > h2 > a.icon div.float100 > div.rightcolumn > h2 > a.icon
Кахетинка ul.bloglist > li > div.user > a
Васмак ul.bloglist > li > div.user > a
apostol_nik ul.bloglist > li > div.user > a
© div.footer > div.footerinner > div.copy > a

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>`
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●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
●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.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[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
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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.
○`<td>` elements in a large `<table>` have one or more table headers.
B
Heading Hierarchy
7 headings
REVIEW
7 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Популярные новости
  • H2 Рейтинг сайтов
  • H2 Дневники Завести дневник
  • H2 Рекомендуемые сайты
  • H2 Погода г. Москва, Россия
  • H2 Курсы валют от 21.04
  • H3 Медицина и здоровье на Doctor.ru:

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

C
Form Accessibility
Action
13 of 15 controls have issues
REVIEW
13 of 15 controls have issues
Critical::
13 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="string" id="searcharea">; <input type="submit">; <select id="MM-town-selector-zBlMSMvL5t">; <input type="text" name="url">; <input type="password" name="password">; <input type="submit">; <input type="text" name="blog_username">; <input type="password" name="blog_password">; <input type="submit">; <input type="text" name="mail_login"> (+3 more)
Info::
2 control(s) properly labeled
15 controls
2 labeled
0 placeholder only
13 unlabeled
ControlTypeLabelMethod
#ssiteradioдневникахfor/id
#sstatradioстатистикеfor/id
#searchareatext(none)none
inputsubmit(none)none
#MM-town-selector-zBlMSMvL5tselect(none)none
urltext(none)none
passwordpassword(none)none
inputsubmit(none)none
blog_usernametext(none)none
blog_passwordpassword(none)none
inputsubmit(none)none
mail_logintext(none)none
domainselect(none)none
mail_passpassword(none)none
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="string" id="searcharea">; <input type="submit">; <select id="MM-town-selector-zBlMSMvL5t">; <input type="text" name="url">; <input type="password" name="password">; <input type="submit">; <input type="text" name="blog_username">; <input type="password" name="blog_password">; <input type="submit">; <input type="text" name="mail_login"> (+3 more)

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title LiveInternet - ��������,�������,������ ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Color Contrast (Screenshot)
20 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.

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Рекомендуе…8.93:13.0:1
#000000
#F49127
Pass
title LiveInternet @ Ст…18.10:14.5:1
#000000
#EEEEEE
Pass
div Войти:21.00:14.5:1
#000000
#FFFFFF
Pass
a В статисти…21.00:14.5:1
#000000
#FFFFFF
Pass
a В дневник15.76:14.5:1
#000000
#DFDFDF
Pass
a В почту10.63:14.5:1
#000000
#9CBCDB
Pass
a Создать дн…17.09:14.5:1
#000000
#DFE9F3
Pass
a Рейтинг дн…13.38:14.5:1
#000000
#BBD1E6
Pass
a Популярные…5.48:14.5:1
#000000
#4D86BF
Pass
a Села за рул…21.00:14.5:1
#000000
#FFFFFF
Pass
a 🌸 Весенни…21.00:14.5:1
#000000
#FFFFFF
Pass
a Бросили от…14.34:14.5:1
#000000
#B9DAEF
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
div Всего 346 ты…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 Дом и семья15.31:14.5:1
#000000
#DCDCDC
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.

Send Feedback