EVOLIZEDIGITAL RISK INTELLIGENCE
RUN FREE ASSESSMENT
RUN FREE ASSESSMENT
Public accessibility assessment

Accessibility issues detected on youareanidiot.cc

Evolize inspected 5 publicly accessible pages on youareanidiot.cc and detected 23 automatically identifiable accessibility findings. 2 findings were classified as critical or high priority. The findings map to 6 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve modal dialog does not trap keyboard focus, links must be distinguishable without relying on color, hidden elements can still receive keyboard focus.

23findings detected
2critical + high
5pages inspected
23 Aug 2026assessed

Independent public assessment. youareanidiot.cc is not necessarily affiliated with or a customer of Evolize.

MONITOR THIS WEBSITERUN A FREE ASSESSMENT
https://

01 · Accessibility summary

Evolize inspected 5 publicly accessible pages on youareanidiot.cc and detected 23 automatically identifiable accessibility findings. 2 findings were classified as critical or high priority. The findings map to 6 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve modal dialog does not trap keyboard focus, links must be distinguishable without relying on color, hidden elements can still receive keyboard focus.

02 · Priority findings

03 · WCAG criteria affected

CriterionNameLevelFindingsPages
2.5.8Target Size (Minimum)AA104
1.4.3Contrast (Minimum)AA62
1.3.1Info and RelationshipsA22
1.4.1Use of ColorA21
2.4.3Focus OrderA21
2.4.1Bypass BlocksA12

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

Continuous monitoring

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

Evolize continuously rescans public websites, detects newly introduced or recurring accessibility issues, tracks remediation and verifies fixes.

MONITOR YOUAREANIDIOT.CCSEE PRICING

04 · All detected findings

High

Modal dialog does not trap keyboard focus

WCAG 2.4.3 (A)2 instances1 affected page
ComponentRef 83J2WB

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.

Affected pagehttps://youareanidiot.cc/
Elementdialog#youare-notice
Accessible nameBefore you click… Clicking anywhere on this page after closing this dialog opens a lot of pop-up windows that skitter around your screen. Nothing is installed, downloaded, or collected about you. Want none of that? The safe version has the same song and animation without the payload. Otherwise, allow pop-ups on this website for the full experience. Upon confirmation this dialog will not appear again. I am an idiot Read more…
Markup
<dialog class="notice adaptive" id="youare-notice" open="">
			<h2>Before you click…</h2>
			<p>
				Clicking anywhere on this page after closing this dialog opens <strong>a lot</strong> of pop-up windows
				that skitter around your screen. Nothing is installed, downloaded, or collected about you.
			</p>
			<p>
				Want none of that? The <a class="link" href="/safe/">safe version</a> has the same song
				and animation without the payload. Otherwise, allow pop-ups on this website for <em>the full experience</em>.
			</p>

			<p>
				Upon confirmation this dialog will not appear again.
			</p…
How to fixTo fix this issue, ensure that the modal dialog traps keyboard focus. This can be achieved by setting the 'tabindex' attribute to '-1' on the modal container and programmatically managing focus within the dialog. Additionally, consider using the 'inert' attribute on the content behind the modal to prevent it from receiving keyboard focus while the modal is open.
High

Links must be distinguishable without relying on color

WCAG 1.4.1 (A)4 instances1 affected page
ComponentRef S9F1LI

Links must be distinguishable without relying on color

Affected pagehttps://youareanidiot.cc/cdn-cgi/l/email-protection
Elementp:nth-child(2) > a
Accessible namesign up for Cloudflare
Markup
<a rel="noopener noreferrer" href="https://www.cloudflare.com/sign-up?utm_source=email_protection">sign up for Cloudflare</a>
How to fixEnsure that links have a distinct visual appearance, such as an underline, bolding, or a different font style, in addition to or instead of relying on color. This can be achieved through CSS styling.
ComponentRef QNM6TV

Links must be distinguishable without relying on color

Affected pagehttps://youareanidiot.cc/cdn-cgi/l/email-protection
Element#brand_link
Accessible nameCloudflare
Markup
<a rel="noopener noreferrer" href="https://www.cloudflare.com/5xx-error-landing" id="brand_link" target="_blank">Cloudflare</a>
How to fixAdd an underline or other visual indicator to the link to make it distinguishable from regular text without relying on color alone. For example, add a CSS rule to underline links on hover or focus.
Medium

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)2 instances1 affected page
ComponentRef YG09Q2

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://youareanidiot.cc/
Elementdialog#youare-notice > a
Accessible nameEndermanch
Markup
<a class="link" href="https://enderman.ch">
				<img draggable="false" src="/images/endy.avif" alt="Endermanch">
			</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.
Medium

Page has no main landmark

WCAG 1.3.1 (A)2 instances1 affected page
ComponentRef CTX2D3

No <main> or role=main region is present, so screen reader users cannot jump to primary content.

Affected pagehttps://youareanidiot.cc/cdn-cgi/l/email-protection
Elementhtml > body
Accessible namePlease enable cookies. Email Protection You are unable to access this email address youareanidiot.cc The website from which you got to this page is protected by Cloudflare. Email addresses on that page have been hidden in order to keep them from being accessed by malicious bots. You must enable Javascript in your browser in order to decode the e-mail address. If you have a website and are interested in protecting it in a similar way, you can sign up for Cloudflare. How does Cloudflare protect email addresses on website from spammers? Can I sign up for Cloudflare? Cloudflare Ray ID: a2f9938edf9767f4 • Your IP: Click to reveal 104.28.152.184 • Performance & security by Cloudflare (function(){function d(){var b=a.getElementById("cf-footer-item-ip"),c=a.getElementById("cf-footer-ip-reveal");b&&"classList"in b&&(b.classList.remove("hidden"),c.addEventListener("click",function(){c.classList.add("hidden");a.getElementById("cf-footer-ip").classList.remove("hidden")}))}var a=document;document.addEventListener&&a.addEventListener("DOMContentLoaded",d)})(); window._cf_translation = {};
Markup
<body>
  <div id="cf-wrapper">
    <div class="cf-alert cf-alert-error cf-cookie-error" id="cookie-alert" data-translate="enable_cookies">Please enable cookies.</div>
    <div id="cf-error-details" class="cf-error-details-wrapper">
      <div class="cf-wrapper cf-header cf-error-overview">
        <h1 data-translate="block_headline">Email Protection</h1>
        <h2 class="cf-subheadline"><span data-translate="unable_to_access">You are unable to access this email address</span> youareanidiot.cc</h2>
      </div><!-- /.header -->

      <div class="cf-section cf-wrapper">
        <div class="cf…
How to fixAdd a <main> element or an element with role="main" to define the primary content region of the page, allowing screen reader users to easily navigate to the main content.
Low

Content sits outside any landmark region

WCAG 1.3.1 (A)4 instances2 affected pages
ComponentRef E6LXEF

Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.

Affected pagehttps://youareanidiot.cc/cdn-cgi/l/email-protection
Elementdiv#cf-error-details > div:nth-of-type(1) > h2
Accessible nameYou are unable to access this email address youareanidiot.cc
Markup
<h2 class="cf-subheadline"><span data-translate="unable_to_access">You are unable to access this email address</span> youareanidiot.cc</h2>
How to fixWrap the content in a landmark region such as a 'main' or 'section' element to enable assistive technology users to reach it via landmark navigation.
Affected pages/ /cdn-cgi/l/email-protection
Low

No skip link to main content

WCAG 2.4.1 (A)4 instances2 affected pages
ComponentRef DNW7BJ

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://youareanidiot.cc/safe/
Elementhtml > body
Accessible nameback to the real deal updates You are an Idiot! ☺ ☺ ☺ — Safe Version The safe version of the HTML5 port of the YouAreAnIdiot JavaScript trojan. It plays the same flashing «You are an idiot!» animation and song, but never opens pop-up windows and never moves your browser.
Markup
<body class="adaptive">
		<section class="topbar">
			<nav class="controls adaptive">
				<img class="speaker clicky" id="youare-micon" src="/images/speakerm.avif" width="32" height="32" alt="Mute control">

				<div class="links">
					<a class="link" href="/">back to the real deal</a>
					<a class="link" href="/updates/">updates</a>
				</div>
			</nav>

			<!--
			<aside class="alert">
				<img src="/images/warning.avif" width="32" height="32" alt="Warning!">
				<span>
					<strong>Phishing <span class="text-red">false positive</span> </strong><a class="link" href="/updates">(read more)</…
How to fixAdd a skip link to the main content, allowing keyboard users to bypass the navigation on every page. This can be achieved by adding an anchor element with a link to the main content container, and styling it to be visible only when focused.
Affected pages/ /safe
Low

Touch targets are too small on mobile

WCAG 2.5.8 (AA)29 instances4 affected pages
ComponentRef VU3FXK

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

Affected pagehttps://youareanidiot.cc/updates/
Elementdiv#youare-links > a:nth-of-type(1)
Accessible nameback
Markup
<a class="link" href="/">back</a>
How to fixTo fix this issue, ensure that all interactive elements, such as buttons and links, have a minimum touch target size of 24x24 pixels. You can achieve this by adjusting the padding or width and height of the element. For the given link, consider adding padding to the <a> element to increase its size.
Affected pages/ /updates
ComponentRef LM5E5I

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

Affected pagehttps://youareanidiot.cc/updates/
Elementhtml > body > main > div > p:nth-of-type(9) > a:nth-of-type(1)
Accessible nameyoudontknowwhoiam.org
Markup
<a class="link" target="_blank" href="https://youdontknowwhoiam.org">youdontknowwhoiam.org</a>
How to fixIncrease the size of the touch target to at least 24x24px to make it easier for users to activate by touch.
ComponentRef TTQ74L

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

Affected pagehttps://youareanidiot.cc/
Elementfooter#youare-footer > a
Accessible namev2.0
Markup
<a class="small" href="/updates/">v2.0</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 element with class 'small' to achieve this.
ComponentRef SB6WSJ

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

Affected pagehttps://youareanidiot.cc/safe/
Elementhtml > body > section > nav > div > a:nth-of-type(1)
Accessible nameback to the real deal
Markup
<a class="link" href="/">back to the real deal</a>
How to fixIncrease the size of the touch target to at least 24x24 pixels to ensure reliable activation by touch. Consider adding padding to the element or increasing the font size of the link text.
ComponentRef WBV1JT

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

Affected pagehttps://youareanidiot.cc/
Elementdialog#youare-notice > p:nth-of-type(2) > a
Accessible namesafe version
Markup
<a class="link" href="/safe/">safe version</a>
How to fixTo improve usability, increase the size of the touch target to at least 24x24 pixels for the link with the text 'safe version'. This can be achieved by adjusting the CSS styles for the element, such as increasing the padding or font size of the link.
ComponentRef Q462T3

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

Affected pagehttps://youareanidiot.cc/cdn-cgi/l/email-protection
Elementa#brand_link
Accessible nameCloudflare
Markup
<a rel="noopener noreferrer" href="https://www.cloudflare.com/5xx-error-landing" id="brand_link" target="_blank">Cloudflare</a>
How to fixIncrease the size of the touch target to at least 24x24px to ensure it can be easily activated by touch.
ComponentRef QO48RX

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

Affected pagehttps://youareanidiot.cc/cdn-cgi/l/email-protection
Elementbutton#cf-footer-ip-reveal
Accessible nameClick to reveal
Markup
<button type="button" id="cf-footer-ip-reveal" class="cf-footer-ip-reveal-btn">Click to reveal</button>
How to fixIncrease the size of the touch target to at least 24x24 pixels to ensure users can reliably activate it by touch on mobile devices. Consider adding padding to the button element or increasing its font size to achieve the minimum target size.
ComponentRef 5FP3RS

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

Affected pagehttps://youareanidiot.cc/cdn-cgi/l/email-protection
Elementdiv#cf-error-details > div:nth-of-type(2) > div > div:nth-of-type(1) > p:nth-of-type(2) > a
Accessible namesign up for Cloudflare
Markup
<a rel="noopener noreferrer" href="https://www.cloudflare.com/sign-up?utm_source=email_protection">sign up for Cloudflare</a>
How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to tap on mobile devices. Consider adding padding or increasing the font size of the link to achieve this minimum size.
ComponentRef MZMS64

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

Affected pagehttps://youareanidiot.cc/cdn-cgi/l/email-protection
Elementdiv > div > div > ul > li:nth-of-type(2) > a
Accessible nameCan I sign up for Cloudflare?
Markup
<a rel="noopener noreferrer" class="modal-link-faq" href="https://developers.cloudflare.com/fundamentals/setup/account/create-account/">Can I sign up for Cloudflare?</a>
How to fixIncrease the size of the touch target to at least 24×24px to make it easier for users to activate the link.
ComponentRef DBD1JI

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

Affected pagehttps://youareanidiot.cc/updates/
Elementbody > main > div > p:nth-of-type(2) > em > a
Accessible nameJump to changelog
Markup
<a class="link" href="#changelog">Jump to changelog</a>
How to fixIncrease this <a>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper. Observed size: 122 × 17 CSS pixels; required minimum: 24 × 24 CSS pixels.
Low

Text has insufficient colour contrast

WCAG 1.4.3 (AA)23 instances2 affected pages
ComponentRef REL38D

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

Affected pagehttps://youareanidiot.cc/
Elementa[href$="3Qn9lXg"]
Accessible nameabout
Markup
<a class="link" target="_blank" rel="noopener" href="https://go.enderman.ch/3Qn9lXg">about</a>
How to fixTo improve the accessibility of this link, consider adjusting the color of the text or the background to increase the contrast ratio to at least 4.5:1 for normal text.
Affected pages/ /safe
ComponentRef UYGXBU

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

Affected pagehttps://youareanidiot.cc/
Elementspan
Accessible nameMade with 💖 by Enderman Feedback: [email removed]
Markup
<span>
				Made with 💖 by <a class="link" target="_blank" rel="noopener" href="https://go.enderman.ch/youtube">Enderman</a><br>
				Feedback: <a class="link" href="mailto:[email removed]">[email removed]</a>
			</span>
How to fixTo improve readability, consider increasing the contrast between the text color and the background color. This can be achieved by adjusting the CSS styles for the affected elements, such as the 'span' and 'a' tags within the 'footer' element. A contrast ratio of at least 4.5:1 for normal text is recommended.
ComponentRef JNCJSG

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

Affected pagehttps://youareanidiot.cc/
Element.small
Accessible namev2.0
Markup
<a class="small" href="/updates/">v2.0</a>
How to fixIncrease the contrast between the text color and background color of the affected elements to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3.
ComponentRef OA3HS5

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

Affected pagehttps://youareanidiot.cc/
Element.link[href$="updates/"]
Accessible nameupdates
Markup
<a class="link" href="/updates/">updates</a>
How to fixIncrease the contrast between the text color and background color of the link elements to meet the minimum contrast ratio thresholds as specified in WCAG 2.1 SC 1.4.3
ComponentRef 0S3R1E

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

Affected pagehttps://youareanidiot.cc/
Element#youare-notice > p:nth-child(2)
Accessible nameClicking anywhere on this page after closing this dialog opens a lot of pop-up windows that skitter around your screen. Nothing is installed, downloaded, or collected about you.
Markup
<p>
				Clicking anywhere on this page after closing this dialog opens <strong>a lot</strong> of pop-up windows
				that skitter around your screen. Nothing is installed, downloaded, or collected about you.
			</p>
How to fixTo improve readability, consider increasing the contrast between the text and background colors. This can be achieved by using a darker or lighter background, or by selecting a text color with sufficient contrast. A contrast ratio of at least 4.5:1 for normal text is recommended.
ComponentRef S84EIW

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

Affected pagehttps://youareanidiot.cc/
Elementem
Accessible namethe full experience
Markup
<em>the full experience</em>
How to fixTo improve legibility, consider increasing the contrast between the text color and background color. A minimum contrast ratio of 4.5:1 for normal text is recommended. You can adjust the CSS styles for the element to achieve this.

05 · Pages inspected

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 WEBSITESEE PRICING

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