Skip to content
https://poznan.pl

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
43
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
F
Heading Hierarchy
Action
108 headings, 5 skip(s)
FIX
108 headings, 5 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Komunikaty
  • H5 Poznan.pl, oficjalna strona Miasta Poznania skipped
  • H5 Poznan.pl, oficjalna strona Miasta Poznania
  • H5 Poznan.pl, oficjalna strona Miasta Poznania
  • H5 Poznan.pl, oficjalna strona Miasta Poznania
  • H5 Poznan.pl, oficjalna strona Miasta Poznania
  • H5 Poznan.pl, oficjalna strona Miasta Poznania
  • H5 Poznan.pl, oficjalna strona Miasta Poznania
  • H1 Poznan.pl, oficjalna strona Miasta Poznania
  • H1 Poznan.pl, oficjalna strona Miasta Poznania duplicate H1
  • H4 Informacja o przetwarzaniu danych skipped
  • H4 Cenimy Twoją prywatność
  • H4 Wybrane pliki cookies:
  • H4 Cookies plików wideo
  • H4 Cookies wpływające na wydajność
  • H4 Funkcjonalne pliki
  • H4 Niezbędne pliki cookies
  • H2 menu
  • H2 Aktualności
  • H3 Informacje dodatkowe
  • H3 Trzecia urodzinowa sobota w CIR
  • H3 Gratka dla fanów motoryzacji
  • H3 Jubileusze par małżeńskich
  • H3 Rusza nabór do miejskiego programu stypendialnego
  • H3 Dzień Ziemi w Arsenale
  • H3 Prezydent Poznania spotkał się z mieszkańcami Woli
  • H4 Srebrny Fyrtel w maju
  • H4 Warsztaty o ptakach w Collegium Cieszkowskich
  • H4 Terytorialsi pomogą zabezpieczyć infrastrukturę Aquanetu
  • H4 Trzecia urodzinowa sobota w CIR
  • H4 Gratka dla fanów motoryzacji
  • H4 Jubileusze par małżeńskich
  • H4 Rusza nabór do miejskiego programu stypendialnego
  • H4 Dzień Ziemi w Arsenale
  • H4 Prezydent Poznania spotkał się z mieszkańcami Woli
  • H4 Lech Poznań UAM powalczy o finał Pucharu Polski
  • H4 Jak oderwać nastolatka od telefonu?
  • H4 Naprawa nawierzchni jezdni na ulicy Matejki
  • H4 Nowe drzewa na Świerczewie, Wildzie i Zielonym Dębcu
  • H4 Srebrny Fyrtel w maju
  • H4 Warsztaty o ptakach w Collegium Cieszkowskich
  • H4 Terytorialsi pomogą zabezpieczyć infrastrukturę Aquanetu
  • H4 Trzecia urodzinowa sobota w CIR
  • H4 Gratka dla fanów motoryzacji
  • H4 Jubileusze par małżeńskich
  • H4 Rusza nabór do miejskiego programu stypendialnego
  • H4 Dzień Ziemi w Arsenale
  • H4 Prezydent Poznania spotkał się z mieszkańcami Woli
  • H4 Lech Poznań UAM powalczy o finał Pucharu Polski
  • H4 Jak oderwać nastolatka od telefonu?
  • H4 Naprawa nawierzchni jezdni na ulicy Matejki
  • H4 Nowe drzewa na Świerczewie, Wildzie i Zielonym Dębcu
  • H4 Srebrny Fyrtel w maju
  • H4 Warsztaty o ptakach w Collegium Cieszkowskich
  • H4 Terytorialsi pomogą zabezpieczyć infrastrukturę Aquanetu
  • H2 blok treści
  • H2 Ważne Sprawy
  • H2 kontakt
  • H3 Bądź w kontakcie usługi do kontaktu z instytucjami miasta
  • H2 kontakt
  • H2 e-urząd
  • H3 E-urząd
  • H2 eurząd
  • H2 Plan Poznania
  • H2 plan
  • H4 Znajdź na mapie Poznania skipped
  • H5 Polecane warstwy
  • H2 Komunikaty Smart City
  • H2 Komunikacja miejska
  • H2 Wydarzenia
  • H3 Spektakl - Calineczka
  • H3 Spotkanie inauguracyjne Otwartego Klubu...
  • H3 Spektakl - Calineczka
  • H3 [WTM-IWD2026] Breaking the pattern -...
  • H3 Koncert - Nadęci - Męska Orkiestra Rozrywkowa
  • H3 Filmy, których nie było - piosenki, które zostają
  • H3 artykuł
  • H3 Wariacje na ptaki i inne instrumenty
  • H3 artykuł
  • H3 Kim jest Król Roger?
  • H3 artykuł
  • H3 Konkurs na Wydarzenie Muzyczne dla Dzieci
  • H3 artykuł
  • H3 NEXT FEST. Między gigami
  • H2 Video Poznań
  • H3 Więcej aktualności z Poznania
  • H4 Wybierz portal
  • H2 biuletyn
  • H4 Aktualności skipped
  • H3 artykuł
  • H3 Konsultacje w sprawie nocnej sprzedaży alkoholu
  • H3 artykuł
  • H3 XXXIII sesja Rady Miasta Poznania
  • H3 artykuł
  • H3 Miliony dla Teatru Polskiego
  • H3 artykuł
  • H3 Kontynuacja oceny realizacji budżetu
  • H3 Biuletyn Informacji Publicznej
  • H2 dziennik prezydenta
  • H3 Prezydent / Rada Miasta
  • H2 Nieruchomości na sprzedaż
  • H3 Nieruchomości na sprzedaż
  • H2 praca
  • H4 Praca skipped
  • H4 Zamówienia publiczne
  • H2 przetargi
  • H2 Zobacz również
  • H1 PLATFORMA POZNAN.PL duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

F
Alt Text Quality
Action
8 of 79 images have issues
FIX
8 of 79 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
5 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with generic alt text
Info::
14 image(s) with alt text over 125 characters
Info::
14 decorative image(s) correctly marked
Info::
43 image(s) with good alt text
79 images 43 good alt text 14 decorative 1 generic 7 missing
IssueCount
missing7 image(s)
generic1 image(s)
too long14 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Form Accessibility
Action
6 of 19 controls have issues
FIX
6 of 19 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <textarea id="chatbotKeypadUserInput">
Info::
13 control(s) properly labeled
19 controls
13 labeled
1 placeholder only
5 unlabeled
ControlTypeLabelMethod
#stringtextszukaj informacjifor/id
#stringtextszukaj informacjifor/id
#stringtextszukaj informacjifor/id
#stringtextszukaj informacjifor/id
#stringtextszukaj informacjifor/id
#stringtextszukaj informacjifor/id
#stringtextszukaj informacjifor/id
#stringtextszukaj informacjifor/id
selectselectWidget de idiomas del Traductoraria-label
#styled-checkbox-1checkboxWszystkiefor/id
#styled-checkbox-2checkboxRozszerzonefor/id
#styled-checkbox-3checkboxPodstawowefor/id
#id_ulica_street_lookuptextNazwa ulicyfor/id
#chatbotKeypadUserInputtextarea(Wpisz treść wiadomości)placeholder only
#goog-gt-votingInputSrcLangtext(none)none
#goog-gt-votingInputTrgLangtext(none)none
#goog-gt-votingInputSrcTexttext(none)none
#goog-gt-votingInputTrgTexttext(none)none
#goog-gt-votingInputVotetext(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<textarea id="chatbotKeypadUserInput">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Poznan.pl ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA
h1 PLATFORMA POZNAN.PL
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Komunikaty
1.12:1
#000000
on
#001325
needs 3.0:1 (large text)
24px · top of page (header area)
h2 menu
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Aktualności
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 blok treści
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ważne Sprawy
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 kontakt
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 kontakt
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 e-urząd
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 eurząd
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Plan Poznania
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 plan
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Komunikaty Smart City
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Komunikacja miejska
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Wydarzenia
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Video Poznań
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 biuletyn
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 dziennik prezydenta
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nieruchomości na sprzedaż
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 praca
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 PLATFORMA POZNAN.PL2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Komunikaty1.12:13.0:1
#000000
#001325
Fail
h2 menu2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Aktualności2.45:13.0:1
#000000
#4C4C4C
Fail
h2 blok treści2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Ważne Sprawy2.45:13.0:1
#000000
#4C4C4C
Fail
h2 kontakt2.45:13.0:1
#000000
#4C4C4C
Fail
h2 kontakt2.45:13.0:1
#000000
#4C4C4C
Fail
h2 e-urząd2.45:13.0:1
#000000
#4C4C4C
Fail
h2 eurząd2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Plan Poznania2.45:13.0:1
#000000
#4C4C4C
Fail
h2 plan2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Komunikaty Smart Cit…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Komunikacja miejska2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Wydarzenia2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Video Poznań2.45:13.0:1
#000000
#4C4C4C
Fail
h2 biuletyn2.45:13.0:1
#000000
#4C4C4C
Fail
h2 dziennik prezydenta2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Nieruchomości na sp…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 praca2.45:13.0:1
#000000
#4C4C4C
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

C
Lighthouse Accessibility Audits
Action
Score 74/100 — 8 failing, 25 passed
REVIEW
74

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.body-section > section.news-section > div#slider-mobile > div#progress-bar-slider-news-main-page div.body-section > section.news-section > div#slider-mobile > div#progress-bar-slider-news-main-page
section#events_main_section > div.events-block-container > div > div.progress-bar-events section#events_main_section > div.events-block-container > div > div.progress-bar-events
section.boxes-container > div.wrapper > div.wrapper > div#progress-bar-video section.boxes-container > div.wrapper > div.wrapper > div#progress-bar-video
div.body-container > div.body-section > section.slick-box-container > div#prog_bar div.body-container > div.body-section > section.slick-box-container > div#prog_bar

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#events_main_section > div.events-block-container > div > div.progress-bar-events section#events_main_section > div.events-block-container > div > div.progress-bar-events

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.herbLogoBody > div#submenu_mobile_head_0 > div#submenu_mobile_button_0 > button.submenu_mobile_arrow_box body.herbLogoBody > div#submenu_mobile_head_0 > div#submenu_mobile_button_0 > button.submenu_mobile_arrow_box
body.herbLogoBody > div#submenu_mobile_head_1 > div#submenu_mobile_button_1 > button.submenu_mobile_arrow_box body.herbLogoBody > div#submenu_mobile_head_1 > div#submenu_mobile_button_1 > button.submenu_mobile_arrow_box
body.herbLogoBody > div#submenu_mobile_head_2 > div#submenu_mobile_button_2 > button.submenu_mobile_arrow_box body.herbLogoBody > div#submenu_mobile_head_2 > div#submenu_mobile_button_2 > button.submenu_mobile_arrow_box
body.herbLogoBody > div#submenu_mobile_head_3 > div#submenu_mobile_button_3 > button.submenu_mobile_arrow_box body.herbLogoBody > div#submenu_mobile_head_3 > div#submenu_mobile_button_3 > button.submenu_mobile_arrow_box
body.herbLogoBody > div#submenu_mobile_head_4 > div#submenu_mobile_button_4 > button.submenu_mobile_arrow_box body.herbLogoBody > div#submenu_mobile_head_4 > div#submenu_mobile_button_4 > button.submenu_mobile_arrow_box
body.herbLogoBody > div#submenu_mobile_head_5 > div#submenu_mobile_button_5 > button.submenu_mobile_arrow_box body.herbLogoBody > div#submenu_mobile_head_5 > div#submenu_mobile_button_5 > button.submenu_mobile_arrow_box
div#slider-mobile > div.wrapper > div.slider-news-mainpage > button.slickslider-mobile-main-page-arrow-box div#slider-mobile > div.wrapper > div.slider-news-mainpage > button.slickslider-mobile-main-page-arrow-box
div#slider-mobile > div.wrapper > div.slider-news-mainpage > button.slickslider-mobile-main-page-arrow-box div#slider-mobile > div.wrapper > div.slider-news-mainpage > button.slickslider-mobile-main-page-arrow-box
div.events-block-container > div > div.events-block-slider > button.events-slickslider-mobile-arrow-box div.events-block-container > div > div.events-block-slider > button.events-slickslider-mobile-arrow-box
div.events-block-container > div > div.events-block-slider > button.events-slickslider-mobile-arrow-box div.events-block-container > div > div.events-block-slider > button.events-slickslider-mobile-arrow-box
div.wrapper > div.video-new-rows-box > section.box > button.slickslider-mobile-banner-arrow-box div.wrapper > div.video-new-rows-box > section.box > button.slickslider-mobile-banner-arrow-box
div.wrapper > div.video-new-rows-box > section.box > button.slickslider-mobile-banner-arrow-box div.wrapper > div.video-new-rows-box > section.box > button.slickslider-mobile-banner-arrow-box

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.event_link > div.event-link-img > div.image-events-main > img a.event_link > div.event-link-img > div.image-events-main > img
div#chatbot-widget-root > div.container > button.chatbot__avatar-positioner > img.chatbot__avatar-image div#chatbot-widget-root > div.container > button.chatbot__avatar-positioner > img.chatbot__avatar-image

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.slick-track > div#wideo_0 > div.box-youtube-iframe-wrapper > iframe.lazyload div.slick-track > div#wideo_0 > div.box-youtube-iframe-wrapper > iframe.lazyload

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.main-header-row1 > div.header-icons-smartcitycee-responsive > span.ue-span > a.icon div.main-header-row1 > div.header-icons-smartcitycee-responsive > span.ue-span > a.icon
div.wrapper > div.footer-container-block-01 > p.poznan_logo_wrapper > a.poznan_logo div.wrapper > div.footer-container-block-01 > p.poznan_logo_wrapper > a.poznan_logo

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Informacja o przetwarzaniu danych div#cookie-box-fixed > div#cookies-top-text > div#text_1 > h4
Znajdź na mapie Poznania div.box-container > div.column-container-plan > div.column > h4#id_ulica_city_header

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Trzecia urodzinowa sobota w CIR Jak się blubra po poznańsku? Czy da się namalo… div.slick-track > div#column_id_0 > article > a
Filmy, których nie było - piosenki, które zostają Michał od Kości - a dokładni… div.box-container-kultura-main > div > article.image-tile > a
21.04.2026 Konsultacje w sprawie nocnej sprzedaży alkoholu div.box_new_container > div.biuletyn-with-button > article.flex_column > a.builetyn_article
14.04.2026 XXXIII sesja Rady Miasta Poznania div.box_new_container > div.biuletyn-with-button > article.flex_column > a.builetyn_article
16.04.2026 Miliony dla Teatru Polskiego div.box_new_container > div.biuletyn-with-button > article.flex_column > a.builetyn_article
17.04.2026 Kontynuacja oceny realizacji budżetu div.box_new_container > div.biuletyn-with-button > article.flex_column > a.builetyn_article
Zobacz więcej ogłoszeń div.bip_main_page_container > div.row-1-1-new > section.box_new_container > a.button-navi-new
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes are valid and not misspelled
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback