[Skip navigation links]

3% of pages3%of pages

Accessibility

1 page with accessibility issues

better than averageChecking 43 pages found 3% (1 page) with accessibility issues. This is better than the 12% average rate of accessibility issues on other sites.

This tab shows accessibility issues, indicating problems for older users, people with disabilities or accessibility needs. Automated testing cannot detect all accessibility issues, so should be used alongside human testing.

WCAG 2.2

WCAG 2.2 is a W3C accessibility standard published in October 2023. It extends WCAG 2.1 by adding success criteria for accessible authentication and focus appearance. It also removes success criteria 4.1.1 Parsing.

Level A3% Pages with level A issues have critical accessibility barriers and are unusable by some people.

Level AA3% Pages with level AA issues have major accessibility barriers and are very difficult to use.

Level AAA3% Pages with level AAA issues have minor accessibility barriers and can be difficult to use.

Section 508

Section 508 of the Rehabilitation Act of 1973 requires that US Federal employees with disabilities have access to information comparable to employees without disabilities. The Section 508 technical requirements for websites were updated in January 2017, to incorporate WCAG 2.0 at level AA by reference.

Level A3% Pages with level A issues have critical accessibility barriers and are unusable by some people.

Level AA3% Pages with level AA issues have major accessibility barriers and are very difficult to use.

ARIA

WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make web content and web applications more accessible to people with disabilities.

Errors3% Errors indicate conformance errors, and appear when mandatory specification requirements are not met.

Warnings3% Warnings do not indicate conformance errors, but appear when optional specification requirements are not met.

PriorityDescription and URLGuideline and Line NumberCount

Level A

5 issues on 1 pages

Pages with level A issues have critical accessibility barriers and are unusable by some people.

CriticalA label used by a form control must not have ARIA attributes or role. HTML ARIA 4 1 pages
<label for='ff_5_7_phone' id='label_ff_5_7_phone' aria-label='Телефон'>Телефон</label>
Line 881
<label for='ff_5_7_message' id='label_ff_5_7_message' aria-label='Сообщение'>Сообщение</label>
Line 881

https://popartstudio.ru/

CriticalCannot use aria-label or aria-labelledby or aria-braillelabel on elements and roles that prohibit naming. HTML ARIA 5.2.8.6 1 pages
The div and span elements have an implicit role of generic and cannot be named unless they have a role attribute. The following roles cannot be named: caption code deletion definition emphasis generic insertion mark paragraph presentation strong subscript suggestion superscript term time
Element role: 
<label for='ff_5_7_phone' id='label_ff_5_7_phone' aria-label='Телефон'>Телефон</label>
Line 881
Element role: 
<label for='ff_5_7_message' id='label_ff_5_7_message' aria-label='Сообщение'>Сообщение</label>
Line 881

https://popartstudio.ru/

CriticalClickable controls should be keyboard accessible. WCAG A F15 WCAG 2.1.1 508 A F15 1 pages
Add tabindex=0 to allow keyboard users to tab to the control. 
<a class='btn btn-style-...'>Подробнее</a>
Line 977

https://popartstudio.ru/

CriticalClickable controls should have an ARIA role. WCAG A F54 WCAG 4.1.2 508 A F54 1 pages
Controls that respond to clicks should be given an ARIA role such as role=button or role=link. div span and a elements without an href attribute have no semantic role. 
<a class='btn btn-style-...'>Подробнее</a>
Line 977

https://popartstudio.ru/

Criticalimg elements must have an accessible name. WCAG A F65 WCAG 1.1.1 508 A F65 1 pages
Add an alt attribute describing the image, which screen readers voice instead of the image. Spacer images and purely decorative images should use alt="" without any global ARIA attributes. Do not use alt text containing only spaces since that's voiced as an unlabeled image.

Impact on users:

  • NVDA 2025.3 Chrome 143 Windows 11 Reading: Image ignored.
  • NVDA 2025.3 FF 140 Windows 11 Reading: Image ignored.
  • NVDA 2025.3 Chrome 143 Windows 11 Reading: Image ignored.
  • JAWS 2025.2508.120 Chrome 143 Windows 11 Reading: Image ignored.
  • JAWS 2025.2508.120 FF 140 Windows 11 Reading: Image ignored.
  • JAWS 2025.2508.120 Chrome 143 Windows 11 Reading: Image ignored.
  • VoiceOver macOS 15.7 Safari 26.0 macOS 15.7.1 Reading: Image filename read out.
  • VoiceOver iOS 18.6 Safari iOS 18.6 iOS 18.6.2 Touch: Image filename read out, along with OCR text from image.
<img decoding='async' class='wd-lazy-fade' src='https://popartstudio.ru/wp-content/themes/woodmart/images/lazy.svg' data-src='https://...' loading='lazy' width='40' height='40'>
Line 919

https://popartstudio.ru/

Level AA

4 issues on 1 pages

Pages with level AA issues have major accessibility barriers and are very difficult to use.

Very ImportantDo not use the meta viewport tag to disable zoom. WCAG AA 1.4.4 508 AA 1.4.4 1 pages
Setting user-scalable=no or maximum-scale to less than 2.0 prevents zooming small text to make it readable. Note that iOS 10+ ignores this setting. 
<meta name='viewport' content='width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no'>
Line 106

https://popartstudio.ru/

Very ImportantEnsure that text and background colors have enough contrast. WCAG AA 1.4.3 WCAG 1.4.6 508 AA 1.4.3 1 pages

Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background.

  • The contrast ratio should be 3.0 or more for 18 point text, or larger
  • The contrast ratio should be 3.0 or more for 14 point bold text, or larger
  • The contrast ratio should be 4.5 or more for all other text
The text color to background color contrast ratio after composition is:
3.00 with color: rgb(230,230,230)background: rgba(10,10,10,50.2%)
font-size: 10.50ptfont-weight: 400
<div class='title-subtitle ...'>СКАЖИ ПРИ ... МЕСЯЦА</div>
Line 773
2.39 with color: rgb(131,183,53)background: rgb(255,255,255)
font-size: 13.50ptfont-weight: 500
<span>МОБИЛЬНЫЙ ШИНОМОНТАЖ</span>
Line 517
2.39 with color: rgb(255,255,255)background: rgb(131,183,53)
font-size: 12ptfont-weight: 600
<a href='#3564353458' title='' class='btn btn-color-...'>...</a>
Line 360
2.39 with color: rgb(255,255,255)background: rgb(131,183,53)
font-size: 10.50ptfont-weight: 600
<a href='#354354354' title='' class='btn btn-color-...'>...</a>
Line 783
2.39 with color: rgb(131,183,53)background: rgb(255,255,255)
font-size: 9.75ptfont-weight: 600
<span class='nav-link-text'>Почему мы</span>
Line 1021

https://popartstudio.ru/

Very ImportantThe CSS outline or border style on this element makes it difficult or impossible to see the link focus outline. WCAG AA F78 WCAG 2.4.7 508 AA F78 1 pages
Do not remove the default outline style, and change any border styles to avoid obscuring the focus outline around focusable elements. See :focus-visible for more information.

Using a border or outline style that obscures the focus ring causes problems for keyboard-only users in:

  • Chrome (obscures the focus indicator on links, buttons, dropdowns and range controls)
  • Firefox (obscures the focus indicator on links)
outline-color: matches background 
<a class='wd-promo-banner-link' href='...udio.ru/prikurit_akkumuljator/' title='' aria-label='Ссылка баннера'></a>
Line 392
outline-color: matches background 
<a class='wd-promo-banner-link' href='...rtstudio.ru/vytashhit_mashinu/' title='' aria-label='Ссылка баннера'></a>
Line 411
outline-color: matches background 
<a class='wd-promo-banner-link' href='...tudio.ru/vskrytie-avtomobilya/' title='' aria-label='Ссылка баннера'></a>
Line 430
outline-color: matches background 
<a class='wd-promo-banner-link' href='...partstudio.ru/pomenjat_koleso/' title='' aria-label='Ссылка баннера'></a>
Line 449
outline-color: matches background 
<a class='wd-promo-banner-link' href='...tudio.ru/zamena_akkumuljatora/' title='' aria-label='Ссылка баннера'></a>
Line 468

https://popartstudio.ru/

Very ImportantUse relative units in CSS property values when zoom is disabled by meta viewport. WCAG AA 1.4.4 508 AA 1.4.4 1 pages
Either allow the user to zoom content using pinch-zoom by removing user-scalable=no from the meta viewport tag (easiest), or allow the user to increase text size by using relative units like em and not absolute units like px and pt 
##wd-694e1b88f22ca .woodmart-title-container { font-size: 48px; }
Line 235
##wd-694e29bfc32c9 .info-box-title { font-size: 18px; }
Line 235
##wd-694e2a239d8c6 .info-box-title { font-size: 18px; }
Line 235
##wd-694e2a289723b .info-box-title { font-size: 18px; }
Line 235
##wd-694e1b88f22ca .woodmart-title-container { font-size: 36px; }
Line 235

https://popartstudio.ru/

Level AAA

2 issues on 1 pages

Pages with level AAA issues have minor accessibility barriers and can be difficult to use.

ImportantAvoid specifying a new window as the target of a link with target=_blank. WCAG AAA F22 WCAG 3.2.5 1 pages
Displaying new windows without warning can be very confusing to non-sighted and mobile users. Some screen readers and mobile devices give very little indication a new tab or window has opened. If you cannot avoid displaying a new window, insert an "opens in a new window" warning into the link text or add the warning to the link using a title attribute or aria-describedby attribute. 
<a href='...partstudio.ru/pomenjat_koleso/' target='_blank' rel='noopener'>...</a>
Line 524
<a href='...ttps://telegram.me/pinochetspb' target='_blank' rel='nofollow noopener' class='chaty-tooltip ...' data-form='chaty-form-_1-...' data-hover='Telegram' aria-label='Telegram'>...</a>
Line 1157

https://popartstudio.ru/

ImportantEnsure that text and background colors have a 7:1 contrast ratio. WCAG AAA 1.4.6 1 pages

Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background.

  • The contrast ratio should be 4.5 or more for 18 point text, or larger
  • The contrast ratio should be 4.5 or more for 14 point bold text, or larger
  • The contrast ratio should be 7.0 or more for all other text
The text color to background color contrast ratio after composition is:
3.74 with color: rgb(255,255,255)background: rgba(10,10,10,50.2%)
font-size: 36ptfont-weight: 600
<h2 class='woodmart-title-...'>СКИДКА 5% ... МЕСЯЦА</h2>
Line 776
4.54 with color: rgb(118,118,118)background: rgb(255,255,255)
font-size: 9.60ptfont-weight: 400
<small>КРУГЛОСУТОЧНАЯ ПОМОЩЬ НА ДОРОГАХ</small>
Line 995
4.54 with color: rgb(118,118,118)background: rgb(255,255,255)
font-size: 12ptfont-weight: 400
<p>Выезд к любому ..., чтобы помочь</p>
Line 822
4.54 with color: rgb(118,118,118)background: rgb(255,255,255)
font-size: 12ptfont-weight: 400
<p>Прикуривание ... прямо на месте</p>
Line 840
4.54 with color: rgb(118,118,118)background: rgb(255,255,255)
font-size: 12ptfont-weight: 400
<p>Специалисты ... в любой ситуации</p>
Line 858

https://popartstudio.ru/

Warnings

2 issues on 1 pages

Warnings do not indicate conformance errors, but appear when optional specification requirements are not met.

WarningThe main role is unnecessary for element main. ARIA 3.2 HTML 1 pages
<main id='main-content' class='wd-content-layout ...' role='main'>...</main>
Line 343

https://popartstudio.ru/

WarningThe navigation role is unnecessary for element nav. ARIA 3.2 HTML 1 pages
<nav class='wd-header-nav wd-...' role='navigation' aria-label='Главное меню'>...</nav>
Line 265

https://popartstudio.ru/

Expand all 13 issues