Fixing WCAG Violations on Bitrix: Audit and Implementation

Standard Bitrix catalog fails an automated Axe check — 40 violations on the homepage. That's not a reason to panic, but a cause for systematic audit. WCAG 2.1 Level AA is not optional for government and financial sites in Russia. In recent years, regulators directly reference the standard during inspections. But even for commercial projects, accessibility affects SEO: search bots read the site like a screen reader — poor semantics means poor indexing. We configure accessibility turnkey: from audit to final testing with real users. Over 5 years we've completed more than 50 WCAG projects, including large online stores on Bitrix.

Which WCAG violations are most common in Bitrix

Bitrix templates "out of the box" violate WCAG for several systemic reasons. Let's look at the most frequent.

Images without alt. The catalog.element component outputs <img> via CFile::ShowImage() — this method does not add alt automatically. In the template, you need to pass the attribute explicitly:

echo CFile::ShowImage($fileId, 800, 800, 'border="0"',
    'alt="' . htmlspecialcharsEx($arResult['NAME']) . '"');

Buttons without text content. Icon buttons like "Add to cart" with an SVG icon and no text violate criterion 1.1.1. The minimum fix is to add aria-label:

<button class="cart-btn" aria-label="Add to cart">
    <svg>...</svg>
</button>

Navigation menus without semantics. The standard bitrix:menu component generates <ul>/<li> without <nav> and without aria-label — multiple navigation menus on a page are indistinguishable for screen readers. Solution: wrap each menu in <nav> with a unique aria-label.

How to fix missing alt in the catalog.element component

Let's show with an example: a client is an auto parts online store with a catalog of 10,000 items. Axe found 400 alt violations. We overrode the catalog.element template — in result_modifier.php we added an array with alt from the element's NAME. Then in the template the image is output via a regular <img> with alt. Additionally, we had to handle images in SKUs via the OnGetImageAlt event. As a result, alt violations dropped to 0, and load time did not increase — page size changed negligibly.

Audit via automated tools

Before code fixes, a baseline check is needed. According to WCAG documentation (see Understanding Documents), automated tools do not replace expert review but speed up finding typical errors. Axe DevTools (Chrome extension) finds violations with DOM node references in 30 seconds. Lighthouse (Accessibility tab) gives a score of 0–100. The target for WCAG AA is 90+, but 100 does not guarantee full conformance: automation does not check logic, only markup.

A typical report for a Bitrix store: 20–40 violations, of which 60% are missing alt, 20% contrast issues, 10% missing label on form fields.

Manual audit reveals 3 times more critical errors than automated checks — this is confirmed by our projects. Axe finds only 30% of violations, while manual testing finds 100%.

Why automated checking is not enough

Axe only finds what is coded into its rules: contrast, alt, aria. But it does not check focus logic, screen reader readability, or keyboard navigation. For example, if a button appears dynamically, Axe will see it but won't check whether it can be tabbed to. Manual testing with NVDA or JAWS is mandatory. Manual audit reveals 3 times more critical errors than automated checks — this is confirmed by our projects.

Forms: fields with label

Bitrix forms (cart, registration, callback) often use placeholder instead of <label>. This violates criterion 1.3.1 — placeholder disappears on input, and users with cognitive impairments lose field context.

The bitrix:main.register component generates fields via $arResult['PERSONAL_FIELDS'] — the template must be rewritten with explicit <label for="...">:

<label for="USER_LOGIN">Login</label>
<input type="text" id="USER_LOGIN" name="USER_LOGIN"
       required aria-required="true"
       autocomplete="username">

Skip-link for keyboard navigation

The first element on the page should be a link "Skip to main content" — it allows keyboard users to bypass navigation. In Bitrix it is added at the beginning of header.php:

<a class="skip-link" href="#main-content">Skip to main content</a>

CSS makes it visible only on focus:

.skip-link {
    position: absolute;
    left: -9999px;
}
.skip-link:focus {
    left: 0; top: 0;
    z-index: 9999;
    padding: 8px 16px;
    background: #000;
    color: #fff;
}

Contrast and font sizes

WCAG 2.1 AA requires text contrast to background at least 4.5:1 for normal text and 3:1 for large text (18pt+). Gray labels on white background (#999 on #fff) give contrast 2.85:1 — violation. Check with the WebAIM Contrast Checker tool, fix by changing color to at least #767676.

How to conduct a WCAG audit on Bitrix: step-by-step guide

1. Run Axe DevTools on each typical page (homepage, catalog, product card, cart, form).
2. Collect the report — export JSON with violations.
3. Classify them into groups: alt, contrast, label, ARIA.
4. Fix first those that block the user path (buttons without text, missing skip-link).
5. Repeat the automated check — ensure the violation count has dropped.
6. Perform manual testing with NVDA or JAWS on 3–5 key scenarios.

The cost of audit and modifications is calculated individually. Yearly savings on support can be substantial.

What is included in turnkey accessibility setup

We provide: an audit report with a full list of violations and recommendations, correction of all errors in template and component code, skip-link setup, semantic markup, contrasts, form improvements, re-audit after fixes, training for content managers, and developer documentation. We guarantee elimination of all critical violations. Contact us to assess your project. Order a free accessibility consultation for your Bitrix site.

Experience: over 50 accessibility projects on 1C-Bitrix, 5+ years in the market. We use WCAG 2.1 and Russian recommendations.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.