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

Accessibility issues detected on ender.ing

Evolize inspected 5 publicly accessible pages on ender.ing and detected 7 automatically identifiable accessibility findings. 1 finding was classified as critical or high priority. The findings map to 3 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve links must be distinguishable without relying on color, touch targets are too small on mobile, page has no main landmark.

7findings detected
1critical + high
5pages inspected
24 Aug 2026assessed

Independent public assessment. ender.ing 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 ender.ing and detected 7 automatically identifiable accessibility findings. 1 finding was classified as critical or high priority. The findings map to 3 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve links must be distinguishable without relying on color, touch targets are too small on mobile, page has no main landmark.

02 · Priority findings

03 · WCAG criteria affected

CriterionNameLevelFindingsPages
2.5.8Target Size (Minimum)AA44
1.3.1Info and RelationshipsA22
1.4.1Use of ColorA11

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 ENDER.INGSEE PRICING

04 · All detected findings

High

Links must be distinguishable without relying on color

WCAG 1.4.1 (A)2 instances1 affected page
ComponentRef I7RVCM

Links must be distinguishable without relying on color

Affected pagehttps://ender.ing/blog/
Elementa[href$="ender.ing/"]
Accessible nameEnder.ing
Markup
<a href="https://ender.ing/" target="_blank" rel="noopener noreferrer" class="">Ender.ing</a>
How to fixTo make links distinguishable without relying on color, add an underline or a bold style to the link text, or provide an alternative visual cue. For example, you can add a CSS rule like 'a { text-decoration: underline; }' to underline all links on the page.
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)18 instances4 affected pages
ComponentRef PT0PS1

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

Affected pagehttps://ender.ing/docs/category/statements/
Elementdiv#__docusaurus > nav > div:nth-of-type(3) > div:nth-of-type(1) > button
Accessible nameClose navigation bar
Markup
<button type="button" aria-label="Close navigation bar" class="clean-btn navbar-sidebar__close"><svg viewBox="0 0 15 15" width="21" height="21"><g stroke="var(--ifm-color-emphasis-600)" stroke-width="1.2"><path d="M.75.75l13.5 13.5M14.25.75L.75 14.25"></path></g></svg></button>
How to fixIncrease the size of the touch target to at least 24x24 pixels to ensure it can be easily activated by touch. Consider adding padding or increasing the size of the button element.
Affected pages/blog /internal-error /docs/category/statements /docs/category/style-guides
ComponentRef 5OZIR8

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

Affected pagehttps://ender.ing/blog/
Elementdiv:nth-of-type(2) > div > div > div > div:nth-of-type(1) > a
Accessible name0xENDER
Markup
<a href="/blog/authors/0-x-ender"><span class="authorName_yefp" translate="no">0xENDER</span></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: 91 × 18 CSS pixels; required minimum: 24 × 24 CSS pixels.
ComponentRef QV1RFQ

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

Affected pagehttps://ender.ing/blog/
Elementdiv > main > article:nth-of-type(1) > footer > div:nth-of-type(2) > a
Accessible nameRead more about Dropping Omni and Frankie
Markup
<a aria-label="Read more about Dropping Omni and Frankie" href="/blog/2026/04/28/dropping-projects"><b>Read more</b></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

Page has no main landmark

WCAG 1.3.1 (A)2 instances1 affected page
ComponentRef XZL3EY

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

Affected pagehttps://ender.ing/
Elementhtml > body
Accessible name!function(){var t;document.documentElement.setAttribute("data-theme",t||"dark"),document.documentElement.setAttribute("data-theme-choice",t||"dark")}(),function(){try{for(var[t,e]of new URLSearchParams(window.location.search).entries())if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.setAttribute(a,e)}}catch(t){}}()Welcome toENDER.ING!Temporary navigational linksBlogContribution GuideJuggernyaut(function(){function c(){var b=a.contentDocument||(a.contentWindow&&a.contentWindow.document);if(b){var d=b.createElement('script');d.innerHTML="window.__CF$cv$params={r:'a2ffb8b2784f15b2',t:'MTc4NzU0Njg3Mg=='};var a=document.createElement('script');a.src='/cdn-cgi/challenge-platform/scripts/jsd/main.js';document.getElementsByTagName('head')[0].appendChild(a);";b.getElementsByTagName('head')[0].appendChild(d)}}if(document.body){var a=document.createElement('iframe');a.height=1;a.width=1;a.style.position='absolute';a.style.top=0;a.style.left=0;a.style.border='none';a.style.visibility='hidden';document.body.appendChild(a);if('loading'!==document.readyState)c();else if(window.addEventListener)document.addEventListener('DOMContentLoaded',c);else{var e=document.onreadystatechange||function(){};document.onreadystatechange=function(b){e(b);'loading'!==document.readyState&&(document.onreadystatechange=e,c())}}}})();
Markup
<body><svg style="display: none;"><defs>
<symbol id="theme-svg-external-link" viewBox="0 0 24 24"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></symbol>
</defs></svg>
<script>!function(){var t;document.documentElement.setAttribute("data-theme",t||"dark"),document.documentElement.setAttribute("data-theme-choice",t||"dark")}(),function(){try{for(var[t,e]of new URLSearchParams(window.location.search).entries())if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");docum…
How to fixAdd a main landmark to the page by including a <main> element or an element with role="main" to help screen reader users jump to the primary content.
Low

Page has no level-one heading

WCAG 1.3.1 (A)2 instances1 affected page
ComponentRef JHJQA5

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

Affected pagehttps://ender.ing/blog/
Elementhtml > body
Accessible name!function(){var t;document.documentElement.setAttribute("data-theme",t||"dark"),document.documentElement.setAttribute("data-theme-choice",t||"dark")}(),function(){try{for(var[t,e]of new URLSearchParams(window.location.search).entries())if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.setAttribute(a,e)}}catch(t){}}()Skip to main contentContribution GuideJuggernyautBlogGitHubRecent posts2026Dropping Omni and Frankie2025New web design!2024Omniarium and PolarFrankie!Unstable DevelopmentWelcomeDropping Omni and FrankieApril 28, 2026 · One min read0xENDERCreator @ Ender.ingOmni and Frankie are being droppedTags:EnderingJuggernyautRead moreNew web design!October 22, 2025 · One min read0xENDERCreator @ Ender.ingExplaining the change of the website's design and the reasons behind this change:Tags:EnderingWebRead moreOmniarium and PolarFrankie!November 24, 2024 · One min read0xENDERCreator @ Ender.ingA notice regarding the current development direction for Omniarium:Tags:EnderingCasual(dropped project)Read moreUnstable DevelopmentOctober 20, 2024 · One min read0xENDERCreator @ Ender.ingUnstable development cycle due to lack of commitment!Tags:CasualRead moreWelcomeOctober 20, 2024 · One min read0xENDERCreator @ Ender.ingWelcome to the documentation website of Ender.ing! Here, you'll find user and developer documentation!Tags:CasualEnderingRead moreGeneralContribution GuideProjectsJuggernyautMoreBlogGitHubCopyright © 2026 Ender-ing, 0xENDER. Built with Docusaurus.
Markup
<body style="overflow: visible;"><svg style="display: none;"><defs>
<symbol id="theme-svg-external-link" viewBox="0 0 24 24"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></symbol>
</defs></svg>
<script>!function(){var t;document.documentElement.setAttribute("data-theme",t||"dark"),document.documentElement.setAttribute("data-theme-choice",t||"dark")}(),function(){try{for(var[t,e]of new URLSearchParams(window.location.search).entries())if(t.startsWith("docusaurus-data-")){var a=t.replace("docus…
How to fixAdd a level-one heading (<h1>) to the page to convey its topic and structure the content in a way that is accessible to screen readers and other assistive technologies.
Low

Touch targets are too small

WCAG 2.5.8 (AA)20 instances1 affected page
ComponentRef 30SKI6

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

Affected pagehttps://ender.ing/blog/
Elementarticle:nth-child(1) > header > .margin-top--md.margin-bottom--sm.row > .col--12.authorCol_Hf19.col > .avatar.margin-bottom--sm > .avatar__intro.authorDetails_lV9A > .authorSocials_rSDt > .authorSocialLink_owbf[href$="0xENDER"][title="GitHub"]
Accessible nameGitHub
Markup
<a href="https://github.com/0xENDER" target="_blank" rel="noopener noreferrer" class="authorSocialLink_owbf" title="GitHub">
How to fixIncrease the size of the interactive control to at least 24x24 pixels to ensure it can be easily activated by touch.

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.