Skip to content
https://cbr.ru

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Alt Text Quality
Action
5 of 17 images have issues
FIX
5 of 17 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
12 image(s) with good alt text
17 images 12 good alt text 5 missing
IssueCount
missing5 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

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: App
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name App ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name App 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::
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.
D
Lighthouse Accessibility Audits
Action
Score 64/100 — 9 failing, 18 passed
FIX
64

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.main-indicator > div.main-indicator_content > div.main-indicator_text > span.main-indicator_info
Инфляция div.main-indicator > div.main-indicator_content > div.main-indicator_sub > span.main-indicator_info

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Новости Новое на сайте Все новости div.col-md-14 > div.home-main_tabs > div.home-sticky > div.tabs

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.main-indicator_rate > div#V_R01375 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn div.main-indicator_rate > div#V_R01375 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn
div.main-indicator_rate > div#V_R01375 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn div.main-indicator_rate > div#V_R01375 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn
div.main-indicator_rate > div#V_R01235 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn div.main-indicator_rate > div#V_R01235 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn
div.main-indicator_rate > div#V_R01235 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn div.main-indicator_rate > div#V_R01235 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn
div.main-indicator_rate > div#V_R01239 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn div.main-indicator_rate > div#V_R01239 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn
div.main-indicator_rate > div#V_R01239 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-btn div.main-indicator_rate > div#V_R01239 > div.main-indicator_tooltip-head > button.main-indicator_tooltip-head-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.search > div.search_field > div.search_clear > img div.search > div.search_field > div.search_clear > img
div.col-md-22 > div.footer_bottom_aic > a > img div.col-md-22 > div.footer_bottom_aic > a > img

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.row > div.col-xl-4 > div.header_left > a.header_logo div.row > div.col-xl-4 > div.header_left > a.header_logo
div.row > div.col-xl-4 > div.header_left > a.d-flex div.row > div.col-xl-4 > div.header_left > a.d-flex
div.row > div.col-xl-5 > div.header_left > a.header_logo div.row > div.col-xl-5 > div.header_left > a.header_logo
div.row > div.col-xl-5 > div.header_left > a.d-flex div.row > div.col-xl-5 > div.header_left > a.d-flex
div.footer_main > div.col-md-23 > div.footer_top > a.footer_logo div.footer_main > div.col-md-23 > div.footer_top > a.footer_logo
div.col-md-23 > div.footer_main_block > div.networks-circle > a.networks-circle_item div.col-md-23 > div.footer_main_block > div.networks-circle > a.networks-circle_item
div.col-md-23 > div.footer_main_block > div.networks-circle > a.networks-circle_item div.col-md-23 > div.footer_main_block > div.networks-circle > a.networks-circle_item
div.footer_bottom > div.col-md-22 > div.footer_bottom_aic > a div.footer_bottom > div.col-md-22 > div.footer_bottom_aic > 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.main-indicator > div.main-indicator_content > div.main-indicator_sub > span.main-indicator_info
Ключевая ставка div.main-indicator > div.main-indicator_content > div.main-indicator_sub > a
Следующее заседание Совета директоров по ключевой ставке div.home-main > div.main-indicator > div.main-indicator_comment > a.main-indicator_comment-text
24.04.2026 div.home-main > div.main-indicator > div.main-indicator_comment > div.main-indicator_comment-date
Ставка RUONIA div.main-indicator > div.main-indicator_content > div.main-indicator_sub > a
Курсы валют div.main-indicator_rates-table > div.main-indicator_rates-head > div.col-md-2 > a
22.04.2026 div.main-indicator_rates-table > div.main-indicator_rates-head > div.col-md-2 > a
23.04.2026 div.main-indicator_rates-table > div.main-indicator_rates-head > div.col-md-2 > a
Новое на сайте div.home-sticky > div.tabs > div.tabs-left > a#tab-4-2
Выберите тип div.filters > span#filtersForEventsAndPress > div#ui-id-1 > div.datepicker-filter_placeholder
Просветительский проект ЦБ о бережном отношении к финансам div.home-main_resources > div.russian-bank-projects > a.russian-bank-project > div.russian-bank-project_text
Популярно о научных исследованиях по экономике и финансам div.home-main_resources > div.russian-bank-projects > a.russian-bank-project > div.russian-bank-project_text
О монетарной политике, финансах и банковской деятельности div.home-main_resources > div.russian-bank-projects > a.russian-bank-project > div.russian-bank-project_text
Цифровой помощник для тех, кто пользуется финуслугами div.home-main_resources > div.russian-bank-projects > a.russian-bank-project > div.russian-bank-project_text
Запись на экскурсии и уникальные материалы по истории денег div.home-main_resources > div.russian-bank-projects > a.russian-bank-project > div.russian-bank-project_text
Электронный каталог экономических и финансовых изданий div.home-main_resources > div.russian-bank-projects > a.russian-bank-project > div.russian-bank-project_text
Данные опросов об экономической активности предприятий div.home-main_resources > div.russian-bank-projects > a.russian-bank-project > div.russian-bank-project_text
www.cbr.ru body.page-v3 > div.popup-cookies > div.popup-cookies_subtitle > a
пользовательское соглашение body.page-v3 > div.popup-cookies > div.popup-cookies_subtitle > a
Подтвердить body.page-v3 > div.popup-cookies > button.btn

These are opportunities to improve the legibility of your content.

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.

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.row > div.col-xl-5 > div.header_left > a.d-flex div.row > div.col-xl-5 > div.header_left > a.d-flex
Ключевая ставка div.main-indicator > div.main-indicator_content > div.main-indicator_sub > a
с 23.03.2026 div.main-indicator > div.main-indicator_content > div.main-indicator_text > a

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
21.04 11,0418 ₽ -0,1039 ₽ 22.04 10,9451 ₽ -0,0967 ₽ 23.04 10,9931 ₽ +0,0480 ₽ div.main-indicator_rates-table > div.main-indicator_rate > div#V_R01375 > table.main-indicator_tooltip-table
21.04 75,2370 ₽ -0,8165 ₽ 22.04 74,5897 ₽ -0,6473 ₽ 23.04 74,9995 ₽ +0,4098 ₽ div.main-indicator_rates-table > div.main-indicator_rate > div#V_R01235 > table.main-indicator_tooltip-table
21.04 88,3769 ₽ -1,2487 ₽ 22.04 87,7659 ₽ -0,6110 ₽ 23.04 87,9733 ₽ +0,2074 ₽ div.main-indicator_rates-table > div.main-indicator_rate > div#V_R01239 > table.main-indicator_tooltip-table
○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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Image elements do not have `[alt]` attributes that are redundant text.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○Heading elements appear in a sequentially-descending order
○`<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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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.
○No element has a `[tabindex]` value greater than 0
○`<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
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Form Accessibility
3 of 8 controls have issues
REVIEW
3 of 8 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="text">; <input type="text" id="SearchForEventsField">; <input type="text" id="SearchForNewsField">
Info::
5 control(s) properly labeled
8 controls
5 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
#filter_1_1ui-id-1radioВсеfor/id
#filter_ui-id-10radioНовостиfor/id
#filter_ui-id-14radioПресс-релизыfor/id
#filter_ui-id-12radioИнтервьюfor/id
#filter_ui-id-11radioВыступленияfor/id
#SearchForEventsFieldtext(Поиск новостей)placeholder only
texttext(Начните писать)placeholder only
#SearchForNewsFieldtext(Поиск новостей)placeholder only

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

<input type="text" name="text">; <input type="text" id="SearchForEventsField">; <input type="text" id="SearchForNewsField">

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

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 404 | Банк России ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
a О Банке России
4.06:1
#000000
on
#696E6E
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Деятельность
2.42:1
#000000
on
#4C4C41
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Денежно-кредитная пол…
2.47:1
#000000
on
#494E49
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Финансовая стабильно…
1.32:1
#000000
on
#162522
needs 4.5:1 (normal text)
16px · above the fold
a Национальная платежн…
2.28:1
#000000
on
#474846
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
title Центральны…21.00:14.5:1
#000000
#FFFFFF
Pass
span Поиск по са…13.88:14.5:1
#000000
#CDD3D6
Pass
span Поиск по са…7.21:14.5:1
#000000
#90999A
Pass
a О Банке Рос…4.06:14.5:1
#000000
#696E6E
Fail
a Деятельнос…2.42:14.5:1
#000000
#4C4C41
Fail
a Денежно-кр…2.47:14.5:1
#000000
#494E49
Fail
a Финансовая…1.32:14.5:1
#000000
#162522
Fail
a Национальн…2.28:14.5:1
#000000
#474846
Fail
a Наличное д…11.32:14.5:1
#000000
#BFBEBD
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
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.

A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 header NAV MAIN CONTENTINFO footer

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

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

Send Feedback