Public accessibility assessment

Accessibility issues detected on audyty-stron-internetowych.pl

Evolize inspected 5 public pages on audyty-stron-internetowych.pl and detected 14 automatically identifiable accessibility findings.

14Findings detected
4WCAG criteria affected
5Pages inspected
29 Aug 2026Assessment date

Highest detected severity: Medium · 0 high-priority findings · 100% inspected-page coverage

Most widespread issueTouch targets are too small on mobileDetected on 5 inspected pages
Most affected page/11 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)8 detected findings

Is audyty-stron-internetowych.pl your website?

Keep this assessment current and get notified when new accessibility issues are detected.

https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on audyty-stron-internetowych.pl and detected 14 accessibility findings. The most widespread issue was "Touch targets are too small on mobile", detected on 5 inspected pages. The most affected inspected page was "/", where 11 findings were detected. The assessment identified findings mapped to 4 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.

02 · Start here

These findings combine the highest severity and broadest reach detected during this assessment.

  1. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 5 inspected pages · 31 instances
    Why this matters

    Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

    Recommended action

    Increase the size of the touch target to at least 24x24px to ensure that it can be easily activated by touch on mobile devices. Consider adding padding or increasing the size of the button element with the class 'toolbar-group-btn'.

    View technical evidence →
  2. Medium

    Text has insufficient colour contrast

    WCAG 1.4.3 (AA) · 5 inspected pages · 13 instances
    Why this matters

    Text and background colours do not meet the minimum contrast ratio, reducing legibility.

    Recommended action

    To improve accessibility, increase the contrast between the text color and the background color. Ensure the contrast ratio meets the minimum requirements of WCAG 2.1 SC 1.4.3. Consider using a color contrast analyzer tool to determine the optimal colors.

    View technical evidence →
  3. Medium

    Navigation regions are not distinguishable

    WCAG 1.3.1 (A) · 5 inspected pages · 10 instances
    Why this matters

    The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

    Recommended action

    Add an accessible name to the navigation region using the aria-label attribute, e.g., <nav aria-label="Main Navigation">

    View technical evidence →
  4. Medium

    Text has insufficient colour contrast

    WCAG 1.4.3 (AA) · 5 inspected pages · 10 instances
    Why this matters

    Text and background colours do not meet the minimum contrast ratio, reducing legibility.

    Recommended action

    To improve the accessibility of the text, consider increasing the contrast between the text color and the background color. This can be achieved by changing the text color, background color, or both. A contrast ratio of at least 4.5:1 for normal text and 7:1 for larger text (18pt or 14pt bold) is recommended.

    View technical evidence →
  5. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 5 inspected pages · 5 instances
    Why this matters

    Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

    Recommended action

    Increase the size of the touch target to at least 24x24px to make it easier for users to activate by touch. Consider adding padding or increasing the font size of the interactive element.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA855 / 5
2.5.8Target Size (Minimum)AA355 / 5
2.4.3Focus OrderA211 / 5
1.3.1Info and RelationshipsA155 / 5

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

Continuous monitoring

A scan shows today's exposure. Monitoring shows what changes next.

Evolize continuously reassesses public website pages, detects newly introduced or recurring accessibility findings, and tracks remediation over time.

04 · All detected findings

Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)38 instances5 inspected pages

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Why it matters

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Recommended correction

To improve the accessibility of this element, consider increasing the contrast between the text color and the background color. This can be achieved by changing the CSS styles for the text or background elements. A contrast ratio of at least 4.5:1 for normal text is recommended.

View 38 affected elements
Component · Ref BWPOQN
Affected pagehttps://www.audyty-stron-internetowych.pl/
Elementfooter > p
Accessible nameOdsłuchaj: Copyright Copyright © 2015–2026 Barbara Cholewa. All rights reserved.
Markup
<p>
Affected pages/ /kontrola/ocena-kodu-stron.html /referencje.html /polityka-plikow-cookies.html /referencje/referencje-wiktor-cichecki.html
Component · Ref 92J5MQ
Affected pagehttps://www.audyty-stron-internetowych.pl/
Elementtext[x="10"]
Accessible nameAudyt strony www
Markup
<text filter="url(#dropShadow)" font-size="36" x="10" y="44">Audyt strony www</text>
Affected pages/ /kontrola/ocena-kodu-stron.html /referencje.html /polityka-plikow-cookies.html /referencje/referencje-wiktor-cichecki.html
Component · Ref CQU48O
Affected pagehttps://www.audyty-stron-internetowych.pl/
Elementspan[itemprop="copyrightYear"]
Accessible name2015
Markup
<span itemprop="copyrightYear">2015</span>
Affected pages/ /kontrola/ocena-kodu-stron.html /referencje.html /polityka-plikow-cookies.html /referencje/referencje-wiktor-cichecki.html
Component · Ref KM3MBM
Affected pagehttps://www.audyty-stron-internetowych.pl/polityka-plikow-cookies.html
Elementp > span:nth-child(5)
Accessible nameBarbara Cholewa
Markup
<span itemprop="author copyrightHolder publisher">Barbara Cholewa</span>
Affected pages/kontrola/ocena-kodu-stron.html /referencje.html /polityka-plikow-cookies.html /referencje/referencje-wiktor-cichecki.html
Component · Ref F8XT5P
Affected pagehttps://www.audyty-stron-internetowych.pl/
Elementfooter > p > span[lang="en"][itemprop="name"]
Accessible nameCopyright
Markup
<span itemprop="name" lang="en">Copyright</span>
Component · Ref QQCEDT
Affected pagehttps://www.audyty-stron-internetowych.pl/
Elementtext[fill="rgb(247,208,66)"]
Accessible namezlecasz . . .
Markup
<text class="bg-white-c-black" fill="rgb(247,208,66)" filter="url(#dropShadow)" font-family="Georgia,Tahoma,sans-serif" font-size="74" stroke="rgb(81,72,92)" stroke-miterlimit="3" stroke-width="3" x="0" y="100">zlecasz . . .</text>
Component · Ref EZ9GTG
Affected pagehttps://www.audyty-stron-internetowych.pl/
Element.bg-white-c-green
Accessible namei wiesz na czym stoisz!
Markup
<text class="bg-white-c-green" fill="rgb(0,73,0)" filter="url(#dropShadow)" font-family="sans-serif" font-size="36" stroke="silver" x="0" y="195">i wiesz na czym stoisz!</text>
Component · Ref UAI9JO
Affected pagehttps://www.audyty-stron-internetowych.pl/
Element.bg-white-c-gray
Accessible namehttps://www.audyty-stron-internetowych.pl
Markup
<text class="bg-white-c-gray" fill="rgb(81,72,92)" font-family="sans-serif" font-size="19.4" stroke="silver" x="0" y="225">https://www.audyty-stron-internetowych.pl</text>
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)39 instances5 inspected pages

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Why it matters

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Recommended correction

Increase the size of the touch target to at least 24x24px to ensure that it can be easily activated by touch on mobile devices. Consider adding padding or increasing the size of the button element with the class 'toolbar-group-btn'.

View 39 affected elements
Component · Ref WJY1KF
Affected pagehttps://www.audyty-stron-internetowych.pl/
Elementbutton#basicletterSpacing
Accessible nameabc
Markup
<button class="toolbar-group-btn" id="basicletterSpacing" data-id="letterSpacing" data-tooltip="abc: wybierz podstawowy odstęp między fontami" data-value="normal" title="abc: wybierz podstawowy odstęp między fontami" type="button"><span class="toolbar-group-btn-icon">abc</span></button>
Affected pages/ /kontrola/ocena-kodu-stron.html /referencje.html /polityka-plikow-cookies.html /referencje/referencje-wiktor-cichecki.html
Component · Ref VA3GJ2
Affected pagehttps://www.audyty-stron-internetowych.pl/
Elementbody#label_top > a
Accessible nameSKIP NAVIGATION
Markup
<a href="#label_main-content" aria-label="SKIP NAVIGATION" class="skip-to-main" tabindex="0">Przejdź do treści</a>
Affected pages/ /kontrola/ocena-kodu-stron.html /referencje.html /polityka-plikow-cookies.html /referencje/referencje-wiktor-cichecki.html
Component · Ref 0L207A
Affected pagehttps://www.audyty-stron-internetowych.pl/
Elementinput#q
Accessible nameWpisz szukaną frazę
Markup
<input id="q" aria-controls="searchpanel" aria-invalid="true" autocapitalize="off" maxlength="256" name="q" placeholder="Wpisz szukaną frazę" required="" spellcheck="true" tabindex="0" title="Wpisz szukaną frazę" type="search">
Medium

Navigation regions are not distinguishable

WCAG 1.3.1 (A)10 instances5 inspected pages

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Why it matters

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Recommended correction

Add an accessible name to the navigation region using the aria-label attribute, e.g., <nav aria-label="Main Navigation">

View 10 affected elements
Component · Ref QLLWJP
Affected pagehttps://www.audyty-stron-internetowych.pl/
Elementbody#label_top > header > nav:nth-of-type(2)
Accessible nameStrona głównaReferencje KlientówRegulamin wydawcyPolityka prywatnościDeklaracja dostępnościMapa stron serwisu
Markup
<nav class="site-navbar" itemscope="" itemtype="https://schema.org/SiteNavigationElement"><meta itemprop="name" content="Site Navigation"><ol class="site-navbar-nav" data-inset="true" data-role="listview"><li class="canonical"><a href="#" itemprop="url" type="text/html">Strona główna</a></li><li><a href="referencje.html" itemprop="url" rel="next" title="Otrzymane referencje Klientów | Audyty stron internetowych" type="text/html">Referencje Klientów</a></li><li><a href="regulamin-wydawcy.html" itemprop="license" rel="author license" title="Regulamin wydawcy | Audyty stron internetowych" type="t…
Affected pages/ /kontrola/ocena-kodu-stron.html /referencje.html /polityka-plikow-cookies.html /referencje/referencje-wiktor-cichecki.html
Medium

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)14 instances1 inspected page

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Why it matters

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Recommended correction

To fix this issue, ensure that all interactive elements are visible when they receive keyboard focus. You can do this by setting 'display: none;' or 'visibility: hidden;' on the element when it's not intended to be interacted with, or by removing it from the tab order by setting 'tabindex="-1"'.

View 14 affected elements
Component · Ref T3UVZF
Affected pagehttps://www.audyty-stron-internetowych.pl/referencje/referencje-wiktor-cichecki.html
Elementp#ex1 > a
Accessible nameJednakże już po kilku dniach, Pani Barbara Cholewa przesłała mi w pełni profesjonalny, prawie trzydziestostronicowy audyt sklepu ortomedica.pl. Jego treść uwzględniała ustawienia serwera, funkcjonalność dla odbiorcy, widoczność w wyszukiwarkach internetowych, poprawność kodu stron i zgodność z wytycznymi Odsłuchaj: World Wide Web Consortium World Wide Web Consortium, Odsłuchaj: HyperText Markup Language HTML, Odsłuchaj: Cascading Style Sheets Specification CSS, Odsłuchaj: Web Content Accessibility Guidelines WCAG 2.0.
Markup
<a href="https://www.w3.org/" aria-labelledby="ex1" hreflang="en" itemprop="url" rel="external" type="text/html"><dfn id="w3c" lang="en">World Wide Web Consortium</dfn></a>
Component · Ref MVD9U4
Affected pagehttps://www.audyty-stron-internetowych.pl/referencje/referencje-wiktor-cichecki.html
Elementbutton#btnW3c
Accessible nameOdsłuchaj: World Wide Web Consortium
Markup
<button id="btnW3c" class="read" title="Czytaj na głos (odsłuchaj)" type="button"> <svg aria-labelledby="play_w3c" class="play" focusable="false" height="44" role="img" tabindex="-1" width="44" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><title id="play_w3c">Odsłuchaj: <span lang="en">World Wide Web Consortium</span></title><use xlink:href="#play" x="4" y="6"></use></svg> </button>

05 · Most affected inspected pages

06 · About this assessment

Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.

  • Publicly accessible surfaces only — no credentials, private systems, or source-code access.
  • Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
  • Results reflect the site at the scan date and may have changed since.

Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment

07 · Continuous monitoring

This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.

Is information in this report inaccurate or outdated? Request a correction or removal.