[Skip navigation links]

6% of pages6%of pages

Accessibility

1 page with accessibility issues

better than averageChecking 19 pages found 6% (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 A6% Pages with level A issues have critical accessibility barriers and are unusable by some people.

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

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

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

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

Warnings0% 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.

CriticalAn image with a null alt attribute should not have title, aria-label or aria-labelledby attributes. WCAG A F39 WCAG 1.1.1 508 A F39 1 pages
If the image should be voiced use a descriptive alt attribute. If the image is purely decorative remove any title and ARIA label attributes.

Impact on users:

  • NVDA 2025.3 : Reads images with alt='' and a title or ARIA label.
  • NVDA 2023 : Sometimes reads images with alt='' and a title or ARIA label.
  • JAWS 2025.2508.120 : Reads images with alt='' and a title or ARIA label.
  • JAWS 2023 : Ignores images with alt='' and a title or ARIA label.
  • VoiceOver : Sometimes reads images with alt='' and a title or ARIA label.
<img id='licntC87E' width='31' height='31' style='border:0' title='LiveInternet' src='...%7C%20MuzCe;0.0980093913250385' alt=''>
Line 669

https://muzce.com/

CriticalLinks must have an accessible name. WCAG A F89 WCAG 2.4.4 WCAG 2.4.9 WCAG 4.1.2 508 A F89 1 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 href='https://muzce.com/4565-jakone-kiliana-zhiganskaya.html' class='track-dl'>...</a>
Line 160
<a href='https://muzce.com/2110-ajgor-tancuj-devochka-tancuj.html' class='track-dl'>...</a>
Line 170
<a href='https://muzce.com/10997-ganvest-dyrka.html' class='track-dl'>...</a>
Line 180
<a href='https://muzce.com/4104-lyudmila-sokolova-valeriya-belova-zhit.html' class='track-dl'>...</a>
Line 190
<a href='https://muzce.com/644-poshlaya-molli-spat-s-toboj.html' class='track-dl'>...</a>
Line 200

https://muzce.com/

CriticalThis button element contains no text and has no accessible name. WCAG A 4.1.2 508 A 4.1.2 1 pages

A programmatically determined name allows screen readers to tell users what the control does. To add a name do one of the following:

  • Add text between the button start and end tags
  • Add a title attribute
  • Add an aria-label attribute
  • Add an aria-labelledby attribute
  • Add an img alt attribute if the button contains an img element
<button type='submit'><span class='fas fa-search'></span></button>
Line 90

https://muzce.com/

Criticalul elements must contain either an li element or an element with role=listitem and must not contain elements with other roles. ARIA 5.2.6 WCAG A 1.3.1 508 A 1.3.1 1 pages
Invalid roles: link from element a
<ul class='track-nav'><div class='track-item-pop fx-...'>...</div>...</ul>
Line 114
Invalid roles: link from element a
<ul class='track-nav'><div class='track-item-pop fx-...'>...</div>...</ul>
Line 743

https://muzce.com/

CriticalUse HTML headings instead of applying CSS heading styles to non-headings. WCAG A F2 WCAG 1.3.1 508 A F2 1 pages
Screen reader users rely on headings to navigate within pages. Either add role=heading with aria-level or use h1-h6 elements to identify the element as a heading to screen readers. 
<div class='side-bt'>Категории</div>
Line 733

https://muzce.com/

Level AA

1 issues on 1 pages

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

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)
:focus has outline: invert none 0px 
<a class='track-desc fx-1' href='...akone-kiliana-zhiganskaya.html'>...</a>
Line 154
:focus has outline: invert none 0px 
<a href='...akone-kiliana-zhiganskaya.html' class='track-dl'>...</a>
Line 160
:focus has outline: invert none 0px 
<a class='track-desc fx-1' href='...or-tancuj-devochka-tancuj.html'>...</a>
Line 164
:focus has outline: invert none 0px 
<a href='...or-tancuj-devochka-tancuj.html' class='track-dl'>...</a>
Line 170
:focus has outline: invert none 0px 
<a class='track-desc fx-1' href='...e.com/10997-ganvest-dyrka.html'>...</a>
Line 174

https://muzce.com/

Level AAA

3 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='...ps://www.liveinternet.ru/click' target='_blank'>...</a>
Line 669

https://muzce.com/

ImportantClickable targets must be at least 44 by 44 CSS pixels. WCAG 2.5.5 1 pages
160 x 40 pixels 
<button id='dmca-alert' class='form-btn dmca-btn'>Жалоба DMCA</button>
Line 767
160 x 40 pixels 
<button id='song-alert' class='form-btn song-btn'>...</button>
Line 767

https://muzce.com/

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:
5.38 with color: rgb(139,148,158)background: rgba(255,255,255,2.0%)
font-size: 11.25ptfont-weight: 400
<div class='track-subtitle ...'>Жиганская</div>
Line 156
5.38 with color: rgb(139,148,158)background: rgba(255,255,255,2.0%)
font-size: 10.50ptfont-weight: 400
<div class='track-time'>02:08</div>
Line 159
5.62 with color: rgb(139,148,158)background: rgb(22,27,34)
font-size: 11.25ptfont-weight: 400
<div class='track-subtitle ...'>Танцуй девочка танцуй</div>
Line 166
5.62 with color: rgb(139,148,158)background: rgb(22,27,34)
font-size: 10.50ptfont-weight: 400
<div class='track-time'>04:57</div>
Line 169
5.38 with color: rgb(139,148,158)background: rgba(255,255,255,2.0%)
font-size: 11.25ptfont-weight: 400
<div class='track-subtitle ...'>Дырка</div>
Line 176

https://muzce.com/

Expand all 9 issues