Skip to content
https://www.nemocnica-bory.sk

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
8
REVIEW
5
PASS
11
INFO
0
Checks
24
11 PASS 5 REVIEW 8 FIX
D
Form Accessibility
Action
4 of 17 controls have issues
FIX
4 of 17 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="gform_submit_button_119">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s" id="s">; <input type="email" name="email">
Info::
13 control(s) properly labeled
17 controls
13 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#ckySwitchfunctionalcheckboxPovoliť Funkčnéaria-label
#ckySwitchanalyticscheckboxPovoliť Analytickéaria-label
#ckySwitchadvertisementcheckboxPovoliť Reklamaaria-label
phrasesearchSearch inputaria-label
phrasesearchSearch inputaria-label
#input_119_21textCompanyfor/id
#input_119_7textMeno*for/id
#input_119_8textPriezviskofor/id
#input_119_3emailE-mail*for/id
#input_119_9telTelefónne číslofor/id
#input_119_20textareaNapíšte námfor/id
#choice_119_6_1checkboxOboznámil/a som sa s Informáciami o spracúvaní osobných údajov.for/id
termscheckboxnone
emailemail(Váš email)placeholder only
#ssearch(Napíšte, čo hľadáte...)placeholder only
#gform_submit_button_119submit(none)none
#g-recaptcha-response-100000textarea(none)none

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

<input type="submit" id="gform_submit_button_119">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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.

<input type="search" name="s" id="s">; <input type="email" name="email">

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
Mobile Keyboard & Autofill
Action
7/7 eligible field(s) missing autocomplete or inputmode
FIX
7/7 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" name="email">
Warning::
6 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email, tel.
Got: <input type="search" name="phrase">, <input type="search" name="phrase">, <input type="search" name="s" id="s">, <input type="email" name="input_3" id="input_119_3">, <input type="tel" name="input_9" id="input_119_9">
D
Tabindex Anti-Patterns
Action
0 positive, 11 -1-on-focusable
FIX
0 positive, 11 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select id="input_119_19">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
16 landmarks
REVIEW
16 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

C
Mobile-Readable Font Sizes
Action
89% of visible text renders at >= 12 CSS px (6 below threshold)
REVIEW
89% of visible text renders at >= 12 CSS px (6 below threshold)
Warning::
6 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <li> 11.0px ("19. 10. 2026"); <a> 11.0px ("Nemocnica"); <li> 11.0px ("19. 10. 2026"); <a> 11.0px ("Gynekológia"); <li> 11.0px ("19. 10. 2026").
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 26 passed
REVIEW
82

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
Všetko div.choices > div.choices__inner > div.choices__list > div.choices__item
Dajte nám spätnú väzbu div.choices > div.choices__inner > div.choices__list > div.choices__item

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Všetko div.hero-banner-content > form.hero-search > span.hero-search-filter > div.choices
Dajte nám spätnú väzbu div#gform_fields_119 > div#field_119_19 > div.ginput_container > div.choices

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Všetko div.hero-banner-content > form.hero-search > span.hero-search-filter > div.choices
Dajte nám spätnú väzbu div#gform_fields_119 > div#field_119_19 > div.ginput_container > div.choices

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SK div.language-bar-element > ul > li.active > a.active
Nemocnica Bory v Bratislave sa od septembra stala univerzitnou nemocnicou. Leká… div.articles-list-item-container > div.right-side > div.content > p.description
19. 10. 2026 div.content > div.meta-element > ul > li
Nemocnica div.meta-element > ul > li > a
Silná menštruačná bolesť, nadmerné krvácanie, únava či problémy s otehotnením. … div.articles-list-item-container > div.right-side > div.content > p.description
19. 10. 2026 div.content > div.meta-element > ul > li
Gynekológia div.meta-element > ul > li > a
Poškodené drobné kĺby prstov môžu výrazne ovplyvniť každodenný život – od boles… div.articles-list-item-container > div.right-side > div.content > p.description
19. 10. 2026 div.content > div.meta-element > ul > li
Ortopédia div.meta-element > ul > li > a
NA PRÍCHOD BÁBÄTKA S NAMI div.container > header.content-section-header > h2.content-section-title > span
Informáciami o spracúvaní osobných údajov. div#input_119_6 > div.gchoice > label#label_119_6_1 > a
div.two-side-wrapper > div.right-side > div.buttons-container > button.button div.two-side-wrapper > div.right-side > div.buttons-container > button.button

These are opportunities to improve the legibility of your content.

Names and labels

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.header-top > div.header-inner > div.left-side > a.left-side-tel div.header-top > div.header-inner > div.left-side > a.left-side-tel
div.header-inner > div.left-side > div#header-compact-nav-button-container > a#header-compact-nav-button div.header-inner > div.left-side > div#header-compact-nav-button-container > a#header-compact-nav-button
div.articles-list-item-container > div.left-side > figure > a div.articles-list-item-container > div.left-side > figure > a
div.articles-list-item-container > div.left-side > figure > a div.articles-list-item-container > div.left-side > figure > a
div.articles-list-item-container > div.left-side > figure > a div.articles-list-item-container > div.left-side > figure > a
div.item > div.video-articles-list-item-container > div.video-container > a.mfp-link div.item > div.video-articles-list-item-container > div.video-container > a.mfp-link
div.item > div.video-articles-list-item-container > div.video-container > a.mfp-link div.item > div.video-articles-list-item-container > div.video-container > a.mfp-link
div.panel-widget-style > div.so-widget-sow-image > div.sow-image-container > a div.panel-widget-style > div.so-widget-sow-image > div.sow-image-container > a
div.social-media-element > ul > li > a div.social-media-element > ul > li > a
div.social-media-element > ul > li > a div.social-media-element > ul > li > a
div.social-media-element > ul > li > a div.social-media-element > ul > li > a
div.social-media-element > ul > li > a div.social-media-element > ul > li > a
div.social-media-element > ul > li > a div.social-media-element > ul > li > a

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.

○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 have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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.
●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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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+
Heading Hierarchy
22 headings
PASS
22 headings
Info::
Single H1 present
  • H1 Nemocnica Bory
  • H2 Ortopédia
  • H2 Neurochirurgia spondylochirurgia
  • H2 Úrazová chirurgia spondylochirurgia
  • H2 Gynekológia
  • H2 Urológia
  • H2 Nateo Rodička budúca mamička
  • H2 Chirurgia
  • H2 Diagneo Laboratórny skríning zdravia
  • H2 Pacient ambulancie hospitalizácie
  • H2 Darcovské centrum
  • H2 Novinky
  • H3 Nemocnica Bory sa stala univerzitnou nemocnicou
  • H3 Endometrióza: Keď bolesť pri menštruácii ovplyvňuje celý život
  • H3 Operácia poškodených drobných kĺbov prstov: Moderné riešenie pre pacientov s artritídou a artrózou
  • H3 V Nemocnici Bory sme ako prví na Slovensku roboticky operovali herniu bez zásahu do brušnej dutiny
  • H2 Pozrite si
  • H3 Poškodené kĺby prstov: Keď pomôže operácia | Nemocnica Bory
  • H3 Moderná rádiofrekvenčná liečba v Nemocnici Bory
  • H2 Pripravte sa na príchod bábätka s nami
  • H2 Napíšte nám
  • H2 Kontakt
A+
Heading Text Quality
All 22 heading(s) have substantive, well-formed text
PASS
All 22 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 28 images OK
PASS
All 28 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
24 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
28 images 3 good alt text 24 decorative
IssueCount
too long1 image(s)
A+
Form Input Types
17 form control(s) checked, no type mismatches
PASS
17 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
17 form control(s) checked, no input-semantic issues
PASS
17 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "sk-SK"
PASS
Lang attribute set to "sk-SK"
Info::
<html lang="sk-SK"> is set and valid
Got: sk-SK
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Nemocnica Bory21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ortopédia21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Neurochirurgia21.00:13.0:1
#000000
#FFFFFF
Pass
h2 spondylochirurgia21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Úrazová chirurgia21.00:13.0:1
#000000
#FFFFFF
Pass
h2 spondylochirurgia21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gynekológia21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Urológia21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nateo21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rodička21.00:13.0:1
#000000
#FFFFFF
Pass
h2 budúca mamička21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Chirurgia21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Diagneo Laboratórny…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Pacient21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ambulancie21.00:13.0:1
#000000
#FFFFFF
Pass
h2 hospitalizácie21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Darcovské centrum21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Novinky21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Pozrite si21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Pripravte sa21.00:13.0:1
#000000
#FFFFFF
Pass

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.

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

Send Feedback