Skip to content
https://garant.ru

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 REVIEW 7 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

D
Favicon & Branding
Action
7 icon(s) detected
FIX
7 icon(s) detected
Info::
favicon.ico present at site root
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Garant.Ru
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name Garant.Ru ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name Garant.Ru Icons 6 icon(s)
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 69/100 — 7 failing, 16 passed
FIX
69

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Читать далее div.container > div.row > div.col-xs-12 > a.btn
Читать далее div.container > div.row > div.col-xs-12 > a.btn

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
div.container > div.row > div.col-xs-12 > button.navbar-toggle div.container > div.row > div.col-xs-12 > button.navbar-toggle
form#search_main > div.input-group > div.input-group-btn > button.btn form#search_main > div.input-group > div.input-group-btn > button.btn
form#search_main > div.input-group > div.input-group-btn > button.btn form#search_main > div.input-group > div.input-group-btn > button.btn
form#search_main > div.input-group > div.input-group-btn > button.btn form#search_main > div.input-group > div.input-group-btn > button.btn

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-xs-6 > a > img.img-responsive div.row > div.col-xs-6 > a > img.img-responsive
div.row > div.col-xs-5 > a > img.img-responsive div.row > div.col-xs-5 > a > img.img-responsive
div.col-xs-12 > p.topic > a > img div.col-xs-12 > p.topic > a > img
div.col-xs-12 > div.item > a > img div.col-xs-12 > div.item > a > img
div.col-xs-12 > div.item > a > img div.col-xs-12 > div.item > a > img
div.col-xs-12 > div.item > a > img div.col-xs-12 > div.item > a > img
div.col-xs-12 > div.item > a > img div.col-xs-12 > div.item > a > img
div.col-xs-12 > div.item > a > img div.col-xs-12 > div.item > a > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > iframe#__utl_share_cnt_fetcher_v1_ body > iframe#__utl_share_cnt_fetcher_v1_
body > iframe body > iframe
body > iframe body > iframe

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.container > div.row > div.col-xs-12 > a.btn div.container > div.row > div.col-xs-12 > a.btn
div.container > div.row > div.col-xs-12 > a.btn div.container > div.row > div.col-xs-12 > a.btn
div.container > div.row > div.col-xs-12 > a.btn div.container > div.row > div.col-xs-12 > a.btn
div.container > div.row > div.col-xs-12 > a.btn div.container > div.row > div.col-xs-12 > a.btn
div.container > div.row > div.col-xs-12 > a.btn div.container > div.row > div.col-xs-12 > a.btn
div.container > div.row > div.col-xs-12 > a.btn div.container > div.row > div.col-xs-12 > a.btn
div.container > div.row > div.col-xs-12 > a.btn div.container > div.row > div.col-xs-12 > a.btn
div.container > div.row > div.col-xs-6 > a div.container > div.row > div.col-xs-6 > a
div.container > div.row > div.col-xs-5 > a div.container > div.row > div.col-xs-5 > a
div.row > div.col-xs-12 > div#adfox_167895530344185320 > a.g73a5bf50 div.row > div.col-xs-12 > div#adfox_167895530344185320 > a.g73a5bf50
div.col-xs-12 > div.pull-right > noindex > a div.col-xs-12 > div.pull-right > noindex > 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.

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.col-xs-12 > div.important-info > div.text-right > a.text-muted
ЖКХ div.meta > div.tags-set > div.category-tag > a.text-muted
Требования касаются возможности удаленного управления, записи по событиям или р… div.col-xs-12 > div.item > div.descr > div.text-muted
Общество div.meta > div.tags-set > div.category-tag > a.text-muted
Также в числе поправок – новый порядок ввоза продукции из ЕАЭС, внесудебное обр… div.col-xs-12 > div.item > div.descr > div.text-muted
Труд div.meta > div.tags-set > div.category-tag > a.text-muted
Если это препятствует плотному прилеганию средства защиты органов дыхания к лиц… div.col-xs-12 > div.item > div.descr > div.text-muted
Судебная практика div.meta > div.tags-set > div.category-tag > a.text-muted
Ранее такое правило разрешалось применять только в отношении участников програм… div.col-xs-12 > div.item > div.descr > div.text-muted
Бизнес div.meta > div.tags-set > div.category-tag > a.text-muted
Добавлять в систему сведения следует в течение 15 дней со дня утверждения докум… div.col-xs-12 > div.item > div.descr > div.text-muted
Зарегистрировано в Минюсте РФ 20 апреля 2026 г. div.row > div.col-xs-12 > div.item > p.text-muted
В рамках мероприятия работала выставка решений и технологий, на которой был пре… div.col-xs-12 > div.item > div.descr > div.text-muted
Конференция предоставила уникальную возможность обсудить важные для юристов и с… div.col-xs-12 > div.item > div.descr > div.text-muted

These are opportunities to improve the legibility of your content.

Best practices

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[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
○`<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.
○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.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 403 Forbidden
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
3 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.

3 pass
Show all checked elements (3)
ElementRatioRequiredFGBGResult
h1 403 Forbidden21.00:13.0:1
#000000
#FFFFFF
Pass
title 403 Forbidden21.00:14.5:1
#000000
#FFFFFF
Pass
center nginx21.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.

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

Send Feedback