Automated technical assessment of 5 publicly accessible pages · Scanned 6 Sep 2026. Inspected 5 of 5 selected pages.
Findings
Critical
Links lack accessible text
Links expose no accessible name, so screen-reader users cannot determine their destination.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 2.4.4 Link Purpose (In Context) (Level A)
Ref 6H6KAX
Affected pagehttps://marekmalik.cz/en/contact/
Element.vc_col-xs-12 > .vc_column-inner > .wpb_wrapper > .nectar_icon_wrap[data-border-thickness="2px"][data-style="border-animation"] > .nectar_icon > a[target="_blank"]
Markup<a href="https://www.linkedin.com/in/marekmalik/" target="_blank"></a>
How to fixThis link exposes no accessible text. Add visible text that identifies its destination, or remove the link if it serves no purpose. For an icon-only link, provide an aria-label describing where it goes. The link points to https://www.linkedin.com/in/marekmalik/.
Critical
Links lack accessible text
Links expose no accessible name, so screen-reader users cannot determine their destination.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 2.4.4 Link Purpose (In Context) (Level A)
Ref A4Y9CR
Affected pagehttps://marekmalik.cz/en/contact/
Element.top_margin_tablet_70px.top_margin_phone_50px.vc_col-sm-12 > .vc_column-inner > .wpb_wrapper > .nectar_icon_wrap[data-border-thickness="2px"][data-style="border-animation"] > .nectar_icon > a[target="_blank"]
Markup<a href="https://www.linkedin.com/in/marekmalik/" target="_blank"></a>
How to fixThis link exposes no accessible text. Add visible text that identifies its destination, or remove the link if it serves no purpose. For an icon-only link, provide an aria-label describing where it goes. The link points to https://www.linkedin.com/in/marekmalik/.
Critical
Links lack accessible text
Links expose no accessible name, so screen-reader users cannot determine their destination.
Component
1 affected page
52 instances
WCAG WCAG 2.1 SC 2.4.4 Link Purpose (In Context) (Level A)
Ref D5H2II
Affected pagehttps://marekmalik.cz/clanky/
Element.cell[data-lazy="false"]:nth-child(1) > .entire-slide-link[data-fancybox="group_8972"]
Markup<a class="entire-slide-link" href="https://marekmalik.cz/wp-content/uploads/2023/02/product_mgmt_in_practice-min-scaled.jpeg" data-fancybox="group_8972"></a>
How to fixThis link exposes no accessible text. Add visible text that identifies its destination, or remove the link if it serves no purpose. For an icon-only link, provide an aria-label describing where it goes. The link points to https://marekmalik.cz/wp-content/uploads/2023/02/product_mgmt_in_practice-min-s….
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
5 affected pages
5 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref E3I25Z
Affected pagehttps://marekmalik.cz/
Elementli#search-btn > div > a
Accessible namesearch
Markup<a href="#searchbox"><span class="icon-salient-search" aria-hidden="true"></span><span class="screen-reader-text">search</span></a>
How to fixKeep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
5 affected pages
29 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref 17UDS4
Affected pagehttps://marekmalik.cz/
Elementdiv#cmplz-cookiebanner-1-optin > div:nth-of-type(3) > div:nth-of-type(2) > div:nth-of-type(1) > div:nth-of-type(1) > button
Accessible nameNutné soubory cookies
Markup<button class="cmplz-category-toggle" aria-expanded="false" aria-controls="cmplz-desc-functional-1-optin" aria-labelledby="cmplz-title-functional-1-optin"> <span class="cmplz-icon cmplz-open"> <svg aria-hidden="true" focusable="false" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512" height="18"><path d="M224 416c-8.188 0-16.38-3.125-22.62-9.375l-192-192c-12.5-12.5-12.5-32.75 0-45.25s32.75-12.5 45.25 0L224 338.8l169.4-169.4c12.5-12.5 32.75-12.5 45.25 0s12.5 32.75 0 45.25l-192 192C240.4 412.9 232.2 416 224 416z"></path></svg> </span> </button>
How to fixTo fix this issue, ensure that the element is either removed from the tab order or made visible when it receives focus. You can achieve this by adding a 'display: none' or 'visibility: hidden' style when the element is not intended to be visible, or by using JavaScript to dynamically update the element's visibility and focusability based on its state.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
5 affected pages
10 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref VX25GE
Affected pagehttps://marekmalik.cz/en/contact/
Elementdiv#search-box > div > div > form > button
Accessible nameSearch
Markup<button aria-label="Search" class="search-box__button" type="submit">Search</button>
How to fixTo fix this issue, ensure that the element is either visible when it receives focus or is removed from the tab order. This can be achieved by setting the 'display' or 'visibility' CSS property to 'none' when the element is not intended to be visible, or by using the 'tabindex' attribute to remove it from the tab order.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
4 affected pages
14 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref YMHLPO
Affected pagehttps://marekmalik.cz/
Elementli#menu-item-39-en > a
Accessible nameEnglish
Markup<a href="https://marekmalik.cz/en/" lang="en-US" hreflang="en-US"><span class="menu-title-text">English</span></a>
How to fixTo fix this issue, ensure that the element is either visible when focused or removed from the tab order. You can achieve this by adding 'tabindex=-1' to the element or by setting 'display: none' or 'visibility: hidden' when it's not intended to be interacted with.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
3 affected pages
6 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref IM5IQR
Affected pagehttps://marekmalik.cz/
Elementdiv#cmplz-cookiebanner-1-optin > div:nth-of-type(4) > ul > li:nth-of-type(2) > a
Accessible nameSpravovat služby
Markup<a class="cmplz-link cmplz-manage-third-parties cookie-statement" href="https://marekmalik.cz/zasady-cookies-eu/#cmplz-cookies-overview" data-relative_url="#cmplz-cookies-overview">Spravovat služby</a>
How to fixTo fix this issue, ensure that the element is either removed from the tab order or made visible when it receives focus. You can do this by adding a `tabindex=-1` attribute to the element to remove it from the tab order, or by adjusting the CSS to make the element visible when focused.
High
Modal dialog does not trap keyboard focus
An open modal leaves the content behind it keyboard-focusable, so keyboard and screen reader users can tab out of the dialog into hidden page content.
Component
3 affected pages
6 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref VH4Q5W
Affected pagehttps://marekmalik.cz/
Elementdiv#cmplz-cookiebanner-1-optin
Accessible nameInformace o cookies 🍪
Roledialog
Markup<div id="cmplz-cookiebanner-1-optin" class="cmplz-cookiebanner banner-1 bottom-right-minimal optin cmplz-bottom cmplz-categories-type-view-preferences cmplz-show" aria-modal="true" data-nosnippet="true" role="dialog" aria-live="polite" aria-labelledby="cmplz-header-1-optin" aria-describedby="cmplz-message-1-optin"><div class="cmplz-header"><div class="cmplz-logo"></div><div class="cmplz-title" id="cmplz-header-1-optin">Informace o cookies 🍪</div><div class="cmplz-close" tabindex="0" role="button" aria-label="Zavřít dialogové okno"> <svg aria-hidden="true" focusable="false" data-prefix="fas" d…
How to fixTo fix this issue, ensure that the modal dialog traps keyboard focus by setting `tabindex='-1'` on the dialog container and managing focus within the dialog. This can be achieved by listening for the `keydown` event and checking if the focused element is within the dialog. If not, move focus back to the first focusable element within the dialog.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
3 affected pages
12 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref RH4BE1
Affected pagehttps://marekmalik.cz/
Elementinput#cmplz-statistics-optin
Markup<input type="checkbox" id="cmplz-statistics-optin" data-category="cmplz_statistics" class="cmplz-consent-checkbox cmplz-statistics" size="40" value="1">
How to fixKeep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
3 affected pages
3 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref J6P49G
Affected pagehttps://marekmalik.cz/zasady-cookies-eu/
Elementdiv:nth-of-type(2) > nav > ul:nth-of-type(2) > li:nth-of-type(2) > div > a
Accessible nameNavigation Menu
Rolebutton
Markup<a href="#slide-out-widget-area" aria-label="Navigation Menu" aria-expanded="false" role="button" class="closed using-label"> <i class="label">Menu</i><span aria-hidden="true"> <i class="lines-button x2"> <i class="lines"></i> </i> <i class="lines-button x2 hover-effect"> <i class="lines"></i> </i><span class="close-wrap loaded"> <span class="close-line close-line1"></span> <span class="close-line close-line2"></span> </span></span> </a>
How to fixKeep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.
High
Links must be distinguishable without relying on color
Links must be distinguishable without relying on color
Component
3 affected pages
6 instances
WCAG WCAG SC 1.4.1
Ref U8T9TK
Affected pagehttps://marekmalik.cz/
Elementp:nth-child(1) > a[href$="zasady-cookies-eu/"]
Accessible namesoubory cookies
Markup<a class="link-click" href="/zasady-cookies-eu/">soubory cookies</a>
How to fixTo fix this issue, ensure that links have a clear visual distinction from surrounding text, such as an underline or a bold font, in addition to any color differences. Modify the CSS for the 'link-click' class to include a non-color based visual indicator.
High
Links must be distinguishable without relying on color
Links must be distinguishable without relying on color
Component
2 affected pages
4 instances
WCAG WCAG SC 1.4.1
Ref JEQZ7H
Affected pagehttps://marekmalik.cz/zasady-cookies-eu/
Element.link-click
Accessible namesoubory cookies
Markup<a class="link-click" href="/zasady-cookies-eu/">soubory cookies</a>
How to fixTo fix this issue, ensure that links have a clear visual distinction from surrounding text, such as an underline or a bold font, in addition to any color differences. Modify the CSS for the 'link-click' class to include a non-color based visual indicator.
Medium
Navigation regions are not distinguishable
The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.
Component
5 affected pages
20 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A)
Ref K2E7SZ
Affected pagehttps://marekmalik.cz/
Elementdiv#slide-out-widget-area > div > div:nth-of-type(1) > div:nth-of-type(1)
Accessible nameEnglish
Rolenavigation
Markup<div class="off-canvas-menu-container mobile-only" role="navigation"><div class="menu-wrap menuwrapper"><ul class="menu menuopen"><li class="lang-item lang-item-4 lang-item-en lang-item-first menu-item menu-item-type-custom menu-item-object-custom menu-item-39-en"><a href="https://marekmalik.cz/en/" lang="en-US" hreflang="en-US">English</a></li></ul></div><div class="menu-wrap menuwrapper"><ul class="menu secondary-header-items menuopen"></ul></div></div>
How to fixAdd an accessible name to the navigation region, such as an aria-label attribute, to help screen reader users distinguish between multiple navigation landmarks.
Medium
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
5 affected pages
5 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref VO2EZP
Affected pagehttps://marekmalik.cz/en/contact/
Elementhtml > body > nav > a
Accessible nameSkip to main content
Markup<a href="#ajax-content-wrap" class="nectar-skip-to-content">Skip to main content</a>
How to fixIncrease the touch target size of the 'Skip to main content' link to at least 24x24 pixels to make it easier for users to activate by touch on mobile devices.
Medium
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
5 affected pages
5 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref RJ7WUE
Affected pagehttps://marekmalik.cz/en/cookie-policy-eu/
Elementdiv#close > a
Accessible nameClose Search
Rolebutton
Markup<a href="#" role="button"><span class="screen-reader-text">Close Search</span> <span class="close-wrap"> <span class="close-line close-line1" role="presentation"></span> <span class="close-line close-line2" role="presentation"></span> </span> </a>
How to fixIncrease the size of the touch target to at least 24x24px to ensure it can be reliably activated by touch.
Medium
No skip link to main content
The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.
Component
3 affected pages
6 instances
WCAG WCAG 2.1 SC 2.4.1 Bypass Blocks (Level A)
Ref QR5AU9
Affected pagehttps://marekmalik.cz/
Elementhtml > body
Accessible nameInformace o cookies 🍪 Soubory cookie používám ke shromažďování a analýze informací o výkonu a používání webu, zajištění fungování funkcí ze sociálních médií a ke zlepšení a přizpůsobení obsahu a reklam. Nutné soubory cookies Nutné soubory cookies Vždy aktivní Některé soubory cookie jsou vyžadovány, aby byla zajištěna základní funkčnost. Bez těchto cookies nebude web fungovat správně. Ve výchozím nastavení jsou povoleny a nelze je zakázat. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Analytické cookies Analytické cookies The technical storage or access that is used exclusively for statistical purposes. Analytické soubory cookie mi pomáhají vylepšovat webové stránky shromažďováním informací a podáváním zpráv o jejich používání. Marketingové cookies Marketingové cookies Marketingové soubory cookie se používají ke sledování návštěvníků napříč webovými stránkami, které majitelům stránek umožňují zobrazovat relevantní a poutavé reklamy.Spravovat možnostiSpravovat službySpráva {vendor_count} prodejcůPřečtěte si více o těchto účelech Povolit vše Pouze nezbytné Nastavení Uložit nastavení NastaveníZásady cookies {title}{title} (function(window, document) {
document.documentElement.classList.remove("no-js");
if(navigator.userAgent.match(/(Android|iPod|iPhone|iPad|BlackBerry|IEMobile|Opera Mini)/)) {
document.body.className += " using-mobile-browser mobile ";
}
if(navigator.userAgent.match(/Mac/) && navigator.maxTouchPoints && navigator.maxTouchPoints > 2) {
document.body.className += " using-ios-device ";
}
if( !("ontouchstart" in window) ) {
var body = document.querySelector("body");
var winW = window.innerWidth;
var bodyW = body.clientWidth;
if (winW > bodyW + 4) {
body.setAttribute("style", "--scroll-bar-w: " + (winW - bodyW - 4) + "px");
} else {
body.setAttribute("style", "--scroll-bar-w: 0px");
}
}
})(window, document); <iframe src="https://www.googletagmanager.com/ns.html?id=GTM-T9CVKW7" height="0" width="0" style="display:none;visibility:hidden" aria-hidden="true"></iframe>Skip to main content Hit enter to search or ESC to close SearchClose Search Marek Malík search Menu Englishsearch Menu UX Designer & VýzkumníkProduct Designer with 7+ Years of Experience Solving Complex Problems in MarTech & Digital CommerceOzvěte se miDůvěřují mi Navrhuji webové a mobilní aplikace, které lidem usnadňují život.Když technologie naplňují lidské potřeby, dějí se úžasné věci. Proto propojuji design zaměřený na člověka s technologiemi budoucnosti. Výsledkem mé práce jsou digitální produkty a služby, které lidem usnadňují život.Pomáhají mi v tom tyto nástrojeKnow-how Discovery workshop pomůže nastartovat webový projekt, aby přinášel výsledky Byznys 25. července 2021 Discovery workshop pomůže nastartovat webový projekt, aby přinášel výsledkyDiscovery workshop je kreativní týmová aktivita, která umožňuje efektivně získat důležité informace o projektu přímo… Marek Malík Jak díky testování použitelnosti odhalit závažné problémy na webu či e-shopu Testování 24. července 2021 Jak díky testování použitelnosti odhalit závažné problémy na webu či e-shopuJak testování použitelnosti webu či e-shopu s uživateli odhalí závažné problémy a pomůže zvýšit finanční… Marek Malík Designový proces pro řešení složitých problémů při návrhu či redesignu webu Designový proces 23. července 2021 Designový proces pro řešení složitých problémů při návrhu či redesignu webuDesignový proces se používá při hledání řešení složitých problémů, kdy jde primárně o návrh správné… Marek Malík Prozkoumat všechny články Jaký vliv má hodnocení produktů v e-shopu na nákupní chování? K této otázce jsem se měl možnost vyjádřit do prestižního časopisu Forbes, společně se zástupci společností Alza, Dáme jídlo a Wolt. Přečíst celý článek Pokračujte naČlánkyKontaktTento web chroustá soubory cookies.© 2026 Marek Malík. Close Menu EnglishÚvodČlánkyKontakt {"prefetch":[{"source":"document","where":{"and":[{"href_matches":"/*"},{"not":{"href_matches":["/wp-*.php","/wp-admin/*","/wp-content/uploads/*","/wp-content/*","/wp-content/plugins/*","/wp-content/themes/salient-child/*","/wp-content/themes/salient/*","/*\\?(.+)"]}},{"not":{"selector_matches":"a[rel~=\"nofollow\"]"}},{"not":{"selector_matches":".no-prefetch, .no-prefetch a"}}]},"eagerness":"conservative"}]} Spravovat souhlaswindow.wpbCustomElement = 1;<style>.lazyload{display:none;}</style>window.lazySizesConfig=window.lazySizesConfig||{};window.lazySizesConfig.loadMode=1;(function() {
var expirationDate = new Date();
expirationDate.setTime( expirationDate.getTime() + 31536000 * 1000 );
document.cookie = "pll_language=cs; expires=" + expirationDate.toUTCString() + "; path=/; secure; SameSite=Lax";
}());
//# sourceURL=pll_cookie_script-js-after var nectarLove = {"ajaxurl":"https://marekmalik.cz/wp-admin/admin-ajax.php","postID":"12","rooturl":"https://marekmalik.cz","disqusComments":"false","loveNonce":"d492846849","mapApiKey":""};
var nectarOptions = {"delay_js":"false","smooth_scroll":"false","smooth_scroll_strength":"50","quick_search":"false","react_compat":"disabled","header_entrance":"false","body_border_func":"default","disable_box_roll_mobile":"off","body_border_mobile":"0","dropdown_hover_intent":"default","simplify_ocm_mobile":"0","mobile_header_format":"default","ocm_btn_position":"default","left_header_dropdown_func":"default","ajax_add_to_cart":"0","ocm_remove_ext_menu_items":"remove_images","woo_product_filter_toggle":"0","woo_sidebar_toggles":"true","woo_sticky_sidebar":"0","woo_minimal_product_hover":"default","woo_minimal_product_effect":"default","woo_related_upsell_carousel":"false","woo_product_variable_select":"default","woo_using_cart_addons":"false","view_transitions_effect":""};
var nectar_front_i18n = {"menu":"Menu","next":"Next","previous":"Previous","close":"Close"};
//# sourceURL=nectar-frontend-js-extra var complianz = {"prefix":"cmplz_","debug":"","user_banner_id":"1","set_cookies":[],"block_ajax_content":"","banner_version":"155","version":"7.5.3.1","store_consent":"","do_not_track_enabled":"","consenttype":"optin","region":"eu","geoip":"","dismiss_timeout":"","disable_cookiebanner":"","soft_cookiewall":"","dismiss_on_scroll":"","cookie_expiry":"365","url":"https://marekmalik.cz/wp-json/complianz/v1/","locale":"lang=cs&locale=cs_CZ","set_cookies_on_root":"","cookie_domain":"","current_policy_id":"39","cookie_path":"/","categories":{"statistics":"statistika","marketing":"marketing"},"tcf_active":"","placeholdertext":"Klepnut\u00edm p\u0159ijm\u011bte marketingov\u00e9 soubory cookie a povolte tento obsah","css_file":"https://marekmalik.cz/wp-content/uploads/complianz/css/banner-{banner_id}-{type}.css?v=155","page_links":{"eu":{"cookie-statement":{"title":"Z\u00e1sady cookies ","url":"https://marekmalik.cz/zasady-cookies-eu/"}}},"tm_categories":"1","forceEnableStats":"","preview":"","clean_cookies":"","aria_label":"Klepnut\u00edm p\u0159ijm\u011bte marketingov\u00e9 soubory cookie a povolte tento obsah","iapi_nav":"fallback"};
//# sourceURL=cmplz-cookiebanner-js-extra {"baseUrl":"https://s.w.org/images/core/emoji/17.0.2/72x72/","ext":".png","svgUrl":"https://s.w.org/images/core/emoji/17.0.2/svg/","svgExt":".svg","source":{"concatemoji":"https://marekmalik.cz/wp-includes/js/wp-emoji-release.min.js?ver=6.9.7"}} /*! This file is auto-generated */
var e="script#wp-emoji-settings",t=do…[truncated by Evolize: exceeded D1 value limit]
Markup<body data-cmplz="1" class="home wp-singular page-template-default page page-id-12 wp-theme-salient wp-child-theme-salient-child material wpb-js-composer js-comp-ver-8.6.1 vc_responsive cmplz-functional cmplz-eu cmplz-optin" data-footer-reveal="false" data-footer-reveal-shadow="none" data-header-format="default" data-body-border="off" data-boxed-style="" data-header-breakpoint="1000" data-dropdown-style="minimal" data-cae="easeOutCubic" data-cad="750" data-megamenu-width="contained" data-aie="none" data-ls="fancybox" data-apte="standard" data-hhun="1" data-fancy-form-rcs="1" data-form-style="d…
How to fixAdd a "Skip to main content" link as the first focusable element, targeting the id of the <main> region.
Medium
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
2 affected pages
2 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref WCW5DC
Affected pagehttps://marekmalik.cz/
Elementarticle#post-105 > div > div > div:nth-of-type(2) > span > a
Accessible nameMarek Malík
Markup<a href="https://marekmalik.cz/author/xmalik/"> <i class="icon-default-style icon-salient-m-user"></i> Marek Malík</a>
How to fixTo fix this issue, ensure that the hidden element is removed from the tab order by adding 'tabindex=-1' to the element or by making it visible when it receives focus.
Medium
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
3 affected pages
3 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref W0H3EA
Affected pagehttps://marekmalik.cz/
Elementdiv#text-2 > div > p:nth-of-type(1) > a
Accessible namesoubory cookies
Markup<a class="link-click" href="/zasady-cookies-eu/">soubory cookies</a>
How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch.
Medium
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
3 affected pages
3 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref NHZ10G
Affected pagehttps://marekmalik.cz/en/contact/
Elementdiv#cmplz-cookiebanner-1-optin > div:nth-of-type(7) > ul > li:nth-of-type(1) > a
Accessible nameCookie policy
Markup<a class="cmplz-link cookie-statement" href="https://marekmalik.cz/en/cookie-policy-eu/" data-relative_url="">Cookie policy </a>
How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch.
Medium
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
2 affected pages
4 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref TAMK1D
Affected pagehttps://marekmalik.cz/zasady-cookies-eu/
Elementdiv:nth-of-type(1) > div:nth-of-type(1) > div:nth-of-type(1) > ul > li > a
Accessible nameEnglish
Markup<a href="https://marekmalik.cz/en/cookie-policy-eu/" lang="en-US" hreflang="en-US">English</a>
How to fixTo fix this issue, ensure that all focusable elements are visible to keyboard users. You can do this by setting 'display: none;' or 'visibility: hidden;' on the element, or by removing it from the tab order using the 'tabindex' attribute. For example, you can add 'tabindex='-1'' to the element to remove it from the tab order.
Medium
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
2 affected pages
4 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref NRDOO0
Affected pagehttps://marekmalik.cz/zasady-cookies-eu/
Elementdiv#cmplz-manage-consent-container > div > div:nth-of-type(2) > div:nth-of-type(1) > button
Accessible namePreferences
Markup<button class="cmplz-category-toggle" aria-expanded="false" aria-controls="cmplz-desc-preferences-1-optin" aria-labelledby="cmplz-title-preferences-1-optin">
<span class="cmplz-icon cmplz-open">
<svg aria-hidden="true" focusable="false" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512" height="18"><path d="M224 416c-8.188 0-16.38-3.125-22.62-9.375l-192-192c-12.5-12.5-12.5-32.75 0-45.25s32.75-12.5 45.25 0L224 338.8l169.4-169.4c12.5-12.5 32.75-12.5 45.25 0s12.5 32.75 0 45.25l-192 192C240.4 412.9 232.2 416 224 416z"></path></svg>
</span>
</button>
How to fixTo fix this issue, ensure that the element is either visible when it receives focus or is removed from the tab order. One possible solution is to add a 'tabindex=-1' attribute to the element when it is not visible, or to use JavaScript to remove the element from the tab order when it is not visible.
Medium
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref HYFQ4Q
Affected pagehttps://marekmalik.cz/en/contact/
Element.poptavka-kontakt-mail
Accessible name[email removed]
Markup<a class="poptavka-kontakt-mail" href="mailto:[email removed]" target="_blank" rel="noopener">[email removed]</a>
How to fixIncrease the contrast ratio to at least 4.5:1 for normal text and 3:1 for large text.
Medium
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
3 affected pages
4 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 4DGLL2
Affected pagehttps://marekmalik.cz/
Element#cmplz-message-1-optin
Accessible nameSoubory cookie používám ke shromažďování a analýze informací o výkonu a používání webu, zajištění fungování funkcí ze sociálních médií a ke zlepšení a přizpůsobení obsahu a reklam.
Markup<div class="cmplz-message" id="cmplz-message-1-optin">Soubory cookie používám ke shromažďování a analýze informací o výkonu a používání webu, zajištění fungování funkcí ze sociálních médií a ke zlepšení a přizpůsobení obsahu a reklam.</div>
How to fixTo improve accessibility, consider adjusting the color scheme of the text and background to meet the minimum contrast ratio thresholds. You can use online tools to check the contrast ratio and adjust the colors accordingly. Ensure that the text is legible and easy to read, especially for users with visual impairments.
Medium
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref 842BH1
Affected pagehttps://marekmalik.cz/en/contact/
Elementdiv:nth-of-type(1) > div > div > div:nth-of-type(2) > p > a
Accessible namecheck my availability
Markup<a class="dostupnost-link link-click" href="#availability">check my availability</a>
How to fixTo fix this issue, ensure that the element is either removed from the tab order or made visible when it receives focus. This can be achieved by adding a `tabindex='-1'` attribute to the element to remove it from the tab order, or by adjusting the CSS to make the element visible when focused.
Low
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
2 affected pages
22 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref XK8ZWX
Affected pagehttps://marekmalik.cz/en/cookie-policy-eu/
Elementdiv#cmplz-cookies-overview > details:nth-of-type(1) > div:nth-of-type(3) > div:nth-of-type(3) > a
Accessible name_grecaptcha
Markup<a target="_blank" rel="noopener noreferrer nofollow" href="https://cookiedatabase.org/cookie/google-recaptcha/_grecaptcha/">_grecaptcha</a>
How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch.
Low
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
2 affected pages
4 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref W9IYKP
Affected pagehttps://marekmalik.cz/en/cookie-policy-eu/
Elementdiv#cmplz-document > p:nth-of-type(2) > a
Accessible namehttps://marekmalik.cz
Markup<a href="https://marekmalik.cz">https://marekmalik.cz</a>
How to fixTo improve the accessibility of this element, increase the size of the touch target to at least 24x24px. Consider adding padding to the element or increasing the font size to make it easier to tap on mobile devices.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
2 affected pages
3 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref GEP6BX
Affected pagehttps://marekmalik.cz/
Element.byznys
Accessible nameByznys
Markup<a class="byznys" href="https://marekmalik.cz/topic/byznys/">Byznys</a>
How to fixTo improve the accessibility of this element, consider adjusting the text color or background color to meet the minimum contrast ratio thresholds. A contrast ratio of at least 4.5:1 for normal text is recommended.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
2 affected pages
3 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref NUS8GR
Affected pagehttps://marekmalik.cz/
Element.designovy-proces
Accessible nameDesignový proces
Markup<a class="designovy-proces" href="https://marekmalik.cz/topic/designovy-proces/">Designový proces</a>
How to fixIncrease the contrast between the text color and background color of the element with class 'designovy-proces' to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3. Consider using a color contrast analyzer tool to determine the optimal colors.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
2 affected pages
9 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref BOBXR4
Affected pagehttps://marekmalik.cz/
Element#post-105 > .animated.inner-wrap > .post-content > .content-inner > .article-content-wrap > .post-header > h3 > a
Accessible nameDiscovery workshop pomůže nastartovat webový projekt, aby přinášel výsledky
Markup<a href="https://marekmalik.cz/kick-off-workshop/"> Discovery workshop pomůže nastartovat webový projekt, aby přinášel výsledky</a>
How to fixTo improve readability, consider adjusting the text color or background color to meet the minimum contrast ratio of 4.5:1 for normal text. You can use online tools to determine the contrast ratio and select suitable colors.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
2 affected pages
2 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref MZS6LN
Affected pagehttps://marekmalik.cz/
Element.mobile-icon > div > .closed.using-label[href$="#slide-out-widget-area"] > .label
Accessible nameMenu
Markup<i class="label">Menu</i>
How to fixTo improve the accessibility of the 'Menu' text, consider increasing the contrast between the text color and the background color. A minimum contrast ratio of 4.5:1 for normal text is recommended. You can achieve this by adjusting the CSS styles for the element with the class 'label'. For example, you can change the text color or background color to meet the contrast ratio requirements.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
2 affected pages
3 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 6RV6Y3
Affected pagehttps://marekmalik.cz/
Element.testovani
Accessible nameTestování
Markup<a class="testovani" href="https://marekmalik.cz/topic/testovani/">Testování</a>
How to fixIncrease the contrast between the text color and the background color of the element with class 'testovani' to meet the minimum contrast ratio threshold as defined in WCAG 2.1 SC 1.4.3.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
2 affected pages
2 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 5I5DLJ
Affected pagehttps://marekmalik.cz/
Element.buttons > .slide-out-widget-area-toggle[data-icon-animation="simple-transform"][data-custom-color="false"] > div > .closed.using-label[href$="#slide-out-widget-area"] > .label
Accessible nameMenu
Markup<i class="label">Menu</i>
How to fixIncrease the contrast between the text color and background color of the 'Menu' element to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
2 affected pages
4 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref TWZHT1
Affected pagehttps://marekmalik.cz/
Element#logo
Accessible nameMarek Malík
Markup<a id="logo" href="https://marekmalik.cz" data-supplied-ml-starting-dark="false" data-supplied-ml-starting="false" data-supplied-ml="false" class="no-image"> Marek Malík </a>
How to fixTo improve the accessibility of this element, consider adjusting the color of the text or the background to meet the minimum contrast ratio of 4.5:1 for normal text. This can be achieved by using a color contrast analyzer tool to find a suitable color combination that meets the WCAG 2.1 guidelines.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
2 affected pages
4 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref N2O0SH
Affected pagehttps://marekmalik.cz/
Elementstrong:nth-child(1)
Accessible nameprestižního časopisu Forbes
Markup<strong>prestižního časopisu Forbes</strong>
How to fixTo improve the accessibility of this text, consider increasing the contrast between the text color and the background color. This can be achieved by changing the text color or the background color to meet the minimum contrast ratio thresholds as defined by the Web Content Accessibility Guidelines (WCAG 2.1).
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref AIM1LC
Affected pagehttps://marekmalik.cz/
Element.hero
Accessible nameProduct Designer with 7+ Years of Experience Solving Complex Problems in MarTech & Digital Commerce
Markup<h1 style="font-size: 41px;line-height: 1.3;text-align: left;font-family:Roboto;font-weight:700;font-style:normal" class="vc_custom_heading vc_do_custom_heading hero">Product Designer with 7+ Years of Experience Solving Complex Problems in MarTech & Digital Commerce</h1>
How to fixIncrease the contrast between the text color and background color of the h1 element to meet the minimum contrast ratio thresholds as specified in WCAG 2.1 SC 1.4.3. Consider using a color contrast analyzer tool to determine the optimal colors.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 9Q3X0R
Affected pagehttps://marekmalik.cz/
Element.vc_custom_1648574545103 > p
Accessible nameDůvěřují mi
How to fixTo improve the accessibility of this text, increase the contrast between the text color and the background color. You can do this by changing the CSS styles for the text or background elements to use colors with a higher contrast ratio. The WCAG 2.1 guidelines recommend a contrast ratio of at least 4.5:1 for normal text.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref B9VH76
Affected pagehttps://marekmalik.cz/clanky/
Elementh1
Accessible nameČlánky
How to fixTo improve the accessibility of this page, consider adjusting the color scheme to ensure that the text and background colors have a sufficient contrast ratio. A minimum contrast ratio of 4.5:1 for normal text and 7:1 for large text (18pt or larger) is recommended. You can use online tools to check the contrast ratio and select colors that meet the accessibility standards.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
23 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 25HNPU
Affected pagehttps://marekmalik.cz/zasady-cookies-eu/
Elementdetails:nth-child(1) > summary > div > p:nth-child(2)
Accessible nameFunkční, nezbytně nutné, Marketingové
Markup<p>Funkční, nezbytně nutné, Marketingové</p>
How to fixTo improve readability, consider increasing the contrast between the text color and background color. You can achieve this by changing the CSS styles for the paragraph element. For example, you could use a darker text color or a lighter background color. Ensure the contrast ratio meets the minimum threshold of 4.5:1 for normal text.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 26W6CB
Affected pagehttps://marekmalik.cz/
Element.menu-title-text
Accessible nameEnglish
Markup<span class="menu-title-text">English</span>
How to fixTo improve the accessibility of the text, consider adjusting the color scheme to meet the minimum contrast ratio of 4.5:1 for normal text. You can use online tools to check the contrast ratio and select colors that meet the requirements. For example, you can change the background color or the text color to achieve sufficient contrast.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 8KHBTM
Affected pagehttps://marekmalik.cz/en/contact/
Element.poptavka-kontakt-phone
Accessible name+420 733 229 317
Markup<a class="poptavka-kontakt-phone" href="tel:+420733229317">+420 733 229 317</a>
How to fixTo improve the accessibility of this text, consider increasing the contrast between the text color and the background color. You can do this by changing the CSS styles for the .poptavka-kontakt-phone class to use a color combination with a higher contrast ratio.