reg.ru Accessibility Report

Accessibility audit of reg.ru — scanned on Feb 20, 2026

Technology
0 /100
F Critical Issues

6 issues found across 2 categories

5 Critical 1 Major

WCAG Compliance Overview

Perceivable 3 issues
Operable 1 issues
Understandable 1 issues
Robust 1 issues

Issues Found

Page missing language attribute

Critical

The <html> element must have a valid lang attribute to help screen readers pronounce content correctly.

WCAG 3.1.1
1 element(s) affected
  • <html>
How to fix

Add lang attribute to the <html> element, e.g., <html lang="en">.

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
2 element(s) affected
  • <a href="https://reg.ru">
  • <a href="/solutions/catalog">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Viewport blocks user scaling

Critical

Users must be able to zoom and scale the page. Blocking zoom prevents low-vision users from enlarging content.

WCAG 1.4.4
1 element(s) affected
  • <meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0">
How to fix

Remove maximum-scale=1 and user-scalable=no from the viewport meta tag.

Form inputs missing labels

Critical

Form elements must have associated labels so users know what information to enter.

WCAG 1.3.1
1 element(s) affected
  • <input type="search" name="query">
How to fix

Add <label> elements with matching for attributes, or use aria-label.

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
6 element(s) affected
  • <button>
  • <button>
  • <button>
  • <button>
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Heading levels skip order

Major

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
1 element(s) affected
  • <h3> "Сделаем за вас" (after h1)
How to fix

Restructure headings to follow sequential order. Don't skip from h1 to h3.

Top Priority Fixes

Here are the most impactful changes reg.ru should make to improve accessibility:

  1. #1
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

  2. #2
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  3. #3
    Page missing language attribute Critical

    Add lang attribute to the <html> element, e.g., <html lang="en">.

Frequently Asked Questions

Is reg.ru accessible?

reg.ru scored 17/100 (grade F) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is reg.ru WCAG compliant?

Our scan found 6 accessibility issues on reg.ru. Full WCAG compliance requires addressing all critical and major issues identified above.

Is reg.ru EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see reg.ru's compliance status.

What accessibility issues does reg.ru have?

See the full issue list above with severity levels, affected elements, and recommended fixes for reg.ru.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing