EVOLIZEDIGITAL RISK INTELLIGENCE
RUN FREE ASSESSMENT
RUN FREE ASSESSMENT
Public accessibility assessment

Accessibility issues detected on gopswartabol.pl

Evolize inspected 5 public pages on gopswartabol.pl and detected 27 automatically identifiable accessibility findings.

27Findings detected
4WCAG criteria affected
5Pages inspected
8 Sep 2026Assessment date

Highest detected severity: Critical · 10 high-priority findings · 100% inspected-page coverage

Most widespread issueHidden elements can still receive keyboard focusDetected on 5 inspected pages
Most affected page/statut21 findings detected
Most represented WCAG criterionWCAG 2.5.8 — Target Size (Minimum)12 detected findings

Is gopswartabol.pl your website?

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

ACTIVATE MONITORINGRUN A FREE ASSESSMENT
https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on gopswartabol.pl and detected 27 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 5 inspected pages. The most affected inspected page was "/statut", where 21 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. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 2 instances
    Why this matters

    Links expose no accessible name, so screen-reader users cannot determine their destination.

    Recommended action

    This link's only content is an image with no text alternative. Provide meaningful alternative text on the linked image (its alt attribute) that identifies the link's destination or purpose. The link points to https://www.wartaboleslawiecka.pl/.

    View technical evidence →
  2. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 2 instances
    Why this matters

    Links expose no accessible name, so screen-reader users cannot determine their destination.

    Recommended action

    This link's only content is an image with no text alternative. Provide meaningful alternative text on the linked image (its alt attribute) that identifies the link's destination or purpose. The link points to https://www.wartaboleslawiecka.pl/.

    View technical evidence →
  3. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 2 instances
    Why this matters

    Links expose no accessible name, so screen-reader users cannot determine their destination.

    Recommended action

    This link's only content is an image with no text alternative. Provide meaningful alternative text on the linked image (its alt attribute) that identifies the link's destination or purpose. The link points to https://www.wartaboleslawiecka.pl/.

    View technical evidence →
  4. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 2 instances
    Why this matters

    Links expose no accessible name, so screen-reader users cannot determine their destination.

    Recommended action

    This link's only content is an image with no text alternative. Provide meaningful alternative text on the linked image (its alt attribute) that identifies the link's destination or purpose. The link points to https://www.wartaboleslawiecka.pl/.

    View technical evidence →
  5. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 70 instances
    Why this 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 action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
2.5.8Target Size (Minimum)AA1255 / 5
1.4.3Contrast (Minimum)AA655 / 5
2.4.3Focus OrderA555 / 5
2.4.4Link Purpose (In Context)A444 / 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.

ACTIVATE MONITORINGSEE PRICING

04 · All detected findings

High

Text has insufficient colour contrast

WCAG 1.4.3 (AA)40 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

Increase the contrast ratio to at least 4.5:1 for normal text and 3:1 for large text.

View 40 affected elements
Component · Ref 075UHP
Affected pagehttps://gopswartabol.pl/statut/
Element#cn-notice-text
Accessible nameTa strona korzysta z niezbędnych i funkcjonalnych plików cookies, aby świadczyć usłygi na najwyższym poziomie. Pliki cookies są przechowywane na urządzeniu użytkownika i wykorzystywane przez przeglądarkę podczas wyświetlania strony. W każdym momencie można dokonać zmiany ustawień przeglądarki.
Markup
<span id="cn-notice-text" class="cn-text-container">
Affected pages/ /kadra /rodo /statut /sample-page
Component · Ref YWZIER
Affected pagehttps://gopswartabol.pl/kadra/
Elementlabel
Accessible nameSzukaj
Markup
<label class="wp-block-search__label" for="wp-block-search__input-2">Szukaj</label>
Affected pages/ /kadra /rodo /statut
Component · Ref LWL2K6
Affected pagehttps://gopswartabol.pl/
Elementh1
Accessible nameAktualności
Markup
<h1 class="page-header-title clr" itemprop="headline">Aktualności</h1>
Affected pages/ /kadra /rodo /statut /sample-page
Component · Ref EBXDJ4
Affected pagehttps://gopswartabol.pl/statut/
Elementspan[itemprop="name"] > a
Accessible nameStatut
Rolelink
Markup
<a href="https://gopswartabol.pl/statut/" role="link">Statut</a>
Affected pages/ /kadra /rodo /statut
Component · Ref YY44JG
Affected pagehttps://gopswartabol.pl/statut/
Element.wp-block-file__button
Accessible namePobierz
Rolelink
Markup
<a href="https://gopswartabol.pl/wp-content/uploads/2024/02/Dz.Urz_.Woj_.Doln-uchwala-nr-XIII.116.16-statut-GOPS.pdf" class="wp-block-file__button wp-element-button" download="" aria-describedby="wp-block-file--media-53529efc-bff8-4e1f-8f6f-4713ea2443ce" role="link">Pobierz</a>
Component · Ref 53FNVR
Affected pagehttps://gopswartabol.pl/sample-page
Element.breadcrumb-error
Accessible name404 nie znaleziono
Markup
<span class="breadcrumb-error">404 nie znaleziono</span>
High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)100 instances5 inspected pages

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

Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

View 100 affected elements
Component · Ref 00MMVC
Affected pagehttps://gopswartabol.pl/rodo/
Elementdiv#site-header-inner > div:nth-of-type(3) > a
Accessible nameMobile Menu
Rolelink
Markup
<a href="https://gopswartabol.pl/#mobile-menu-toggle" class="mobile-menu" aria-controls="mobile-dropdown" aria-expanded="false" aria-label="Mobile Menu" role="link">
							<div class="hamburger hamburger--boring" aria-hidden="true">
					<div class="hamburger-box">
						<div class="hamburger-inner"></div>
					</div>
				</div>
								<span class="oceanwp-text">Menu</span>
				<span class="oceanwp-close-text">Zamknij</span>
						</a>
Affected pages/ /kadra /rodo /statut /sample-page
Component · Ref X3UOUW
Affected pagehttps://gopswartabol.pl/kadra/
Elementul#menu-menu-1 > li:nth-of-type(2) > ul > li:nth-of-type(1) > a
Accessible namePomoc społeczna
Rolelink
Markup
<a href="https://gopswartabol.pl/pomoc-spoleczna/" role="link">Pomoc społeczna</a>
Affected pages/ /kadra /rodo /statut /sample-page
Component · Ref 15CASG
Affected pagehttps://gopswartabol.pl/sample-page
Elementli#menu-item-309 > a
Accessible nameJednorazowa zapomoga z tytułu urodzenia się dziecka
Rolelink
Markup
<a href="https://gopswartabol.pl/jednorazowa-zapomoga-z-tytulu-urodzenia-sie-dziecka/" class="menu-link" role="link"><span class="text-wrap">Jednorazowa zapomoga z tytułu urodzenia się dziecka</span></a>
Affected pages/ /kadra /rodo /statut /sample-page
Component · Ref 15CAXB
Affected pagehttps://gopswartabol.pl/kadra/
Elementul#menu-menu-1 > li:nth-of-type(2) > a > span
Markup
<span class="dropdown-toggle" tabindex="0"></span>
Affected pages/ /kadra /rodo /statut /sample-page
Medium

Positive tabindex disrupts focus order

WCAG 2.4.3 (A)10 instances5 inspected pages

Elements use tabindex greater than zero, overriding the natural DOM focus order in confusing ways.

Why it matters

Elements use tabindex greater than zero, overriding the natural DOM focus order in confusing ways.

Recommended correction

Remove positive tabindex values; rely on DOM order and tabindex=0 / -1 only.

View 10 affected elements
Component · Ref E3PD0X
Affected pagehttps://gopswartabol.pl/sample-page
Elementa#pojo-a11y-skip-content
Accessible namePrzejdź do treści
Rolelink
Markup
<a id="pojo-a11y-skip-content" class="pojo-skip-link pojo-skip-content" tabindex="1" accesskey="s" href="#content" role="link">Przejdź do treści</a>
Affected pages/ /kadra /rodo /statut /sample-page
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)67 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 this <a>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper. Observed size: 73 × 20 CSS pixels; required minimum: 24 × 24 CSS pixels.

View 67 affected elements
Component · Ref NQGEVF
Affected pagehttps://gopswartabol.pl/kadra/
Elementdiv#site-header-inner > div:nth-of-type(3) > a
Accessible nameMobile Menu
Rolelink
Markup
<a href="https://gopswartabol.pl/#mobile-menu-toggle" class="mobile-menu" aria-controls="mobile-dropdown" aria-expanded="false" aria-label="Mobile Menu" role="link">
							<div class="hamburger hamburger--boring" aria-hidden="true">
					<div class="hamburger-box">
						<div class="hamburger-inner"></div>
					</div>
				</div>
								<span class="oceanwp-text">Menu</span>
				<span class="oceanwp-close-text">Zamknij</span>
						</a>
Affected pages/ /kadra /rodo /statut /sample-page
Component · Ref X8DTBY
Affected pagehttps://gopswartabol.pl/kadra/
Elementheader > div > nav > ol > li:nth-of-type(1) > a
Accessible nameStrona Główna
Rolelink
Markup
<a href="https://gopswartabol.pl" rel="home" aria-label="Strona Główna" itemprop="item" role="link"><span itemprop="name"><i class=" icon-home" aria-hidden="true" role="img"></i><span class="breadcrumb-home has-icon">Strona Główna</span></span></a>
Affected pages/ /kadra /rodo /statut /sample-page
Component · Ref QD3PM
Affected pagehttps://gopswartabol.pl/rodo/
Elementdiv#outer-wrap > a
Accessible nameSkip to content
Rolelink
Markup
<a class="skip-link screen-reader-text" href="#main" role="link">Skip to content</a>
Affected pages/ /kadra /rodo /statut /sample-page
Component · Ref ALSYT4
Affected pagehttps://gopswartabol.pl/kadra/
Elementdiv > nav > ol > li:nth-of-type(2) > span > a
Accessible nameKadra
Rolelink
Markup
<a href="https://gopswartabol.pl/kadra/" role="link">Kadra</a>
Affected pages/ /kadra /rodo /statut
Component · Ref 184464
Affected pagehttps://gopswartabol.pl/kadra/
Elementdiv#block-49 > ul > li:nth-of-type(5) > a
Accessible name5 czerwiec 2026 – GOPS nieczynny
Rolelink
Markup
<a class="wp-block-latest-posts__post-title" href="https://gopswartabol.pl/5-czerwca-2026-gops-nieczynny/" role="link">5 czerwiec 2026 – GOPS nieczynny</a>
Affected pages/ /kadra /rodo /statut
Component · Ref JXK7PH
Affected pagehttps://gopswartabol.pl/statut/
Elementdiv#block-58 > p > a
Accessible nameTerminy wypłat
Rolelink
Markup
<a href="https://gopswartabol.pl/terminy-wyplat/" data-type="page" data-id="506" role="link">Terminy wypłat</a>
Affected pages/ /rodo /statut /sample-page
Component · Ref UIOAA7
Affected pagehttps://gopswartabol.pl/sample-page
Elementbutton#cn-close-notice
Accessible nameNie wyrażam zgody
Markup
<button type="button" id="cn-close-notice" data-cookie-set="accept" class="cn-close-icon" aria-label="Nie wyrażam zgody" tabindex="0"></button>
Affected pages/ /sample-page
Component · Ref 49I4U2
Affected pagehttps://gopswartabol.pl/statut/
Elementdiv#block-41 > div > div:nth-of-type(5) > div > p > a
Accessible nameGmina Warta Bolesławiecka
Rolelink
Markup
<a href="https://www.wartaboleslawiecka.pl/" target="_blank" rel="noreferrer noopener" role="link"><strong>Gmina Warta Bolesławiecka</strong></a>
Affected pages/kadra /statut
Component · Ref 8E2N58
Affected pagehttps://gopswartabol.pl/rodo/
Elementdiv#content > article > div > p:nth-of-type(3) > a
Accessible name[email removed]
Rolelink
Markup
<a href="mailto:[email removed]" role="link">[email removed]</a>
Affected pages/kadra /rodo
Low

Touch targets are too small

WCAG 2.5.8 (AA)6 instances2 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 this <a>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper.

View 6 affected elements
Component · Ref BDYPY2
Affected pagehttps://gopswartabol.pl/kadra/
Element.is-style-default > .wp-block-media-text__content > .wp-block-paragraph > a[rel="noreferrer noopener"][target="_blank"]
Accessible nameBiuletyn Informacji Publicznej
Rolelink
Markup
<a href="https://gopswartabol.bip.gov.pl/" target="_blank" rel="noreferrer noopener" role="link"><strong>Biuletyn Informacji Publicznej</strong></a>
Affected pages/kadra /statut
Component · Ref OXT1HX
Affected pagehttps://gopswartabol.pl/kadra/
Elementa[href$="empatia.mpips.gov.pl/"][rel="noreferrer noopener"][target="_blank"]
Accessible namePortal Informacyjno-Usługowy
Rolelink
Markup
<a href="https://empatia.mpips.gov.pl/" target="_blank" rel="noreferrer noopener" role="link"><strong>Portal Informacyjno-Usługowy</strong></a>
Affected pages/kadra /statut
Component · Ref OPCQM6
Affected pagehttps://gopswartabol.pl/statut/
Element.wp-block-media-text.is-stacked-on-mobile:nth-child(5) > .wp-block-media-text__content > .wp-block-paragraph > a[rel="noreferrer noopener"][target="_blank"]
Accessible nameGmina Warta Bolesławiecka
Rolelink
Markup
<a href="https://www.wartaboleslawiecka.pl/" target="_blank" rel="noreferrer noopener" role="link"><strong>Gmina Warta Bolesławiecka</strong></a>

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.

ACTIVATE MONITORINGSEE PRICING

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