[Skip navigation links]

5% of pages5%of pages

Accessibility

2 pages with accessibility issues

better than averageChecking 42 pages found 5% (2 pages) 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 A5% Pages with level A issues have critical accessibility barriers and are unusable by some people.

Level AA5% 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 A5% Pages with level A issues have critical accessibility barriers and are unusable by some people.

Level AA5% 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.

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

Warnings5% 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 2 pages

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

CriticalElements with role=img must have an accessible name. WCAG A F65 WCAG 1.1.1 508 A F65 2 pages
Add an aria-label or aria-labelledby attribute describing the image. Purely decorative images should use role=presentation.
<div class='tn-atom t-bgimg ...' data-original='https://static....' role='img' style='box-sizing: border-...' aria-label=''></div>
Line 75
<div class='tn-atom t-bgimg ...' data-original='https://static....' role='img' style='box-sizing: border-...' aria-label=''></div>
Line 75
<div class='tn-atom t-bgimg' data-original='https://static....' role='img' style='box-sizing: border-...' aria-label=''></div>
Line 75
<div class='tn-atom t-bgimg' data-original='https://static....' role='img' style='box-sizing: border-...' aria-label=''></div>
Line 75
<div class='tn-atom t-bgimg' data-original='https://static....' role='img' style='box-sizing: border-...' aria-label=''></div>
Line 75

https://abramchuk-strateg.ru/

<div class='tn-atom t-bgimg' data-original='https://static....' role='img' aria-label=''></div>
Line 533
<div class='tn-atom t-bgimg' data-original='https://static....' role='img' aria-label=''></div>
Line 2199
<div class='tn-atom t-bgimg' data-original='https://static....' role='img' aria-label=''></div>
Line 2204
<div class='tn-atom t-bgimg' data-original='https://static....' role='img' aria-label=''></div>
Line 2209

https://abramchuk-strateg.ru/konsalting

Criticaliframe and frame elements must have a title attribute. WCAG A 4.1.2 508 A 4.1.2 1 pages
Add a title attribute or ARIA label to each iframe and frame element (e.g. title='Main Content'). VoiceOver on macOS does not read frame contents automatically, and without a title the user does not know what the frame contains.

Impact on users:

  • VoiceOver macOS 15.7 Safari 26.0 macOS 15.7.1 Reading: Meaningless frame title read out.
<iframe id='...' class='t1035__iframe ...' src='https://kinescope.io/embed/84KXEY3F5Yy6esEsuJnvRF?v=2.187.1&#38;_=cGxheWVySWQ9a2luZXNjb3BldGh1bWIyMTc3MzI5NDgxXzYwJnNpemUlNUJoZWlnaHQlNUQ9MTAwJTI1JnNpemUlNUJ3aWR0aCU1RD0xMDAlMjUmYmVoYXZpb3IlNUJsb29wJTVEPXRydWUmYmVoYXZpb3IlNUJhdXRvUGxheSU1RD10cnVl' width='560' height='315' frameborder='0' scrolling='no' allow='fullscreen; picture-...' allowfullscreen style='border-width: 0px;'></iframe>
Line 58

https://abramchuk-strateg.ru/

CriticalIndicating links using only a text color change does not work for color-blind users. WCAG A F73 WCAG 1.4.1 508 A F73 1 pages
Remove the text-decoration:none property from your link styles, or add other style attributes in addition to color changes to make links visible to people without color vision. If the non-color cue only happens when the mouse hovers over the link or when the link receives focus, it is still a failure.
<a href='...//abramchuk-strateg.ru/privacy' style='color: rgb(121, 46, ...'>политикой конфиденциальности</a>
Line 75

https://abramchuk-strateg.ru/

CriticalLinks must have an accessible name. WCAG A F89 WCAG 2.4.4 WCAG 2.4.9 WCAG 4.1.2 508 A F89 2 pages

A link name allows screen readers to voice what the links does. If there is no link content, or the link content is hidden by CSS, screen readers have nothing to read, so read out the URL instead. To add a name do one of the following:

  • Add text between the a element start and end tags
  • Add an aria-label attribute
  • Add an aria-labelledby attribute
  • Add an img alt attribute labeling the link if it contains an img element
img elements with role=presentation or role=none are not included in the link's accessible name.
<a class='tn-atom' href='https://t.me/abramchuk_strateg' style='box-sizing: border-...'>...</a>
Line 58
<a class='tn-atom' href='https://dzen.ru/abramchuk_strateg' style='box-sizing: border-...'>...</a>
Line 58
<a class='tn-atom' href='https://vk.com/strateg.abramchuk' style='box-sizing: border-...'>...</a>
Line 58

https://abramchuk-strateg.ru/

<a class='tn-atom' href='https://t.me/abramchuk_strateg'>...</a>
Line 149
<a class='tn-atom' href='https://dzen.ru/abramchuk_strateg'>...</a>
Line 171
<a class='tn-atom' href='https://vk.com/strateg.abramchuk'>...</a>
Line 179

https://abramchuk-strateg.ru/konsalting

CriticalUse the lang attribute to identify the language of the page. WCAG A 3.1.1 508 A 3.1.1 2 pages
In HTML add a lang attribute containing a language code to the html tag, and in PDF set the language using Document Properties in Acrobat. This allows screen readers to pronounce words correctly.
<html><head><meta charset='utf-8'>...</head>...</html>
Line 2

https://abramchuk-strateg.ru/

<html><head><meta charset='utf-8'>...</head>...</html>
Line 2

https://abramchuk-strateg.ru/konsalting

Level AA

2 issues on 2 pages

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

Very ImportantEnsure that text and background colors have enough contrast. WCAG AA 1.4.3 WCAG 1.4.6 508 AA 1.4.3 2 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:
1.95 with color: rgb(43,114,180)background: rgb(116,44,44)
font-size: 19.50ptfont-weight: 400
<em style='font-family: var(--...'>{01}</em>
Line 75
1 with color: rgb(255,255,255)background: linear-gradient(180.0deg , rgb(255,255,255) 0% , rgb(59,59,59) 100%)
font-size: 150ptfont-weight: 400
<div class='tn-atom' field='...' style='box-sizing: border-...'>....</div>
Line 75

https://abramchuk-strateg.ru/

The text color to background color contrast ratio after composition is:
1 with color: rgb(255,255,255)background: linear-gradient(180.0deg , rgb(255,255,255) 0% , rgb(59,59,59) 100%)
font-size: 150ptfont-weight: 400
<div class='tn-atom' field='...'>Абрамчук а.н.</div>
Line 3126

https://abramchuk-strateg.ru/konsalting

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 2 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)
:focus has outline: rgb(32,21,255) auto 0px
<button type='button' class='t-menuburger t-...' aria-label='Навигационное меню' aria-expanded='false'>...</button>
Line 59
:focus has outline: rgb(32,21,255) auto 0px
<a class='tn-atom' href='#popuppdf' style='box-sizing: border-...'>...</a>
Line 75
:focus has outline: rgb(32,21,255) auto 0px
<a class='tn-atom' href='#forma' style='box-sizing: border-...'>...</a>
Line 75
:focus has outline: rgb(32,21,255) auto 0px
<a href='...bramchuk-strateg.ru/konsalting' style='color: inherit'>...</a>
Line 58
:focus has outline: rgb(32,21,255) auto 0px
<a href='#contacts' style='color: inherit'>Контакты</a>
Line 58

https://abramchuk-strateg.ru/

:focus has outline: rgb(32,21,255) auto 0px
<a href='https://t.me/Yulipopi' style='color: inherit'>...</a>
Line 3139
:focus has outline: rgb(32,21,255) auto 0px
<a href='...//abramchuk-strateg.ru/privacy' style='color: inherit'>...</a>
Line 3145
:focus has outline: rgb(32,21,255) auto 0px
<a href='#contacts' style='color: inherit'>Контакты</a>
Line 3151
:focus has outline: rgb(32,21,255) auto 0px
<a href='#smi' style='color: inherit'>...</a>
Line 3157
:focus has outline: rgb(32,21,255) auto 0px
<a href='#portfolio' style='color: inherit'>Проекты и кейсы</a>
Line 3163

https://abramchuk-strateg.ru/konsalting

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='https://t.me/abramchuk_strateg' target='_blank' rel='nofollow noopener' style='width: 30px; height:' aria-label='telegram'>...</a>
Line 75
<a href='...tps://vk.com/strateg.abramchuk' target='_blank' rel='nofollow noopener' style='width: 30px; height:' aria-label='vk'>...</a>
Line 75
<a href='...ps://dzen.ru/abramchuk_strateg' target='_blank' rel='nofollow noopener' style='width: 30px; height:' aria-label='zen'>...</a>
Line 75

https://abramchuk-strateg.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.69 with color: rgb(43,114,180)background: rgb(0,21,34)
font-size: 19.50ptfont-weight: 400
<em style='color: rgb(43, 114, ...'>{02}</em>
Line 75
3.69 with color: rgb(43,114,180)background: rgb(0,21,34)
font-size: 19.50ptfont-weight: 400
<em style='color: rgb(43, 114, ...'>{03}</em>
Line 75
3.69 with color: rgb(43,114,180)background: rgb(0,21,34)
font-size: 19.50ptfont-weight: 400
<em style='color: rgb(43, 114, ...'>{04}</em>
Line 75
3.69 with color: rgb(43,114,180)background: rgb(0,21,34)
font-size: 19.50ptfont-weight: 400
<em style='color: rgb(43, 114, ...'>{05}</em>
Line 75

https://abramchuk-strateg.ru/

Warnings

2 issues on 2 pages

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

WarningThe form role is unnecessary for element form. ARIA 3.2 HTML 1 pages
<form class='t-form t-...' id='form1997050462' name='form1997050462' action='https://forms....' method='post' role='form' data-formactiontype='2' data-inputbox='.t-input-group' data-success-callback='t396_onSuccess' data-success-popup='y' data-error-popup='y'>...</form>
Line 75
<form class='t-form t-...' id='form1997063162' name='form1997063162' action='https://forms....' method='post' role='form' data-formactiontype='2' data-inputbox='.t-input-group' data-success-callback='t396_onSuccess' data-success-popup='y' data-error-popup='y'>...</form>
Line 75

https://abramchuk-strateg.ru/

WarningThe list role is unnecessary for element ul. ARIA 3.2 HTML 2 pages
<ul role='list' class='t-...' aria-label='Соц. сети'>...</ul>
Line 75
<ul role='list' class='t450__list t-...'><li class='t450__list_item'>...</li>...</ul>
Line 61

https://abramchuk-strateg.ru/

<ul role='list' class='t450__list t-...'><li class='t450__list_item'>...</li>...</ul>
Line 263
<ul role='list' class='t-...' aria-label='Соц. сети'>...</ul>
Line 320

https://abramchuk-strateg.ru/konsalting

Expand all 11 issues