Public accessibility assessment

Accessibility issues detected on wr-tech.pl

Evolize inspected 5 public pages on wr-tech.pl and detected 30 automatically identifiable accessibility findings.

30Findings detected

8WCAG criteria affected

5Pages inspected

21 Aug 2026Assessment date

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

Most widespread issueButtons have no accessible nameDetected on 5 inspected pages

Most affected page/25 findings detected

Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)14 detected findings

Is wr-tech.pl your website?

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

MONITOR THIS WEBSITE RUN A FREE ASSESSMENT

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on wr-tech.pl and detected 30 accessibility findings. The most widespread issue was "Buttons have no accessible name", detected on 5 inspected pages. The most affected inspected page was "/", where 25 findings were detected. The assessment identified findings mapped to 8 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.

Critical
Buttons have no accessible name
WCAG 4.1.2 (A) · 5 inspected pages · 5 instances
Why this matters
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Recommended action
Add an accessible name to the button, either by including text within the button element or by using the aria-label attribute. For example: <button class="search-submit" type="submit" role="button" aria-label="Search"> <img src="https://wr-tech.pl/wp-content/themes/prime-basic/img/lupa.svg"> </button>
View technical evidence →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 5 inspected pages · 45 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
To fix this issue, ensure that elements which are not visible do not remain in the tab order. This can be achieved by setting the 'tabindex' attribute to '-1' or by removing the element from the DOM when it is not visible.
View technical evidence →
High
Form fields use placeholder text as the only label
WCAG 1.3.1 (A) · 5 inspected pages · 10 instances
Why this matters
Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.
Recommended action
To fix this issue, add a visible and programmatic label to the form field. This can be achieved by adding a label element with a 'for' attribute matching the input's 'id' attribute. For example: <label for='search-input'>Search</label> <input class='search-input' type='search' id='search-input' name='szukaj' placeholder='szukaj'>
View technical evidence →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 5 inspected pages · 10 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
To fix this issue, ensure that the element is either visible when it receives focus or is removed from the tab order. This can be achieved by adding 'tabindex="-1"' to the element or by making it visible when focused.
View technical evidence →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 5 inspected pages · 10 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
To fix this issue, ensure that the hidden element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using the 'display: none' or 'visibility: hidden' CSS properties to hide it. For example: <input class="search-input" type="search" name="szukaj" placeholder="szukaj" style="display: none;"> or <input class="search-input" type="search" name="szukaj" placeholder="szukaj" tabindex="-1">
View technical evidence →

03 · WCAG criteria affected

Criterion	Name	Level	Findings	Pages	Reach
1.4.3	Contrast (Minimum)	AA	14	5	5 / 5
2.5.8	Target Size (Minimum)	AA	8	5	5 / 5
2.4.3	Focus Order	A	3	5	5 / 5
1.3.1	Info and Relationships	A	2	5	5 / 5
1.1.1	Non-text Content	A	1	5	5 / 5
2.4.1	Bypass Blocks	A	1	5	5 / 5
3.3.2	Labels or Instructions	A	1	5	5 / 5
4.1.2	Name, Role, Value	A	1	5	5 / 5

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

04 · All detected findings

Critical

Buttons have no accessible name

WCAG 4.1.2 (A)5 instances5 inspected pages

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Why it matters

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Recommended correction

Add an accessible name to the button, either by including text within the button element or by using the aria-label attribute. For example: <button class="search-submit" type="submit" role="button" aria-label="Search"> <img src="https://wr-tech.pl/wp-content/themes/prime-basic/img/lupa.svg"> </button>

View 5 affected elements

Component · Ref 4V6COX

Affected pagehttps://wr-tech.pl/

Element.search-submit

Rolebutton

Markup

<button class="search-submit" type="submit" role="button">
        <img src="https://wr-tech.pl/wp-content/themes/prime-basic/img/lupa.svg">
    </button>

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

High

Text has insufficient colour contrast

WCAG 1.4.3 (AA)56 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 readability, consider adjusting the color scheme to meet the minimum contrast ratio of 4.5:1 for normal text. For this specific issue, update the CSS styles for the '.header__button.cbtn.cbtn--red' class to use a background color or text color that provides sufficient contrast.

View 56 affected elements

Component · Ref S2LS13

Affected pagehttps://wr-tech.pl/

Element.header__button

Accessible nameSKLEP

Markup

<a class="header__button cbtn cbtn--red" href="https://sklep.wr-tech.pl/" target="_blank">SKLEP</a>

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Component · Ref C6KP8H

Affected pagehttps://wr-tech.pl/sections/section-contact-with-map/

Elementh3 > span

Accessible nameWR

Markup

<span style="color: #ff010b;">WR</span>

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Component · Ref 45A13L

Affected pagehttps://wr-tech.pl/

Element.wr-section--steps__step:nth-child(1) > .cbtn--red.cbtn

Accessible nameZobacz ROZWIĄZANIA do demontażu

Markup

<a class="cbtn cbtn--red" href="https://sklep.wr-tech.pl/produkt/wr5003/">Zobacz ROZWIĄZANIA do demontażu</a>

Component · Ref 3LN5EG

Affected pagehttps://wr-tech.pl/

Element.wr-section--cross-blog__item.link-box:nth-child(1) > .wr-section--cross-blog__item-button

Accessible namePRZEJDŹ DO CENTRUM WIEDZY >

Markup

<span class="wr-section--cross-blog__item-button">
                            PRZEJDŹ DO CENTRUM WIEDZY &gt;
                        </span>

Component · Ref NITO0N

Affected pagehttps://wr-tech.pl/category/bez-kategorii/

Elementa[title="Pasta miedziana czy aerozol?"]

Accessible namePasta miedziana czy aerozol?

Markup

<a href="https://wr-tech.pl/bez-kategorii/pasta-miedziana-czy-aerozol/" title="Pasta miedziana czy&nbsp;aerozol?">Pasta miedziana czy&nbsp;aerozol?</a>

Component · Ref QBZEYH

Affected pagehttps://wr-tech.pl/category/bez-kategorii/

Element#post-2260 > .blog_txt > p > a

Accessible nameDlaczego śruba mimo użycia smaru nadal się zapieka?

Markup

<a href="https://wr-tech.pl/bez-kategorii/jak-skutecznie-odtluscic-powierzchnie/" title="Dlaczego śruba mimo użycia smaru nadal się zapieka?">Dlaczego śruba mimo użycia smaru nadal się zapieka?</a>

Component · Ref F2WY1N

Affected pagehttps://wr-tech.pl/

Element.wr-section--content-section.wr-section--white-text.wr-section:nth-child(5) > .container > .wr-section__head > h2 > span

Accessible nameWR

Markup

<span style="color: #ff010b;">WR</span>

Component · Ref OZ10X6

Affected pagehttps://wr-tech.pl/

Elementh2[data-animation_delay="500"]

Accessible nameSkróć czas demontażu. Zabezpiecz połączenia. Ogranicz przestoje.

Markup

<h2 class="prime-animation" data-animation="fadeInDown" data-animation_delay="500">Skróć czas demontażu. Zabezpiecz połączenia. Ogranicz przestoje.</h2>

Component · Ref EHABVJ

Affected pagehttps://wr-tech.pl/

Element.slide-description > p

Accessible nameWRTech to zintegrowany system rozwiązań wspierający utrzymanie ruchu oraz serwisy techniczne w wymagających warunkach pracy. Łączymy skuteczne preparaty z praktycznymi procedurami, pomagając przyspieszyć prace serwisowe i zwiększyć trwałość połączeń.

Markup

<p>WRTech to zintegrowany system rozwiązań wspierający utrzymanie ruchu oraz serwisy techniczne w&nbsp;wymagających warunkach pracy. Łączymy skuteczne preparaty z&nbsp;praktycznymi procedurami, pomagając przyspieszyć prace serwisowe i&nbsp;zwiększyć trwałość połączeń.</p>

Component · Ref 4FP319

Affected pagehttps://wr-tech.pl/

Element.wr-section--content-section.wr-section--white-text.wr-section:nth-child(5) > .container > .wr-section__head > h2

Accessible nameRozwiązaniom technicznym WRTech zaufały firmy z różnych branż przemysłowych.

Markup

<h2>Rozwiązaniom technicznym <span style="color: #ff010b;">WR</span>Tech zaufały firmy z&nbsp;różnych branż przemysłowych.</h2>

Component · Ref IN36TC

Affected pagehttps://wr-tech.pl/

Element.content > a[href$="#kroki"]

Accessible nameZOBACZ ROZWIĄZANIA WRTECH

Markup

<a class="cbtn cbtn--red link-box" href="#kroki">ZOBACZ ROZWIĄZANIA WRTECH</a>

Component · Ref N0U7EE

Affected pagehttps://wr-tech.pl/

Element.content-60 > .container > .wr-section--content-section__content > p

Accessible nameRozwiązania WRTech zostały opracowane jako zintegrowany system wspierający utrzymanie ruchu, serwisy techniczne oraz przemysł wszędzie tam, gdzie kluczowe znaczenie ma szybki demontaż, trwałe zabezpieczenie i ograniczenie przestojów produkcyjnych. Nasze produkty nie są przypadkowym zbiorem preparatów – stanowią element spójnego procesu technologicznego, którego celem jest zwiększenie bezpieczeństwa pracy, trwałości połączeń oraz efektywności działań serwisowych.

Markup

<p>

Component · Ref 5A4IX3

Affected pagehttps://wr-tech.pl/

Element.content-60 > .container > .wr-section__head > h2

Accessible nameZobacz pełną ofretę sklepu WRTECH

Markup

<h2 style="text-align: left;">Zobacz pełną ofretę sklepu&nbsp;<span style="color: #ff010b;">WR</span>TECH</h2>

Component · Ref WQA18H

Affected pagehttps://wr-tech.pl/

Element.content-60 > .container > .wr-section__head > h2 > span

Accessible nameWR

Markup

<span style="color: #ff010b;">WR</span>

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)65 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

To fix this issue, ensure that the element is either visible when it receives focus or is removed from the tab order. This can be achieved by adding 'tabindex="-1"' to the element or by making it visible when focused.

View 65 affected elements

Component · Ref KK3FBO

Affected pagehttps://wr-tech.pl/

Elementdiv:nth-of-type(1) > div > div:nth-of-type(2) > ul > li > a

Accessible nameWszystkie produkty

Markup

<a class="cbtn cbtn--blue-dark" href="https://sklep.wr-tech.pl/sklep/">Wszystkie produkty</a>

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Component · Ref OT417R

Affected pagehttps://wr-tech.pl/

Elementheader > div:nth-of-type(1) > div > div:nth-of-type(2) > form > input

Markup

<input class="search-input" type="search" name="szukaj" placeholder="szukaj">

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Component · Ref UL1SO9

Affected pagehttps://wr-tech.pl/

Elementli#menu-item-2298 > a

Accessible nameKorozja

Markup

<a href="https://sklep.wr-tech.pl/sklep/czyszczenie-i-przygotowanie-podloza/"><span class="title">Korozja</span><span class="arrow"></span></a>

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

High

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)10 instances5 inspected pages

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Why it matters

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Recommended correction

To fix this issue, add a visible and programmatic label to the form field. This can be achieved by adding a label element with a 'for' attribute matching the input's 'id' attribute. For example: <label for='search-input'>Search</label> <input class='search-input' type='search' id='search-input' name='szukaj' placeholder='szukaj'>

View 10 affected elements

Component · Ref DM5AJI

Affected pagehttps://wr-tech.pl/sections/section-contact-with-map/

Elementheader > div:nth-of-type(1) > div > div:nth-of-type(2) > form > input

Markup

<input class="search-input" type="search" name="szukaj" placeholder="szukaj">

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

High

Images lack text alternatives

WCAG 1.1.1 (A)5 instances5 inspected pages

Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.

Why it matters

Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.

Recommended correction

Add an alt attribute to the img tag, for example: <img src="https://wr-tech.pl/wp-content/themes/prime-basic/img/lupa.svg" alt="Search icon">

View 5 affected elements

Component · Ref U9G2TK

Affected pagehttps://wr-tech.pl/

Element.search-submit > img

Markup

<img src="https://wr-tech.pl/wp-content/themes/prime-basic/img/lupa.svg">

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Medium

No skip link to main content

WCAG 2.4.1 (A)10 instances5 inspected pages

The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.

Why it matters

The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.

Recommended correction

Add a skip link to the main content of the page, allowing keyboard users to bypass the navigation. This can be achieved by adding an anchor link with a visible or hidden target that jumps to the main content section.

View 10 affected elements

Component · Ref DV7EMC

Affected pagehttps://wr-tech.pl/sections/section-contact-with-map/

Elementhtml > body

Accessible nameWszystkie produkty SKLEP Strona główna Oferta Korozja Odrdzewiacz molibdenowy WR5001 520ml Penetrant Strong WR5003 520ml Smarowanie Smar EP WR300–KG 650ml Smar do lin i łańcuchów WR500 650ml Smar wielozadaniowy WR1000 650ml Spray do pasów klinowych WR1001 520ml Smar miedziany WR1100 520ml SUCHY SMAR PTFE WR3001 Spray wiercenie/gwintowanie WR3004 520ml Odtłuszczanie Zmywacz Przemysłowy WR3000 650ml Środek do usuwania farb i uszczelek WR3003 520ml Inne Zamrażacz ICE TECH 1000 520ml Tester szczelności WR5010 520ml Technologie Centrum wiedzy Jak działa system WRTECH? Kontakt Oferta Technologie Centrum wiedzy Jak działa system WRTech? Kontakt POLITYKA PRYWATNOŚCI Rozwiązaniom technicznym WRTech zaufały firmy z różnych branż przemysłowych. function newsletterPD(){ let pdn_fconts = document.getElementsByClassName('pdn--register-form--container'); Array.from(pdn_fconts).forEach(fcont => { let form = fcont.querySelector('form'); let info = form.querySelector('.pdn_user_info'); let type = form.querySelector('.pdn_form_type'); let button = form.querySelector('button'); var respone_field = fcont.querySelector('.pdn--response'); form.addEventListener('submit', (e) => { e.preventDefault(); data = { action: 'pdn_add_user', user_info: info.value, form_type: type.value }; let r; let response = jQuery.ajax({ url: 'https://wr-tech.pl/wp-admin/admin-ajax.php', data: data, type: 'POST', beforeSend: function () { respone_field.innerHTML = ''; respone_field.classList.remove('success'); button.classList.add('loading'); respone_field.classList.remove('display'); }, complete: function( response ) { button.classList.remove('loading'); respone_field.classList.add('display'); if (response.responseText == 'success') { respone_field.classList.add('success'); if (type.value == "email") { respone_field.innerHTML = "Dziękujemy za zapis do newslettera! <br /> Email potwierdzający został wysłany na adres: <span>"+info.value+"</span>"; } else { respone_field.innerHTML = "Pomyślnie zapisano numer telefonu. Dziękujemy za kontakt!"; } } else if (response.responseText == 'error data') { respone_field.classList.add('error'); respone_field.innerHTML = 'Wystąpił błąd. Podano nieprawidłowe dane.'; } else if (response.responseText == 'error exists') { respone_field.classList.add('error'); respone_field.classList.add('exists'); if (type.value == "email") { respone_field.innerHTML = 'Przepraszamy, twój adres email został już wykorzystany'; } else { respone_field.innerHTML = "Przepraszamy, twój numer telefonu został już wkorzystany"; } } } }); }); }); }; if (document.readyState === "complete" || document.readyState === "interactive") { setTimeout(newsletterPD, 100); } else { document.addEventListener("DOMContentLoaded", newsletterPD); } Strona korzysta z plików cookie w celu realizacji usług zgodnie z polityką prywatności i ochroną danych osobowych. Możesz określić warunki przechowywania lub dostępu do cookie w Twojej przeglądarce lub konfiguracji usługi. Zarządzaj preferencjami Zaakceptuj

Markup

<body><input type="hidden" id="data_primecookies" data-primecookies_gtm="" data-primecookis_pixel="" data-primecookies_bgc_general="#ffffff" data-primecookies_bgc_option="" data-primecookies_btn_bgc="#231e2e" data-primecookies_btn_txt_color="" data-primecookies_txt_color="" data-primecookies_nocookiesbtn="" data-primecookies_logo="" data-primecookies_if_timeout="" data-primecookies_require_txt="Są one niezbędne do umożliwienia działania głównych funkcji i funkcjonalności. Nie mogą zostać wyłączone w naszych systemach. Możesz ustawić swoją przeglądarkę w taki sposób, aby blokowała te pliki cook…

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)43 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 make it easier for users to activate by touch. Consider adding padding or increasing the size of the logo image.

View 43 affected elements

Component · Ref A9BBMU

Affected pagehttps://wr-tech.pl/sections/section-contact-with-map/

Elementdiv:nth-of-type(2) > header > div:nth-of-type(1) > div > div:nth-of-type(1) > a

Accessible namewr-tech-logo

Markup

<a href="https://wr-tech.pl">
                                <img loading="lazy" class="header__logo" src="https://wr-tech.pl/wp-content/uploads/2026/03/wr-tech-logo.svg" width="" height="" alt="wr-tech-logo">                            </a>

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Component · Ref 4SM49J

Affected pagehttps://wr-tech.pl/

Elementdiv#pd-cookie-plugin > div:nth-of-type(1) > p > a

Accessible namepolityką prywatności

Markup

<a href="//localhost:3000/polityka-prywatnosci/" style="color: rgb(35, 30, 46);">polityką prywatności</a>

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Component · Ref YE8PEY

Affected pagehttps://wr-tech.pl/sections/section-contact-with-map/

Elementli#menu-item-2341 > a

Accessible nameOferta

Markup

<a href="https://sklep.wr-tech.pl/sklep/"><span class="title">Oferta</span><span class="arrow"></span></a>

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Component · Ref QYL0ZA

Affected pagehttps://wr-tech.pl/category/bez-kategorii/

Elementarticle#post-2263 > div > p > a

Accessible namePasta miedziana czy aerozol?

Markup

<a href="https://wr-tech.pl/bez-kategorii/pasta-miedziana-czy-aerozol/" title="Pasta miedziana czy&nbsp;aerozol?">Pasta miedziana czy&nbsp;aerozol?</a>

Component · Ref CDF1C6

Affected pagehttps://wr-tech.pl/

Elementmain#strona-glowna > section:nth-of-type(6) > div > div:nth-of-type(2) > div:nth-of-type(4) > a

Accessible nameTRANSPORT

Markup

<a href="https://sklep.wr-tech.pl/sklep/motoryzacja/">TRANSPORT</a>

Medium

Touch targets are too small

WCAG 2.5.8 (AA)9 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 interactive controls to a minimum of 24x24 pixels to make them easier to tap or click, especially for users with motor impairments or those using touchscreens.

View 9 affected elements

Component · Ref LHLHY1

Affected pagehttps://wr-tech.pl/

Element.search-submit

Rolebutton

Markup

<button class="search-submit" type="submit" role="button">
        <img src="https://wr-tech.pl/wp-content/themes/prime-basic/img/lupa.svg">
    </button>

Affected pages/ /category/bez-kategorii /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

Component · Ref 3DZSN0

Affected pagehttps://wr-tech.pl/category/bez-kategorii/

Elementa[title="Pasta miedziana czy aerozol?"]

Accessible namePasta miedziana czy aerozol?

Markup

<a href="https://wr-tech.pl/bez-kategorii/pasta-miedziana-czy-aerozol/" title="Pasta miedziana czy&nbsp;aerozol?">Pasta miedziana czy&nbsp;aerozol?</a>

Component · Ref L086UQ

Affected pagehttps://wr-tech.pl/category/bez-kategorii/

Element#post-2260 > .blog_txt > p > a

Accessible nameDlaczego śruba mimo użycia smaru nadal się zapieka?

Markup

<a href="https://wr-tech.pl/bez-kategorii/jak-skutecznie-odtluscic-powierzchnie/" title="Dlaczego śruba mimo użycia smaru nadal się zapieka?">Dlaczego śruba mimo użycia smaru nadal się zapieka?</a>

Medium

Page has no level-one heading

WCAG 1.3.1 (A)8 instances4 inspected pages

The page exposes no <h1>, so its topic is not conveyed in the heading structure.

Why it matters

The page exposes no <h1>, so its topic is not conveyed in the heading structure.

Recommended correction

Add a level-one heading (h1) to the page to convey its topic and provide a clear structure for users with disabilities. This can be achieved by wrapping the main title or introductory text in an <h1> element.

View 8 affected elements

Component · Ref F4J4SB

Affected pagehttps://wr-tech.pl/sections/section-contact-with-map/

Elementhtml > body

Markup

<body><input type="hidden" id="data_primecookies" data-primecookies_gtm="" data-primecookis_pixel="" data-primecookies_bgc_general="#ffffff" data-primecookies_bgc_option="" data-primecookies_btn_bgc="#231e2e" data-primecookies_btn_txt_color="" data-primecookies_txt_color="" data-primecookies_nocookiesbtn="" data-primecookies_logo="" data-primecookies_if_timeout="" data-primecookies_require_txt="Są one niezbędne do umożliwienia działania głównych funkcji i funkcjonalności. Nie mogą zostać wyłączone w naszych systemach. Możesz ustawić swoją przeglądarkę w taki sposób, aby blokowała te pliki cook…

Affected pages/ /blog /faq/przykladowe-pytanie /sections/section-contact-with-map

05 · Most affected inspected pages

/
Critical
26 findings
- Critical Buttons have no accessible name
- High Form fields use placeholder text as the only label
- High Hidden elements can still receive keyboard focus
- High Images lack text alternatives
- High Text has insufficient colour contrast
- Medium No skip link to main content
- Medium Page has no level-one heading
- Medium Touch targets are too small
- Medium Touch targets are too small on mobile
/category/bez-kategorii/Critical21 findings
/blog/Critical15 findings
/faq/przykladowe-pytanie/Critical15 findings
/sections/section-contact-with-map/Critical15 findings

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.

MONITOR THIS WEBSITE SEE PRICING

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

Accessibility issues detected on wr-tech.pl

Is wr-tech.pl your website?

01 · Accessibility summary

02 · Start here

Buttons have no accessible name

Hidden elements can still receive keyboard focus

Form fields use placeholder text as the only label

Hidden elements can still receive keyboard focus

Hidden elements can still receive keyboard focus

03 · WCAG criteria affected

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

04 · All detected findings

Buttons have no accessible name

Text has insufficient colour contrast

Hidden elements can still receive keyboard focus

Form fields use placeholder text as the only label

Images lack text alternatives

No skip link to main content

Touch targets are too small on mobile

Touch targets are too small

Page has no level-one heading

05 · Most affected inspected pages

06 · About this assessment

07 · Continuous monitoring

Reports with similar accessibility findings