Public accessibility assessment

Accessibility issues detected on keyfunding.com

Evolize inspected 4 publicly accessible pages on keyfunding.com and detected 27 automatically identifiable accessibility findings. 3 findings were classified as critical or high priority. The findings map to 9 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve buttons have no accessible name, elements must only use permitted aria attributes, no skip link to main content.

27findings detected

3critical + high

4pages inspected

26 Aug 2026assessed

Independent public assessment. keyfunding.com is not necessarily affiliated with or a customer of Evolize.

MONITOR THIS WEBSITE RUN A FREE ASSESSMENT

01 · Accessibility summary

02 · Priority findings

Critical Buttons have no accessible nameWCAG 4.1.2 (A) · 2 pages · 4 instances
Critical Buttons have no accessible nameWCAG 4.1.2 (A) · 2 pages · 2 instances
High Elements must only use permitted ARIA attributesWCAG 4.1.2 (A) · 2 pages · 4 instances
Medium No skip link to main contentWCAG 2.4.1 (A) · 4 pages · 8 instances
Medium Hidden elements can still receive keyboard focusWCAG 2.4.3 (A) · 2 pages · 8 instances

03 · WCAG criteria affected

Criterion	Name	Level	Findings	Pages
1.4.3	Contrast (Minimum)	AA	10	4
2.5.8	Target Size (Minimum)	AA	6	4
2.4.3	Focus Order	A	3	2
4.1.2	Name, Role, Value	A	3	4
1.3.1	Info and Relationships	A	2	4
1.2.2	Captions (Prerecorded)	A	1	2
1.4.1	Use of Color	A	1	2
2.4.1	Bypass Blocks	A	1	4
3.3.2	Labels or Instructions	A	1	2

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

04 · All detected findings

Critical

Buttons have no accessible name

WCAG 4.1.2 (A)6 instances2 affected pages

ComponentRef 2XIV3T

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

Affected pagehttps://keyfunding.com/cookie-policy/

Element.crisp-button

Markup

<button class="crisp-button" onclick="$crisp.push(['do', 'chat:toggle'])"></button>

How to fixGive it an accessible name that describes the action it performs: provide visible text when a visible label is appropriate, an aria-label for an icon-only control (for example aria-label="Dismiss notification"), or aria-labelledby when an existing visible label already describes it. Avoid vague names such as "Button", "Action", or the component's internal name.

Affected pages/cookie-policy /ua/cookie-policy

ComponentRef YOS6PA

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

Affected pagehttps://keyfunding.com/cookie-policy/

Element.header__nav-toggle

Markup

<button type="button" class="header__nav-toggle js-nav-button">
        <span></span>
        <span></span>
        <span></span>
      </button>

Affected pages/cookie-policy /ua/cookie-policy

High

Elements must only use permitted ARIA attributes

WCAG 4.1.2 (A)4 instances2 affected pages

ComponentRef T9E0WJ

Elements must only use permitted ARIA attributes

Affected pagehttps://keyfunding.com/

Element.logo

Accessible nameKey Funding

Markup

<div class="logo" aria-label="Key Funding">

How to fixReview the use of ARIA attributes on the logo and navigation elements. Ensure that only permitted ARIA attributes are used. For example, the 'aria-label' attribute is used on the logo element, but it's not clear if this is necessary. Consider removing unnecessary ARIA attributes to prevent confusion for screen readers and other assistive technologies.

Affected pages/ /ua

Medium

No skip link to main content

WCAG 2.4.1 (A)8 instances4 affected pages

ComponentRef VYZBC5

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

Affected pagehttps://keyfunding.com/

Elementhtml > body

Accessible nameEN UA RU We are launching Take on a challenge in a simulated trading environmentand earn payouts based on your results Time left until launch 13Days 04Hours 09Minutes 08Seconds We are live — welcome! Leave your e-mail Be the first to know about the launchand get early-participant terms We're giving away 60 free challenges Among everyone who leaves an e-mail before September 8.Free to enter, no purchase necessary Giveaway rules September 8, 7:00 PM Join the list We do not share your data with third parties About the product. All trading is conducted in a simulated environment. Key Funding is not a broker, does not provide brokerage or investment services, does not accept funds for investment and does not manage client funds. Risk. Trading derivative financial instruments involves a high level of risk. Results achieved in a simulated environment do not guarantee similar results in the future. Nothing on this website constitutes investment advice. About the giveaway. The giveaway is organised by Key Funding. Entry is free and no purchase is necessary. 60 free challenges are being given away. Age and country restrictions apply; the full list is set out in the giveaway rules. Platforms. This promotion is in no way sponsored, endorsed or administered by, or associated with, Meta. Terms and Conditions Privacy Policy Risk Disclaimer Cookie Policy Giveaway rules We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it. Accept Decline Subscribe to Telegram channel (function () { "use strict"; /* ---------- фоновое видео: на мобиле сносим элемент, чтобы 7.4 МБ не качались ---------- Тот же приём, что в mu-plugin keyfunding-mobile-perf для основного сайта. */ if (window.matchMedia && window.matchMedia("(pointer: coarse), (max-width: 900px)").matches) { var bgv = document.getElementById("bg-video"); if (bgv) { try { bgv.pause(); } catch (e) {} bgv.removeAttribute("autoplay"); bgv.removeAttribute("loop"); var srcs = bgv.querySelectorAll("source"); for (var i = 0; i < srcs.length; i++) { srcs[i].removeAttribute("src"); } bgv.removeAttribute("src"); try { bgv.load(); } catch (e) {} if (bgv.parentNode) bgv.parentNode.removeChild(bgv); } } /* ---------- i18n ---------- Один и тот же файл лежит по трём путям: /coming-soon/, /coming-soon/ua/, /coming-soon/ru/. Язык берётся из пути, поэтому файлы байт-в-байт равны — правку текста достаточно внести здесь и разложить один файл по трём путям. */ var I18N = { "en": { "title": "Key Funding — We are launching", "description": "Take on a challenge in a simulated trading environment. Launching September 8, 7:00 PM. 60 free challenges given away.", "h1": "We are launching", "lead": "Take on a challenge in a simulated trading environment and earn payouts based on your results", "countLabel": "Time left until launch", "days": "Days", "hours": "Hours", "minutes": "Minutes", "seconds": "Seconds", "launched": "We are live — welcome!", "emailHead": "Leave your e-mail", "emailText": "Be the first to know about the launch and get early-participant terms", "giveawayHead": "We're giving away 60 free challenges", "giveawayText": "Among everyone who leaves an e-mail before September 8. Free to enter, no purchase necessary", "launchDate": "September 8, 7:00 PM", "placeholder": "Enter your e-mail", "submit": "Join the list", "sending": "Sending…", "privacy": "We do not share your data with third parties", "okTitle": "You're in!", "okText": "We'll keep you updated by email, but for all the latest news, next steps, and announcements, subscribe to our Telegram channel.", "okAction": "Subscribe to Telegram channel", "dupTitle": "Already entered!", "dupText": "This email is already registered for the giveaway. You're already in. Good luck!", "dupAction": "Got it", "errTitle": "Something went wrong", "errText": "We couldn't register your email right now. Please try again.", "errAction": "Try again", "typoText": "Looks like a typo in your e-mail — check it and try again.", "legalTerms": "Terms and Conditions", "legalPrivacy": "Privacy Policy", "legalRisk": "Risk Disclaimer", "legalCookie": "Cookie Policy", "cookieText": "We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.", "cookieAccept": "Accept", "cookieDecline": "Decline", "giveawayRules": "Giveaway rules", "discProduct": "About the product. All trading is conducted in a simulated environment. Key Funding is not a broker, does not provide brokerage or investment services, does not accept funds for investment and does not manage client funds.", "discRisk": "Risk. Trading derivative financial instruments involves a high level of risk. Results achieved in a simulated environment do not guarantee similar results in the future. Nothing on this website constitutes investment advice.", "discGiveaway": "About the giveaway. The giveaway is organised by Key Funding. Entry is free and no purchase is necessary. 60 free challenges are being given away. Age and country restrictions apply; the full list is set out in the giveaway rules.", "discPlatforms": "Platforms. This promotion is in no way sponsored, endorsed or administered by, or associated with, Meta." }, "ua": { "title": "Key Funding — Ми запускаємось", "description": "Челендж у симульованому торговому середовищі. Запуск 8 вересня, 19:00. Розігруємо 60 безкоштовних челенджів.", "h1": "Ми запускаємось", "lead": "Пройдіть челендж у симульованому торговому середовищі та отримуйте виплати за його результатами", "countLabel": "Час до запуску", "days": "Днів", "hours": "Годин", "minutes": "Хвилин", "seconds": "Секунд", "launched": "Ми в ефірі — вітаємо!", "emailHead": "Залиште e-mail", "emailText": "Дізнайтеся про запуск першими та отримайте умови для ранніх учасників", "giveawayHead": "Розігруємо 60 безкоштовних челенджів", "giveawayText": "Серед усіх, хто залишив e-mail до 8 вересня. Участь безкоштовна, купівля не потрібна", "launchDate": "8 вересня, 19:00", "placeholder": "Введіть ваш e-mail", "submit": "Приєднатися", "sending": "Надсилаємо…", "privacy": "Ми не передаємо ваші дані третім …[truncated by Evolize: exceeded D1 value limit]

Markup

<body>
<div class="general-background" aria-hidden="true">
  <video autoplay="" loop="" muted="" playsinline="" preload="metadata" id="bg-video">
    <source src="/wp-content/uploads/2026/05/hf_20260328_105406_16f4600d-7a92-4292-b96e-b19156c7830a.mp4" type="video/mp4">
  </video>
  <div id="video-tint"></div>
  <div class="glow-top"></div>
  <div class="orb orb-1"></div>
  <div class="orb orb-2"></div>
  <div class="orb orb-3"></div>
  <div class="vignette"></div>
</div>

<main class="scene">
  <nav class="lang" id="lang" aria-label="Language">
    <a href="/" data-lang="en" aria-current="true…

How to fixAdd a skip link to the main content. This can be achieved by adding an anchor link with a visible or hidden text that becomes visible when focused, allowing keyboard users to bypass the navigation and directly access the main content.

Affected pages/ /ua /cookie-policy /ua/cookie-policy

Medium

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)24 instances2 affected pages

ComponentRef G3VBZ8

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://keyfunding.com/

Elementbutton#modal-x

Accessible nameClose

Markup

<button class="modal-x" type="button" id="modal-x" aria-label="Close">
      <svg width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"><path d="M6 6l12 12M18 6L6 18"></path></svg>
    </button>

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.

Affected pages/ /ua

ComponentRef R5291A

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://keyfunding.com/

Elementa#modal-tg

Accessible nameSubscribe to Telegram channel

Markup

<a class="modal-act tg" id="modal-tg" href="#" target="_blank" rel="noopener noreferrer">
      <span class="tg-badge">
        <svg width="14" height="14" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M21.9 4.3 18.9 19c-.2 1-.8 1.2-1.6.8l-4.5-3.3-2.2 2.1c-.2.2-.5.5-.9.5l.3-4.6L18.4 7c.4-.3-.1-.5-.6-.2L7.4 13.4l-4.5-1.4c-1-.3-1-1 .2-1.4l17.6-6.8c.8-.3 1.5.2 1.2 1.5z"></path></svg>
      </span>
      <span data-i18n="okAction">Subscribe to Telegram channel</span>
    </a>

How to fixTo fix this issue, ensure that the element is removed from the tab order when it's not visible. You can achieve this by setting the 'tabindex' attribute to '-1' or by using JavaScript to remove the element from the DOM when it's hidden.

Affected pages/ /ua

ComponentRef AYIIV9

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://keyfunding.com/

Elementnav#lang > a:nth-of-type(1)

Accessible nameEN

Markup

<a href="/" data-lang="en" aria-current="true">EN</a>

How to fixTo fix this issue, ensure that the hidden element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using CSS to set 'display: none' or 'visibility: hidden' when it's not visible. For example: '<a href="/" data-lang="en" aria-current="true" style="display: none;">EN</a>' or '<a href="/" data-lang="en" aria-current="true" tabindex="-1">EN</a>'.

Affected pages/ /ua

Medium

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)4 instances2 affected pages

ComponentRef S3IOTW

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

Affected pagehttps://keyfunding.com/

Elementinput#email

Markup

<input type="email" id="email" name="email" placeholder="Enter your e-mail" required="" autocomplete="email" inputmode="email">

How to fixAdd a visible label element to the form field, using the 'label' tag and the 'for' attribute to associate it with the input field. For example: <label for="email">Enter your e-mail</label> <input type="email" id="email" name="email" required="" autocomplete="email" inputmode="email">

Affected pages/ /ua

Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)119 instances4 affected pages

ComponentRef AVNWLY

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/cookie-policy/

Element#menu-item-144 > a[href="/"]

Accessible nameAbout Us

Markup

<a href="/">About Us</a>

How to fixIncrease the contrast between the text color and the background color of the 'Terms and Conditions' link in the footer to meet the minimum contrast ratio thresholds as defined by WCAG 2.1 SC 1.4.3. Consider using a color contrast analyzer tool to determine the optimal colors.

Affected pages/ /ua /cookie-policy /ua/cookie-policy

ComponentRef EVLEAT

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/

Element.lead

Accessible nameTake on a challenge in a simulated trading environmentand earn payouts based on your results

Markup

<p class="lead" data-i18n-html="lead">Take on a challenge in a simulated trading environment<br>and earn payouts based on your results</p>

How to fixTo improve readability, consider adjusting the text color or background color of the affected element to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3. A contrast ratio of at least 4.5:1 for normal text is recommended.

Affected pages/ /ua

ComponentRef NHSZF4

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/

Elementspan[data-i18n="countLabel"]

Accessible nameTime left until launch

Markup

<span data-i18n="countLabel">Time left until launch</span>

How to fixTo improve accessibility, consider increasing the contrast between the text color and the background color of the element with the text 'Time left until launch'. This can be achieved by changing the CSS styles for the element, such as the color property or the background-color property, to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3.

Affected pages/ /ua

ComponentRef 5UUT6W

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/

Elementp[data-i18n-html="discProduct"]

Accessible nameAbout the product. All trading is conducted in a simulated environment. Key Funding is not a broker, does not provide brokerage or investment services, does not accept funds for investment and does not manage client funds.

Markup

<p data-i18n-html="discProduct"><b>About the product.</b> All trading is conducted in a simulated environment. Key Funding is not a broker, does not provide brokerage or investment services, does not accept funds for investment and does not manage client funds.</p>

How to fixTo improve accessibility, consider increasing the contrast between the text and background colors. This can be achieved by using a color with higher contrast, adjusting the opacity or brightness of the background, or adding a background image or texture that provides sufficient contrast. For example, you can use online tools to check the contrast ratio and adjust the colors accordingly.

Affected pages/ /ua

ComponentRef YX6VTC

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/

Element.hl

Accessible namelaunching

Markup

<span class="hl">launching</span>

How to fixTo improve text legibility, consider increasing the contrast between the text color and background color. This can be achieved by adjusting the CSS styles for the .hl class, such as changing the color or background-color properties to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3.

Affected pages/ /ua

ComponentRef 287L92

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/

Elementh1

Accessible nameWe are launching

Markup

<h1 data-i18n-html="h1">We are <span class="hl">launching</span></h1>

How to fixTo improve the accessibility of the website, increase the contrast between the text color and the background color of the element with the text 'We are launching'. This can be achieved by changing the CSS styles to use a color combination that meets the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3.

Affected pages/ /ua

ComponentRef 2HF1ZQ

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/

Elementp[data-i18n-html="discProduct"] > b

Accessible nameAbout the product.

Markup

<b>About the product.</b>

How to fixTo improve accessibility, consider adjusting the text or background color 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 are accessible to users with visual impairments.

Affected pages/ /ua

ComponentRef IJFRJW

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/

Element#t-d

Accessible name13

Markup

<b id="t-d">13</b>

How to fixTo improve readability, consider increasing the contrast between the text color and background color. You can do this by changing the CSS styles for the element with id 't-d' to use a darker or lighter color, depending on the background. For example, you could use a tool to select a color that meets the WCAG 2.1 contrast ratio guidelines.

Affected pages/ /ua

ComponentRef 6I28PH

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/cookie-policy/

Element#cn-notice-text

Accessible nameWe use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Markup

<span id="cn-notice-text" class="cn-text-container">We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.</span>

How to fixTo improve the accessibility of the cookie policy text, consider adjusting the color scheme to meet the minimum contrast ratio thresholds. This can be achieved by changing the background color, text color, or both, to ensure sufficient contrast between the text and its background.

Affected pages/cookie-policy /ua/cookie-policy

ComponentRef TMIHLB

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://keyfunding.com/cookie-policy/

Element.header__button

Accessible nameSign In

Markup

<a href="/" target="_self" class="button header__button _bordered">Sign In</a>

How to fixIncrease the contrast between the text color and background color of the 'Sign In' button to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3.

Affected pages/cookie-policy /ua/cookie-policy

Medium

Links must be distinguishable without relying on color

WCAG 1.4.1 (A)4 instances2 affected pages

ComponentRef F3ZU2P

Links must be distinguishable without relying on color

Affected pagehttps://keyfunding.com/cookie-policy/

Elementa[href$="mailto:[email removed]"]

Accessible name[email removed]

Markup

<a href="mailto:[email removed]"><b>[email removed]</b></a>

How to fixAdd an underline or other visual indicator to the link to make it distinguishable from surrounding text without relying on color. For example, add a CSS style to the link element: style="text-decoration: underline;"

Affected pages/cookie-policy /ua/cookie-policy

Low

Page has no level-one heading

WCAG 1.3.1 (A)4 instances2 affected pages

ComponentRef MLPVOA

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

Affected pagehttps://keyfunding.com/cookie-policy/

Elementhtml > body

Accessible nameAbout Us How it works Challenges Blog FAQ Sign In Cookie Policy Introduction This Cookie Policy (hereinafter – CP) constitutes a policy in regard to the HTTP cookies data (small text files we send to your computer or mobile device), which are unique to your account or your browser. It is an integral part of the Terms and conditions of Key Funding adopted by Cryptology Key OÜ (hereinafter – T&C). All terms used in the T&C have the same meaning in this CP. Generally, there are 2 types of cookies: (a) the session-based cookies (which last only while your browser is opened and running, they are automatically deleted when you close it), and (b) persistent cookies (which last until you, or your browser, delete them, or until they expire). We, or our affiliates/partners, use such files and similar technologies (e.g., like single-pixel gifs and web beacons) in our activities. To be exact, we may use both session-based and persistent cookies to provide you our services, or to make it easier to navigate the website. The applicable law provides you with certain rights, allowing you to opt-out from cookies gathering to some degree, or completely. In order to adhere your rights, you will receive a pop-up notification on such and a questionnaire of the relevant content, so you may choose to exercise those rights or not. We have a person whose role puts him/her in charge of the technical matters – data protection officer (DPO), whom you can reach in order to ask any question in regard to your cookies, or other related matters via this email [email removed] with the appropriate topic. Cookies in details Some cookies are associated with your account and personal information in order to remember that you are logged in and which services you order. Other cookies are not tied to your account, but are unique, and allow us to carry out analytics and customization, among other similar things. Cookies can be used to recognize you when you visit our website or use our services, remember your preferences, and give you a personalized experience that’s consistent with your settings. Cookies also make your interactions faster and more secure. Cookies and other advertisement technologies (such as beacons, pixels, and tags) help us market more effectively to actual (or potential) users that we, and our partners, believe may be interested in our services. They also help provide us with aggregated auditing, research, statistics and reporting, and know when content has been shown to you. You may prefer not to allow cookies, which is why most browsers give you the ability to manage cookies to suit your interest. In some browsers you may also manage cookies preferences for each particular website. Your options in regard to cookies You can find the instructions how to manage your cookies for different browsers below: Google Chrome Internet Explorer Mozilla Firefox Safari Android Browser Opera For any other browsers – please consult the documentation that your browser manufacturer provides. You may opt-out of third-party cookies from Google Analytics on the relevant website. You can opt out of interest-based targeting provided by participating ad servers through the Digital Advertising Alliance (http://youradchoices.com). In addition, you can change your device settings to control whether you see online interest-based ads. Be aware, that if you limit the ability of any websites and applications to set cookies, you may spoil your overall user experience and/or lose the ability to access the services – since it will no longer be personalized to you. It may also stop you from saving customized settings, like login information. Also, please note, that the pop-up window, which may be shown to you upon your entrance on our website, provides you with the option to opt-out in compliance with the provision of the law applicable. Cookies which we may use on our website: Authentication – if you’re signed in to our website, cookies help us show you the right information and personalize your experience; Security – we use cookies to enable and support our security features, and to help us detect malicious activity; Preferences, features and services – cookies can tell us which language you prefer and what your communications preferences are, and they can help you fill out forms on our website more easily. They also provide you with features, insights, and customized content); Marketing – we may use cookies to help us deliver marketing campaigns and track their performance, e.g., a user visited our support page and then made a purchase, and, similarly, our partners may use cookies to provide us with information about your interactions with their services but use of those third-party cookies would be subject to the service provider’s policies; Performance, analytics and research – cookies help us learn how convenient our website is for users, and we also use cookies to understand, improve, and research products, features, and services, including to create logs and record when you access our website from different devices, such as your work computer or your mobile device. The applicable law Depending on the country/territory you are based in (meaning, location from where you enter the website), the rules governing your interaction with us may differ. Thus, if anything contrary regarding your rights or obligations are provided to you due to the operation of law, which we are unaware of, let us know via the contacts below. Please be advised that the regulations of the EU are generally applicable to us, due to the fact that we are an operator of the website and provider of the services. Our contact details You may get in touch with us via several methods send us an email to the following address [email removed] with the subject matter of your concern (any of the aforementioned or else), and we shall return to you promptly. Cryptology Key OÜ Register number: 17062904, VAT number EE102796018, Registered office: Tornimäe tn 7-36, Kesklinna linnaosa, Tallinn, 10145, Estonia As described in the Terms & Conditions of Key Funding (current version), all and any information provided on this website is intended exclusively for educational purpose for training of your skills in the sphere of financial, digital assets and other instruments trading activity, and shall not serve (and is not deem to serve) in any way as a specific investment recommendation, business recommendation, investment opportunity analysis or similar general recommendation regarding the trading of investment instruments. Please, note that if the law, applicable to you, prohibits use/consumption of such types of electronic services, it effectively means that we are not soliciting our service to you. The information on this site is not directed at residents in any country or jurisdiction where such distribution or use would be contrary to local laws or regulation. We do not act as a broker and do not accept any deposits. The offered technical solution for our platform and data feed is powered by the liquidity providers. Terms and Conditions Privacy Policy Risk Disclaimer Cookie Policy window.CRISP_READY_TRIGGER = function() { $crisp.push(["config", "color:theme", ["light_green"]]); }; {"prefetch":[{"source":"…[truncated by Evolize: exceeded D1 value limit]

Markup

<body class="wp-singular page-template-default page page-id-704 wp-theme-key-new theme-key-new woocommerce-js cookies-not-set">
  <header class="header">
    <div class="container">
      <a href="https://keyfunding.com/" class="header__logo" aria-label="logo">
        <img src="https://keyfunding.com/wp-content/uploads/2026/01/logo.svg" class="attachment-full size-full" alt="" loading="lazy" decoding="async">      </a>

      <div class="header__controls js-nav">
        <nav class="header__nav-wrap"><ul id="main_menu_2" class="header__nav"><li id="menu-item-144" class="menu-item menu-item-ty…

How to fixAdd a level-one heading (<h1>) to the page to convey its topic and provide a clear structure for screen readers and other assistive technologies. This heading should be a concise summary of the page's content.

Affected pages/cookie-policy /ua/cookie-policy

Low

Touch targets are too small on mobile

WCAG 2.5.8 (AA)38 instances4 affected pages

ComponentRef 7TTP6N

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://keyfunding.com/

Elementfooter#legal > a:nth-of-type(1)

Accessible nameTerms and Conditions

Markup

<a href="/terms-of-conditions/" data-legal="terms-of-conditions" data-i18n="legalTerms">Terms and Conditions</a>

How to fixIncrease the size of the touch target to at least 24x24px to make it easier for users to activate by touch.

Affected pages/ /ua

ComponentRef VX1Y0F

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://keyfunding.com/

Elementmain > div:nth-of-type(2) > div:nth-of-type(3) > div:nth-of-type(1) > div:nth-of-type(2) > a

Accessible nameGiveaway rules

Markup

<a class="rules-link" href="/giveaway-rules/" data-i18n="giveawayRules">Giveaway rules</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. Consider adding padding or increasing the font size of the 'Giveaway rules' link to achieve this.

Affected pages/ /ua

ComponentRef VXQBDV

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://keyfunding.com/

Elementform#sub-form > input:nth-of-type(1)

Markup

<input class="hp-field" type="text" name="website" tabindex="-1" autocomplete="off" aria-hidden="true">

How to fixIncrease the size of the touch target to at least 24x24px to make it easier to activate by touch. Consider adding padding or increasing the font size of the interactive element to achieve this minimum size.

Affected pages/ /ua

ComponentRef 4QV8QV

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://keyfunding.com/cookie-policy/

Elementbutton#cn-close-notice

Accessible nameDecline

Markup

<button type="button" id="cn-close-notice" data-cookie-set="accept" class="cn-close-icon" aria-label="Decline"></button>

How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch. Consider adding padding or increasing the font size of the button to achieve this.

Affected pages/cookie-policy /ua/cookie-policy

ComponentRef 1XXFTJ

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://keyfunding.com/cookie-policy/

Elementmain#primary > section > div > article > p:nth-of-type(12) > a

Accessible nameGoogle Chrome

Markup

<a href="https://support.google.com/chrome/answer/95647?hl=en-GB"><span style="font-weight: 400;">Google Chrome</span></a>

How to fixIncrease the size of the touch target to at least 24x24px to make it easier for users to activate by touch. Consider adding padding or increasing the font size of the interactive element.

Affected pages/cookie-policy /ua/cookie-policy

ComponentRef 3LAFD7

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://keyfunding.com/cookie-policy/

Elementli#menu-item-414 > a

Accessible nameTerms and Conditions

Markup

<a href="https://keyfunding.com/terms-of-conditions/">Terms and Conditions</a>

How to fixTo fix this issue, increase the size of the touch target to at least 24x24 pixels. This can be achieved by adding padding to the element or increasing the font size of the text within the element.

Affected pages/cookie-policy /ua/cookie-policy

Low

Video may be missing captions

WCAG 1.2.2 (A)2 instances2 affected pages

ComponentRef AV4K3I

A video element has no captions or subtitles track. Whether captions are needed depends on the audio content and requires manual review.

Affected pagehttps://keyfunding.com/

Elementvideo#bg-video

Markup

<video autoplay="" loop="" muted="" playsinline="" preload="metadata" id="bg-video">
    <source src="/wp-content/uploads/2026/05/hf_20260328_105406_16f4600d-7a92-4292-b96e-b19156c7830a.mp4" type="video/mp4">
  </video>

How to fixAdd captions or subtitles to the video, if the audio content is important for understanding. Consider using the track element to provide a captions or subtitles track for the video.

Affected pages/ /ua

05 · Pages inspected

/ua/cookie-policy/11 findings Critical
/cookie-policy/11 findings Critical
/ua/18 findings High
/18 findings High

06 · About this assessment

Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.

Publicly accessible surfaces only — no credentials, private systems, or source-code access.
Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
Results reflect the site at the scan date and may have changed since.

Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment

07 · Continuous monitoring

This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.

MONITOR THIS WEBSITE SEE PRICING

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

Accessibility issues detected on keyfunding.com

01 · Accessibility summary

02 · Priority findings

03 · WCAG criteria affected

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

04 · All detected findings

Buttons have no accessible name

Elements must only use permitted ARIA attributes

No skip link to main content

Hidden elements can still receive keyboard focus

Form fields use placeholder text as the only label

Text has insufficient colour contrast

Links must be distinguishable without relying on color

Page has no level-one heading

Touch targets are too small on mobile

Video may be missing captions

05 · Pages inspected

06 · About this assessment

07 · Continuous monitoring

Other public accessibility assessments