Report

https://podmiot.kamilianie.eu/

Back to analysis
Export or download

Summary

The report is built from validator messages for the analysed pages.

  • Errors: 0
  • Warnings: 15
  • Information: 0
  • Analysed page view: Desktop (1280×720)
  • Basic Auth: disabled

Analysed files

  • HTML: 1

Results

Each time you change the selection, click ‘Apply filters’ to refresh the report view.

Report view

The choice changes how findings are grouped. It applies immediately, without the \u201cApply filters\u201d button.

One card may belong to several WCAG criteria or equivalent rules. Counters still show all occurrences.

Scope

Filtering works locally in the browser.

The selection narrows the report to a single page (URL).

Select a rule (title + code, e.g. ‘Links…’ (axe_link-in-text-block)).

The selection narrows the report to a single success criterion (e.g. 1.3.1).

Message level
WCAG level

This is an automated test result, not a full audit — verify each message manually in the context of the page.

Results for each address are collapsed. Expand a chosen address to see its messages, or use the “Expand all” button above.

https://podmiot.kamilianie.eu/ — errors: 0, warnings: 15, information: 0, total: 15

  • Text contrast needs manual review

    Level
    warning · WCAG 2.1 (AA) (axe_incomplete_color-contrast)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    The automated check could not measure the contrast of this text, so it is unknown whether the contrast is too low. The required minimum is 4.5:1 for normal text and 3:1 for large text (at least 18 pt, or 14 pt bold).
    Why it matters
    People with low vision, older users, and those using a screen in difficult conditions cannot read text with too low contrast. It is one of the most common and most easily measurable barriers.
    How to fix it
    Measure the contrast manually: sample the text colour and the background colour at that exact spot, then compare them with the required threshold. Only make changes if the result falls short.
    Why the automated check could not assess this
    Element content contains only non-text characters
    Automated check limitation
    Contrast measurement can be unreliable for text over an image or gradient - check such cases manually.
    — Rule details: Elements must meet minimum color contrast ratio thresholds, WCAG 1.4.3 WCAG: 1.4.3
    Validator details
    Fix at least one of the following issues:
    • Element content contains only non-text characters
    Message
    Elements must meet minimum color contrast ratio thresholds
    Text and context
    Text: ❮Poprzednie zdjęcie
    Context: ❮Poprzednie zdjęcie ❯Następne zdjęcie
    Location
    • Selector: 
      #heroPrev
    • XPath: 
      //*[@id="heroPrev"]
    • Position: x=82, y=460.7, w=44, h=44 (viewport 1280×720)
    • Alternative selectors:
      • #heroPrev
    HTML snippet 
    <button type="button" class="hero__ctrl hero__ctrl--prev" id="heroPrev" aria-label="Poprzednie zdjęcie">❮<span style="display:none">Poprzednie zdjęcie</span></button>
    HTML context 
    <section class="hero" aria-label="Zdjęcia z placówek Podmiotu"> <div class="hero__viewport" id="heroSlider"> <img class="hero__slide is-active" src="images/new-2A.jpg" alt="Leczenie w najwyższych standardach"> <img class="hero__slide" src="images/new-3.jpg" alt="Nowoczesne pracownie diagnostyczne"> <img class="hero__slide" src="images/new-4.jpg" alt="Indywidualne podejście do Pacjenta"> <img class="hero__slide" src="images/new-5.jpg" alt="Chronimy środowisko naturalne"> </div> <button type="button" class="hero__ctrl hero__ctrl--prev" id="heroPrev" aria-label="Poprzednie zdjęcie">❮<span style="display:none">Poprzednie zdjęcie</span></button> <button type="button" class="hero__ctrl hero__ctrl--next" id="heroNext" aria-label="Następne zdjęcie">❯<span style="display:none">Następne zdjęcie</span></button> </section>

  • Text contrast needs manual review

    Level
    warning · WCAG 2.1 (AA) (axe_incomplete_color-contrast)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    The automated check could not measure the contrast of this text, so it is unknown whether the contrast is too low. The required minimum is 4.5:1 for normal text and 3:1 for large text (at least 18 pt, or 14 pt bold).
    Why it matters
    People with low vision, older users, and those using a screen in difficult conditions cannot read text with too low contrast. It is one of the most common and most easily measurable barriers.
    How to fix it
    Measure the contrast manually: sample the text colour and the background colour at that exact spot, then compare them with the required threshold. Only make changes if the result falls short.
    Why the automated check could not assess this
    Element content contains only non-text characters
    Automated check limitation
    Contrast measurement can be unreliable for text over an image or gradient - check such cases manually.
    — Rule details: Elements must meet minimum color contrast ratio thresholds, WCAG 1.4.3 WCAG: 1.4.3
    Validator details
    Fix at least one of the following issues:
    • Element content contains only non-text characters
    Message
    Elements must meet minimum color contrast ratio thresholds
    Text and context
    Text: ❯Następne zdjęcie
    Context: ❮Poprzednie zdjęcie ❯Następne zdjęcie
    Location
    • Selector: 
      #heroNext
    • XPath: 
      //*[@id="heroNext"]
    • Position: x=1154, y=460.7, w=44, h=44 (viewport 1280×720)
    • Alternative selectors:
      • #heroNext
    HTML snippet 
    <button type="button" class="hero__ctrl hero__ctrl--next" id="heroNext" aria-label="Następne zdjęcie">❯<span style="display:none">Następne zdjęcie</span></button>
    HTML context 
    <section class="hero" aria-label="Zdjęcia z placówek Podmiotu"> <div class="hero__viewport" id="heroSlider"> <img class="hero__slide is-active" src="images/new-2A.jpg" alt="Leczenie w najwyższych standardach"> <img class="hero__slide" src="images/new-3.jpg" alt="Nowoczesne pracownie diagnostyczne"> <img class="hero__slide" src="images/new-4.jpg" alt="Indywidualne podejście do Pacjenta"> <img class="hero__slide" src="images/new-5.jpg" alt="Chronimy środowisko naturalne"> </div> <button type="button" class="hero__ctrl hero__ctrl--prev" id="heroPrev" aria-label="Poprzednie zdjęcie">❮<span style="display:none">Poprzednie zdjęcie</span></button> <button type="button" class="hero__ctrl hero__ctrl--next" id="heroNext" aria-label="Następne zdjęcie">❯<span style="display:none">Następne zdjęcie</span></button> </section>

  • Match between label and accessible name needs manual review

    Level
    warning · WCAG 2.1 (A) (axe_incomplete_label-content-name-mismatch)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    The automated check could not determine whether the visible label matches the name a screen reader announces.
    Why it matters
    A voice-control user speaks the visible caption to activate the element. When the accessible name does not contain it, the voice command fails; a screen reader user hears text different from what they see.
    How to fix it
    Compare the visible text with the name announced by a screen reader. The accessible name should contain the visible text.
    — Rule details: Elements must have their visible text as part of their accessible name, WCAG 2.5.3 WCAG: 2.5.3
    Text and context
    Text: ❮Poprzednie zdjęcie
    Context: ❮Poprzednie zdjęcie ❯Następne zdjęcie
    Location
    • Selector: 
      #heroPrev
    • XPath: 
      //*[@id="heroPrev"]
    • Position: x=82, y=460.7, w=44, h=44 (viewport 1280×720)
    • Alternative selectors:
      • #heroPrev
    HTML snippet 
    <button type="button" class="hero__ctrl hero__ctrl--prev" id="heroPrev" aria-label="Poprzednie zdjęcie">❮<span style="display:none">Poprzednie zdjęcie</span></button>
    HTML context 
    <section class="hero" aria-label="Zdjęcia z placówek Podmiotu"> <div class="hero__viewport" id="heroSlider"> <img class="hero__slide is-active" src="images/new-2A.jpg" alt="Leczenie w najwyższych standardach"> <img class="hero__slide" src="images/new-3.jpg" alt="Nowoczesne pracownie diagnostyczne"> <img class="hero__slide" src="images/new-4.jpg" alt="Indywidualne podejście do Pacjenta"> <img class="hero__slide" src="images/new-5.jpg" alt="Chronimy środowisko naturalne"> </div> <button type="button" class="hero__ctrl hero__ctrl--prev" id="heroPrev" aria-label="Poprzednie zdjęcie">❮<span style="display:none">Poprzednie zdjęcie</span></button> <button type="button" class="hero__ctrl hero__ctrl--next" id="heroNext" aria-label="Następne zdjęcie">❯<span style="display:none">Następne zdjęcie</span></button> </section>

  • Match between label and accessible name needs manual review

    Level
    warning · WCAG 2.1 (A) (axe_incomplete_label-content-name-mismatch)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    The automated check could not determine whether the visible label matches the name a screen reader announces.
    Why it matters
    A voice-control user speaks the visible caption to activate the element. When the accessible name does not contain it, the voice command fails; a screen reader user hears text different from what they see.
    How to fix it
    Compare the visible text with the name announced by a screen reader. The accessible name should contain the visible text.
    — Rule details: Elements must have their visible text as part of their accessible name, WCAG 2.5.3 WCAG: 2.5.3
    Text and context
    Text: ❯Następne zdjęcie
    Context: ❮Poprzednie zdjęcie ❯Następne zdjęcie
    Location
    • Selector: 
      #heroNext
    • XPath: 
      //*[@id="heroNext"]
    • Position: x=1154, y=460.7, w=44, h=44 (viewport 1280×720)
    • Alternative selectors:
      • #heroNext
    HTML snippet 
    <button type="button" class="hero__ctrl hero__ctrl--next" id="heroNext" aria-label="Następne zdjęcie">❯<span style="display:none">Następne zdjęcie</span></button>
    HTML context 
    <section class="hero" aria-label="Zdjęcia z placówek Podmiotu"> <div class="hero__viewport" id="heroSlider"> <img class="hero__slide is-active" src="images/new-2A.jpg" alt="Leczenie w najwyższych standardach"> <img class="hero__slide" src="images/new-3.jpg" alt="Nowoczesne pracownie diagnostyczne"> <img class="hero__slide" src="images/new-4.jpg" alt="Indywidualne podejście do Pacjenta"> <img class="hero__slide" src="images/new-5.jpg" alt="Chronimy środowisko naturalne"> </div> <button type="button" class="hero__ctrl hero__ctrl--prev" id="heroPrev" aria-label="Poprzednie zdjęcie">❮<span style="display:none">Poprzednie zdjęcie</span></button> <button type="button" class="hero__ctrl hero__ctrl--next" id="heroNext" aria-label="Następne zdjęcie">❯<span style="display:none">Następne zdjęcie</span></button> </section>

  • Content disappears in high-contrast mode

    Level
    warning · WCAG 2.1 (A/AA) (ace_style_highcontrast_visible)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    In forced-colors mode (Windows High Contrast/forced-colors) some content or indicators disappear - e.g. background images carrying information, borders defined only by background.
    Why it matters
    People using high-contrast mode (low vision) lose information conveyed by elements that are not rendered in that mode. An element may become invisible or indistinguishable.
    How to fix it
    Do not convey significant content only via a background image or background color. Use properties supported by forced-colors, and test the page in high-contrast mode.
    Automated check limitation
    This supports the use-of-color and contrast criteria; it is not a separate WCAG criterion. Confirm the actual behavior manually in high-contrast mode.
    — Rule details: Windows high contrast mode must be supported when CSS is used to include, position, or modify non-decorative content, WCAG 1.1.1, 1.3.2, 1.4.11 WCAG: 1.1.1, 1.3.2, 1.4.11
    Text and context
    Context: Podmiot Leczniczy Zakonu Ojców Kamilianów w Tarnowskich Górach - Podmiot Leczniczy Zakonu OO. Kamilianów if (top!=self) { top.location.href=self.location.href; } // podtrzymanie sesji (co ok. 14 minut) — bez zal…
    Location
    • XPath: 
      /html[1]/head[1]/link[3]
    • Position: x=0, y=0, w=0, h=0 (viewport 1280×720)
    HTML snippet 
    <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/layout/podmiot/css/style.css?v=1.0.6">
    HTML context 
    <head><meta content="pl_PL" property="og:locale"> <meta content="website" property="og:type"> <meta content="Zatrudnimy specjalistę w oddziale internistycznym" property="og:title"> <meta content="Szpital św. Kamilia w Tarnowskich Górach zatrudni specjalistę w oddziale internistycznym, warunki do omówienia. Praca stabilna, szpital przyjazny. Szczegóły pod numerami: 32 384 97 56, kom. 577 131 623, e-mail: centrum@kamilianie.eu" property="og:description"> <meta content="https://podmiot.kamilianie.eu/index.php?id=103&amp;zoom=15" property="og:url"> <meta content="Szpital św. Kamila" property="og:site_name"> <meta content="2026-08-07T12:10:17+00:00" property="article:modified_time"> <meta content="https://podmiot.kamilianie.eu/images/upload/lekarz.jpg" property="og:image"> <meta content="716" property="og:image:width"> <meta content="409" property="og:image:height"> <meta content="image/jpeg" property="og:image:type"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <!-- <meta name="Copyright" content="Zakon OO. Kamilianów w Polsce"> <meta name="Distribution" content="Global"> <meta name="Rating" content="General"> <meta name="Robots" content="All"> --> <meta name="revisit-after" content="2 days"> <meta name="reply-to" content="kamilianie@kamilianie.eu"> <meta http-equiv="X-UA-Compatible" content="IE=8"> <meta name="Author" content="Zakon OO. Kamilianów w Polsce"> <meta name="Classification" content="CMS"> <meta name="Description" content="Podmiotu Leczniczego Zakonu Ojców Kamilianów w Tarnowskich Górach."> <meta name="KeyWords" content="Szpital św. Kamila, Tarnowskie góry, Szpital, kamilianie, oddział wewnętrzny, pracownia holtera, laboratorium analityczne"> <meta name="Generator" content="SmodCMS"> <meta name="Authoring_Tool" content="SmodCMS // www.smod.pl"> <link href="//podmiot.kamilianie.eu/favicon.ico" rel="shortcut icon"> <link href="//podmiot.kamilianie.eu/favicon.ico" rel="bookmark icon"> <meta name="deklaracja-dostepnosci" content="https://podmiot.kamilianie.eu/index.php?id=176"> <title>Podmiot Leczniczy Zakonu Ojców Kamilianów w Tarnowskich Górach - Podmiot Leczniczy Zakonu OO. Kamilianów</title> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/layout/podmiot/css/style.css?v=1.0.6"> <!--[if IE]> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/layout/podmiot/css/stylemsie.css" /> <![endif]--> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/modules/artykuly/style.css"> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/modules/news/style.css"> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/modules/contact/style.css"> <script type="text/javascript" language="JavaScript" src="//podmiot.kamilianie.eu/add/js.js"></script><script type="text/javascript"> if (top!=self) { top.location.href=self.location.href; } </script> <script type="text/javascript"> // podtrzymanie sesji (co ok. 14 minut) — bez zaleznosci od MooTools window.setInterval(function () { fetch('index.php', { credentials: 'same-origin' }).catch(function () {}); }, 840000); </script> <script type="text/javascript">/*! axe v4.11.1 * Copyright (c) 2015 - 2026 Deque Systems, Inc. * * Your use of this Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at …

  • Information conveyed by color alone

    Level
    warning · WCAG 2.1 (A) (ace_style_color_misuse)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    Information, an action, or a distinction is conveyed by color alone - e.g. "required fields are red", errors only in red, a link distinguished from text only by hue.
    Why it matters
    People who cannot distinguish colors (color blindness), people with low vision, and those using monochrome screens will not receive information encoded only in color.
    How to fix it
    Add a second, non-color cue: text, an icon, a pattern, an underline, or a border. E.g. mark required fields with an asterisk and text, errors with a message, links with an underline.
    Automated check limitation
    The validator detects common patterns, but it cannot assess every use of color — confirm relevance manually.
    — Rule details: Combine color with a descriptive marker to convey information, WCAG 1.4.1 WCAG: 1.4.1
    Text and context
    Context: Podmiot Leczniczy Zakonu Ojców Kamilianów w Tarnowskich Górach - Podmiot Leczniczy Zakonu OO. Kamilianów if (top!=self) { top.location.href=self.location.href; } // podtrzymanie sesji (co ok. 14 minut) — bez zal…
    Location
    • XPath: 
      /html[1]/head[1]/link[3]
    • Position: x=0, y=0, w=0, h=0 (viewport 1280×720)
    HTML snippet 
    <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/layout/podmiot/css/style.css?v=1.0.6">
    HTML context 
    <head><meta content="pl_PL" property="og:locale"> <meta content="website" property="og:type"> <meta content="Zatrudnimy specjalistę w oddziale internistycznym" property="og:title"> <meta content="Szpital św. Kamilia w Tarnowskich Górach zatrudni specjalistę w oddziale internistycznym, warunki do omówienia. Praca stabilna, szpital przyjazny. Szczegóły pod numerami: 32 384 97 56, kom. 577 131 623, e-mail: centrum@kamilianie.eu" property="og:description"> <meta content="https://podmiot.kamilianie.eu/index.php?id=103&amp;zoom=15" property="og:url"> <meta content="Szpital św. Kamila" property="og:site_name"> <meta content="2026-08-07T12:10:17+00:00" property="article:modified_time"> <meta content="https://podmiot.kamilianie.eu/images/upload/lekarz.jpg" property="og:image"> <meta content="716" property="og:image:width"> <meta content="409" property="og:image:height"> <meta content="image/jpeg" property="og:image:type"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <!-- <meta name="Copyright" content="Zakon OO. Kamilianów w Polsce"> <meta name="Distribution" content="Global"> <meta name="Rating" content="General"> <meta name="Robots" content="All"> --> <meta name="revisit-after" content="2 days"> <meta name="reply-to" content="kamilianie@kamilianie.eu"> <meta http-equiv="X-UA-Compatible" content="IE=8"> <meta name="Author" content="Zakon OO. Kamilianów w Polsce"> <meta name="Classification" content="CMS"> <meta name="Description" content="Podmiotu Leczniczego Zakonu Ojców Kamilianów w Tarnowskich Górach."> <meta name="KeyWords" content="Szpital św. Kamila, Tarnowskie góry, Szpital, kamilianie, oddział wewnętrzny, pracownia holtera, laboratorium analityczne"> <meta name="Generator" content="SmodCMS"> <meta name="Authoring_Tool" content="SmodCMS // www.smod.pl"> <link href="//podmiot.kamilianie.eu/favicon.ico" rel="shortcut icon"> <link href="//podmiot.kamilianie.eu/favicon.ico" rel="bookmark icon"> <meta name="deklaracja-dostepnosci" content="https://podmiot.kamilianie.eu/index.php?id=176"> <title>Podmiot Leczniczy Zakonu Ojców Kamilianów w Tarnowskich Górach - Podmiot Leczniczy Zakonu OO. Kamilianów</title> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/layout/podmiot/css/style.css?v=1.0.6"> <!--[if IE]> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/layout/podmiot/css/stylemsie.css" /> <![endif]--> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/modules/artykuly/style.css"> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/modules/news/style.css"> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/modules/contact/style.css"> <script type="text/javascript" language="JavaScript" src="//podmiot.kamilianie.eu/add/js.js"></script><script type="text/javascript"> if (top!=self) { top.location.href=self.location.href; } </script> <script type="text/javascript"> // podtrzymanie sesji (co ok. 14 minut) — bez zaleznosci od MooTools window.setInterval(function () { fetch('index.php', { credentials: 'same-origin' }).catch(function () {}); }, 840000); </script> <script type="text/javascript">/*! axe v4.11.1 * Copyright (c) 2015 - 2026 Deque Systems, Inc. * * Your use of this Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at …

  • Content does not adapt when zoomed

    Level
    warning · WCAG 2.1 (AA) (ace_style_viewport_resizable)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    When zoomed or in a narrow view, content does not reflow and requires scrolling in two directions.
    Why it matters
    Having to scroll horizontally and vertically significantly hinders reading for people with low vision who use zoom.
    How to fix it
    Provide a responsive layout in which content reflows to a width equivalent to 320 px without horizontal scrolling (avoid fixed widths).
    — Rule details: Text must be able to be enlarged to 200% without loss of content or functionality, WCAG 1.4.4, 1.4.10 WCAG: 1.4.4, 1.4.10
    Text and context
    Context: Podmiot Leczniczy Zakonu Ojców Kamilianów w Tarnowskich Górach - Podmiot Leczniczy Zakonu OO. Kamilianów if (top!=self) { top.location.href=self.location.href; } // podtrzymanie sesji (co ok. 14 minut) — bez zal…
    Location
    • XPath: 
      /html[1]/head[1]/link[3]
    • Position: x=0, y=0, w=0, h=0 (viewport 1280×720)
    HTML snippet 
    <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/layout/podmiot/css/style.css?v=1.0.6">
    HTML context 
    <head><meta content="pl_PL" property="og:locale"> <meta content="website" property="og:type"> <meta content="Zatrudnimy specjalistę w oddziale internistycznym" property="og:title"> <meta content="Szpital św. Kamilia w Tarnowskich Górach zatrudni specjalistę w oddziale internistycznym, warunki do omówienia. Praca stabilna, szpital przyjazny. Szczegóły pod numerami: 32 384 97 56, kom. 577 131 623, e-mail: centrum@kamilianie.eu" property="og:description"> <meta content="https://podmiot.kamilianie.eu/index.php?id=103&amp;zoom=15" property="og:url"> <meta content="Szpital św. Kamila" property="og:site_name"> <meta content="2026-08-07T12:10:17+00:00" property="article:modified_time"> <meta content="https://podmiot.kamilianie.eu/images/upload/lekarz.jpg" property="og:image"> <meta content="716" property="og:image:width"> <meta content="409" property="og:image:height"> <meta content="image/jpeg" property="og:image:type"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <!-- <meta name="Copyright" content="Zakon OO. Kamilianów w Polsce"> <meta name="Distribution" content="Global"> <meta name="Rating" content="General"> <meta name="Robots" content="All"> --> <meta name="revisit-after" content="2 days"> <meta name="reply-to" content="kamilianie@kamilianie.eu"> <meta http-equiv="X-UA-Compatible" content="IE=8"> <meta name="Author" content="Zakon OO. Kamilianów w Polsce"> <meta name="Classification" content="CMS"> <meta name="Description" content="Podmiotu Leczniczego Zakonu Ojców Kamilianów w Tarnowskich Górach."> <meta name="KeyWords" content="Szpital św. Kamila, Tarnowskie góry, Szpital, kamilianie, oddział wewnętrzny, pracownia holtera, laboratorium analityczne"> <meta name="Generator" content="SmodCMS"> <meta name="Authoring_Tool" content="SmodCMS // www.smod.pl"> <link href="//podmiot.kamilianie.eu/favicon.ico" rel="shortcut icon"> <link href="//podmiot.kamilianie.eu/favicon.ico" rel="bookmark icon"> <meta name="deklaracja-dostepnosci" content="https://podmiot.kamilianie.eu/index.php?id=176"> <title>Podmiot Leczniczy Zakonu Ojców Kamilianów w Tarnowskich Górach - Podmiot Leczniczy Zakonu OO. Kamilianów</title> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/layout/podmiot/css/style.css?v=1.0.6"> <!--[if IE]> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/layout/podmiot/css/stylemsie.css" /> <![endif]--> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/modules/artykuly/style.css"> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/modules/news/style.css"> <link rel="stylesheet" type="text/css" href="//podmiot.kamilianie.eu/modules/contact/style.css"> <script type="text/javascript" language="JavaScript" src="//podmiot.kamilianie.eu/add/js.js"></script><script type="text/javascript"> if (top!=self) { top.location.href=self.location.href; } </script> <script type="text/javascript"> // podtrzymanie sesji (co ok. 14 minut) — bez zaleznosci od MooTools window.setInterval(function () { fetch('index.php', { credentials: 'same-origin' }).catch(function () {}); }, 840000); </script> <script type="text/javascript">/*! axe v4.11.1 * Copyright (c) 2015 - 2026 Deque Systems, Inc. * * Your use of this Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at …

  • Download not accessible from the keyboard

    Level
    warning · WCAG 2.1 (A) (ace_download_keyboard_controllable)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    The file download mechanism works only through mouse interaction and cannot be triggered from the keyboard.
    Why it matters
    People who use only the keyboard cannot download the file if the action requires a mouse.
    How to fix it
    Ensure the download can be triggered from the keyboard (a focusable element, Enter/Space). Simplest is to use a link or a button.
    Automated check limitation
    The validator flags suspicious patterns (e.g. onclick without keyboard handling), but full keyboard operation must be checked manually.
    — Rule details: File download mechanisms should be keyboard operable and preserve the focus position on the page, WCAG 2.1.2 WCAG: 2.1.2
    Text and context
    Text: Polityka jakości
    Context: Polityka prywatności | Klauzula Obowiązku Informacyjnego | Deklaracja dostępności Standardy Ochrony Małoletnich | Polityka jakości
    Location
    • Selector: 
      a[href="https://podmiot.kamilianie.eu/pliki/Polityka_jakosci_2026.pdf"]
    • XPath: 
      /html[1]/body[1]/div[3]/div[1]/a[5]
    • Position: x=215.4, y=2354.7, w=90.7, h=17 (viewport 1280×720)
    HTML snippet 
    <a href="https://podmiot.kamilianie.eu/pliki/Polityka_jakosci_2026.pdf">Polityka jakości</a>
    HTML context 
    <div class="fl"> <a href="./index.php?id=166">Polityka prywatności</a> | <a href="./index.php?id=165">Klauzula Obowiązku Informacyjnego</a> | <a href="./index.php?id=176">Deklaracja dostępności</a><br> <a href="./index.php?id=175">Standardy Ochrony Małoletnich</a> | <a href="https://podmiot.kamilianie.eu/pliki/Polityka_jakosci_2026.pdf">Polityka jakości</a> </div>

  • Content outside any landmark region

    Level
    warning · WCAG 2.1 (A) (ace_aria_content_in_landmark)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    Part of the page content is outside any landmark region (main, nav, header/banner, footer/contentinfo, aside/complementary).
    Why it matters
    Landmarks let screen reader users jump quickly between page regions. Content outside landmarks is harder to find and is skipped when navigating by region.
    How to fix it
    Place all meaningful content in the appropriate regions: main content in <main>, navigation in <nav>, the footer in <footer>. Avoid content sitting directly in <body> outside landmarks.
    — Rule details: All content must be inside an element with a landmark role, WCAG 1.3.1 WCAG: 1.3.1
    Text and context
    Text: Przejdź do treści
    Context: Przejdź do treści Rozmiar czcionki: | Wersja strony:
    Location
    • Selector: 
      ul.skip-links.list-unstyled
    • XPath: 
      /html[1]/body[1]/div[1]/ul[1]
    • Position: x=16, y=6, w=1248, h=0 (viewport 1280×720)
    HTML snippet 
    <ul style="/*display:none;*/" class="skip-links list-unstyled"> <li> <a href="#txt"> Przejdź do treści</a> </li> </ul>
    HTML context 
    <div id="change"><ul style="/*display:none;*/" class="skip-links list-unstyled"> <li> <a href="#txt"> Przejdź do treści</a> </li> </ul> <span class="aaa"> <span class="at">Rozmiar czcionki: </span> <a style="CURSOR: pointer" href="change_style.php?styl=0"><img width="16" height="21" src="images/a1.png" alt="Czcionka" title="Czcionka domyślna"></a> <a style="CURSOR: pointer" href="change_style.php?styl=1"><img width="16" height="21" src="images/a2.png" alt="Czcionka +" title="Czcionka średnia"></a> <a style="CURSOR: pointer" href="change_style.php?styl=2"><img width="16" height="21" src="images/a3.png" alt="Czcionka ++" title="Czcionka duża"></a> | Wersja strony: <a style="CURSOR: pointer" href="change_style.php?kontrast=0"><img width="16" height="21" src="images/a4.png" alt="Wersja standard" title="Wersja standardowa"></a> <a style="CURSOR: pointer" href="change_style.php?kontrast=1"><img width="16" height="21" src="images/a5.png" alt="Wersja z kontrastem 1" title="Wersja z dużym kontrastem 1"></a> <a style="CURSOR: pointer" href="change_style.php?kontrast=2"><img width="16" height="21" src="images/a6.png" alt="Wersja z kontrastem 2" title="Wersja z dużym kontrastem 2"></a> </span> </div>

  • Content outside any landmark region

    Level
    warning · WCAG 2.1 (A) (ace_aria_content_in_landmark)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    Part of the page content is outside any landmark region (main, nav, header/banner, footer/contentinfo, aside/complementary).
    Why it matters
    Landmarks let screen reader users jump quickly between page regions. Content outside landmarks is harder to find and is skipped when navigating by region.
    How to fix it
    Place all meaningful content in the appropriate regions: main content in <main>, navigation in <nav>, the footer in <footer>. Avoid content sitting directly in <body> outside landmarks.
    — Rule details: All content must be inside an element with a landmark role, WCAG 1.3.1 WCAG: 1.3.1
    Text and context
    Context: Rozmiar czcionki: | Wersja strony:
    Location
    • Selector: 
      a[href="change_style.php?styl=0"]
    • XPath: 
      /html[1]/body[1]/div[1]/span[1]/a[1]
    • Position: x=1034, y=34.8, w=20, h=39.2 (viewport 1280×720)
    HTML snippet 
    <a style="CURSOR: pointer" href="change_style.php?styl=0"><img width="16" height="21" src="images/a1.png" alt="Czcionka" title="Czcionka domyślna"></a>
    HTML context 
    <span class="aaa"> <span class="at">Rozmiar czcionki: </span> <a style="CURSOR: pointer" href="change_style.php?styl=0"><img width="16" height="21" src="images/a1.png" alt="Czcionka" title="Czcionka domyślna"></a> <a style="CURSOR: pointer" href="change_style.php?styl=1"><img width="16" height="21" src="images/a2.png" alt="Czcionka +" title="Czcionka średnia"></a> <a style="CURSOR: pointer" href="change_style.php?styl=2"><img width="16" height="21" src="images/a3.png" alt="Czcionka ++" title="Czcionka duża"></a> | Wersja strony: <a style="CURSOR: pointer" href="change_style.php?kontrast=0"><img width="16" height="21" src="images/a4.png" alt="Wersja standard" title="Wersja standardowa"></a> <a style="CURSOR: pointer" href="change_style.php?kontrast=1"><img width="16" height="21" src="images/a5.png" alt="Wersja z kontrastem 1" title="Wersja z dużym kontrastem 1"></a> <a style="CURSOR: pointer" href="change_style.php?kontrast=2"><img width="16" height="21" src="images/a6.png" alt="Wersja z kontrastem 2" title="Wersja z dużym kontrastem 2"></a> </span>

  • Focusable element without a visible focus indicator

    Level
    warning · WCAG 2.1 (AA) (ace_element_tabbable_visible)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    A keyboard-reachable element does not show a visible focus indicator (an outline or highlight) when focused - often due to removing the default CSS outline.
    Why it matters
    People navigating by keyboard must see where the focus currently is. Without an indicator they "get lost" on the page - they do not know which element they are activating.
    How to fix it
    Provide a clear, high-contrast focus indicator (e.g. :focus-visible with a visible outline). Do not remove the outline without providing an equivalent replacement.
    Automated check limitation
    The visibility and contrast of the focus indicator are best assessed manually by moving through the page with the Tab key.
    — Rule details: A Tab-reachable element should be visible on screen when it has keyboard focus, WCAG 2.4.7 WCAG: 2.4.7
    Text and context
    Text: Przejdź do treści
    Context: Przejdź do treści
    Location
    • Selector: 
      a[href="#txt"]
    • XPath: 
      /html[1]/body[1]/div[1]/ul[1]/li[1]/a[1]
    • Position: x=-999, y=0, w=90.1, h=23.2 (viewport 1280×720)
    HTML snippet 
    <a href="#txt"> Przejdź do treści</a>
    HTML context 
    <li> <a href="#txt"> Przejdź do treści</a> </li>

  • Style removes keyboard focus visibility

    Level
    warning · WCAG 2.1 (AA) (ace_style_focus_visible)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    CSS rules (e.g. outline:none) remove the default focus indicator without replacing it with another visible marker.
    Why it matters
    A keyboard user without a visible focus has no way to track their position on the page - using it becomes guesswork.
    How to fix it
    Do not remove the focus indicator without a replacement. Define a clear :focus/:focus-visible style with sufficient contrast and size.
    Automated check limitation
    The visibility and contrast of the focus indicator are best assessed manually by moving through the page with the Tab key.
    — Rule details: The keyboard focus indicator should be visible when the default border or outline is modified by CSS, WCAG 2.4.7 WCAG: 2.4.7
    Text and context
    Text: ❮Poprzednie zdjęcie
    Context: ❮Poprzednie zdjęcie ❯Następne zdjęcie
    Location
    • Selector: 
      #heroPrev
    • XPath: 
      /html[1]/body[1]/div[2]/main[1]/section[1]/button[1]
    • Position: x=82, y=460.7, w=44, h=44 (viewport 1280×720)
    HTML snippet 
    <button type="button" class="hero__ctrl hero__ctrl--prev" id="heroPrev" aria-label="Poprzednie zdjęcie">❮<span style="display:none">Poprzednie zdjęcie</span></button>
    HTML context 
    <section class="hero" aria-label="Zdjęcia z placówek Podmiotu"> <div class="hero__viewport" id="heroSlider"> <img class="hero__slide is-active" src="images/new-2A.jpg" alt="Leczenie w najwyższych standardach"> <img class="hero__slide" src="images/new-3.jpg" alt="Nowoczesne pracownie diagnostyczne"> <img class="hero__slide" src="images/new-4.jpg" alt="Indywidualne podejście do Pacjenta"> <img class="hero__slide" src="images/new-5.jpg" alt="Chronimy środowisko naturalne"> </div> <button type="button" class="hero__ctrl hero__ctrl--prev" id="heroPrev" aria-label="Poprzednie zdjęcie">❮<span style="display:none">Poprzednie zdjęcie</span></button> <button type="button" class="hero__ctrl hero__ctrl--next" id="heroNext" aria-label="Następne zdjęcie">❯<span style="display:none">Następne zdjęcie</span></button> </section>

  • Style removes keyboard focus visibility

    Level
    warning · WCAG 2.1 (AA) (ace_style_focus_visible)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    CSS rules (e.g. outline:none) remove the default focus indicator without replacing it with another visible marker.
    Why it matters
    A keyboard user without a visible focus has no way to track their position on the page - using it becomes guesswork.
    How to fix it
    Do not remove the focus indicator without a replacement. Define a clear :focus/:focus-visible style with sufficient contrast and size.
    Automated check limitation
    The visibility and contrast of the focus indicator are best assessed manually by moving through the page with the Tab key.
    — Rule details: The keyboard focus indicator should be visible when the default border or outline is modified by CSS, WCAG 2.4.7 WCAG: 2.4.7
    Text and context
    Text: ❯Następne zdjęcie
    Context: ❮Poprzednie zdjęcie ❯Następne zdjęcie
    Location
    • Selector: 
      #heroNext
    • XPath: 
      /html[1]/body[1]/div[2]/main[1]/section[1]/button[2]
    • Position: x=1154, y=460.7, w=44, h=44 (viewport 1280×720)
    HTML snippet 
    <button type="button" class="hero__ctrl hero__ctrl--next" id="heroNext" aria-label="Następne zdjęcie">❯<span style="display:none">Następne zdjęcie</span></button>
    HTML context 
    <section class="hero" aria-label="Zdjęcia z placówek Podmiotu"> <div class="hero__viewport" id="heroSlider"> <img class="hero__slide is-active" src="images/new-2A.jpg" alt="Leczenie w najwyższych standardach"> <img class="hero__slide" src="images/new-3.jpg" alt="Nowoczesne pracownie diagnostyczne"> <img class="hero__slide" src="images/new-4.jpg" alt="Indywidualne podejście do Pacjenta"> <img class="hero__slide" src="images/new-5.jpg" alt="Chronimy środowisko naturalne"> </div> <button type="button" class="hero__ctrl hero__ctrl--prev" id="heroPrev" aria-label="Poprzednie zdjęcie">❮<span style="display:none">Poprzednie zdjęcie</span></button> <button type="button" class="hero__ctrl hero__ctrl--next" id="heroNext" aria-label="Następne zdjęcie">❯<span style="display:none">Następne zdjęcie</span></button> </section>

  • Link opens a new window without warning

    Level
    warning · WCAG 2.1 (A) (ace_a_target_warning)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    A link opens in a new window or tab (target="_blank") without any notice in its text or accessible name.
    Why it matters
    Suddenly opening a new window is disorienting - especially for screen reader users (they don't hear that the context changed) and people with cognitive disabilities. The Back button stops working as expected.
    How to fix it
    Warn about opening in a new window: in the link text or via screen-reader text (e.g. "(opens in a new window)"). Consider whether a new window is really needed.
    Automated check limitation
    The validator signals risky patterns; confirm the actual effect of the interaction manually.
    — Rule details: The user should be warned in advance if their action will open a new window, WCAG 3.2.2 WCAG: 3.2.2
    Text and context
    Text: Kliknij aby powiększyć
    Context: Kliknij aby powiększyć
    Location
    • Selector: 
      a[href="https://podmiot.kamilianie.eu/images/upload/0f4bb448-72cc-4efd-bc5f-e1e3149c55b1.jpg"]
    • XPath: 
      /html[1]/body[1]/div[2]/main[1]/div[1]/div[1]/p[5]/a[1]
    • Position: x=70, y=1549.8, w=733, h=83.2 (viewport 1280×720)
    HTML snippet 
    <a href="https://podmiot.kamilianie.eu/images/upload/0f4bb448-72cc-4efd-bc5f-e1e3149c55b1.jpg" target="_blank" rel="noopener"><img style="width: 100%; height: auto; margin: 10px;" src="https://podmiot.kamilianie.eu/images/upload/0f4bb448-72cc-4efd-bc5f-e1e3149c55b1.jpg" alt="Ogłoszenie"><br><small>Kliknij aby powiększyć</small></a>
    HTML context 
    <p style="text-align: center;"><a href="https://podmiot.kamilianie.eu/images/upload/0f4bb448-72cc-4efd-bc5f-e1e3149c55b1.jpg" target="_blank" rel="noopener"><img style="width: 100%; height: auto; margin: 10px;" src="https://podmiot.kamilianie.eu/images/upload/0f4bb448-72cc-4efd-bc5f-e1e3149c55b1.jpg" alt="Ogłoszenie"><br><small>Kliknij aby powiększyć</small></a></p>

  • Link opens a new window without warning

    Level
    warning · WCAG 2.1 (A) (ace_a_target_warning)
    Page
    https://podmiot.kamilianie.eu/
    What it means
    A link opens in a new window or tab (target="_blank") without any notice in its text or accessible name.
    Why it matters
    Suddenly opening a new window is disorienting - especially for screen reader users (they don't hear that the context changed) and people with cognitive disabilities. The Back button stops working as expected.
    How to fix it
    Warn about opening in a new window: in the link text or via screen-reader text (e.g. "(opens in a new window)"). Consider whether a new window is really needed.
    Automated check limitation
    The validator signals risky patterns; confirm the actual effect of the interaction manually.
    — Rule details: The user should be warned in advance if their action will open a new window, WCAG 3.2.2 WCAG: 3.2.2
    Text and context
    Text: Install-IT
    Context: Layout (c) 2026 by: Install-IT Copyright © 2013-2026 Podmiot Leczniczy Zakonu OO. Kamilianów
    Location
    • Selector: 
      a[href="https://www.install-it.pl/"]
    • XPath: 
      /html[1]/body[1]/div[3]/div[2]/a[1]
    • Position: x=1209.5, y=2333, w=50.5, h=17 (viewport 1280×720)
    HTML snippet 
    <a href="https://www.install-it.pl/" target="_blank">Install-IT</a>
    HTML context 
    <div class="fr"> Layout (c) 2026 by: <a href="https://www.install-it.pl/" target="_blank">Install-IT</a><br> Copyright © 2013-2026 Podmiot Leczniczy Zakonu OO. Kamilianów </div>