Public accessibility assessment

Accessibility issues detected on eseachellenger.com

Evolize inspected 5 public pages on eseachellenger.com and detected 56 automatically identifiable accessibility findings.

56Findings detected
10WCAG criteria affected
5Pages inspected
23 Aug 2026Assessment date

Highest detected severity: Critical · 30 high-priority findings · 100% inspected-page coverage

Most widespread issueLinks lack accessible textDetected on 5 inspected pages
Most affected page/28 findings detected
Most represented WCAG criterionWCAG 2.4.4 — Link Purpose (In Context)12 detected findings

Is eseachellenger.com your website?

Keep this assessment current and get notified when new accessibility issues are detected.

https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on eseachellenger.com and detected 56 accessibility findings. The most widespread issue was "Links lack accessible text", detected on 5 inspected pages. The most affected inspected page was "/", where 28 findings were detected. The assessment identified findings mapped to 10 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.

02 · Start here

These findings combine the highest severity and broadest reach detected during this assessment.

  1. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 14 instances
    Why this matters

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add text to the link that describes its purpose, or use the aria-label attribute to provide an accessible name for screen reader users. For example: <a href="https://www.facebook.com/NODWINGaming" target="_blank" rel="noopener nofollow" class="cm-link--white centering z--9999" aria-label="Follow us on Facebook">

    View technical evidence →
  2. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 6 instances
    Why this matters

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add text to the link or provide an alternative way to convey its purpose, such as using an aria-label attribute.

    View technical evidence →
  3. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 6 instances
    Why this matters

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add text to the link, such as <a class="cm-link--white centering z--9999" href="/nod">Link Text</a>, so that screen reader users know the link's destination.

    View technical evidence →
  4. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 4 instances
    Why this matters

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add text to the link, such as 'Learn more about Roo' or use an aria-label attribute with a descriptive value, e.g., aria-label='Go to Roo page'

    View technical evidence →
  5. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 4 instances
    Why this matters

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add text to the link, such as 'Learn more about Roo' or use an aria-label attribute with a descriptive value, e.g., aria-label='Go to Roo page'

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
2.4.4Link Purpose (In Context)A1255 / 5
1.4.3Contrast (Minimum)AA955 / 5
2.1.1KeyboardA955 / 5
2.4.3Focus OrderA855 / 5
2.5.8Target Size (Minimum)AA655 / 5
1.1.1Non-text ContentA555 / 5
1.3.1Info and RelationshipsA455 / 5
1.2.2Captions (Prerecorded)A233 / 5
3.3.2Labels or InstructionsA233 / 5
1.4.4Resize TextAA155 / 5

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 reassesses public website pages, detects newly introduced or recurring accessibility findings, and tracks remediation over time.

04 · All detected findings

High

Text has insufficient colour contrast

WCAG 1.4.3 (AA)27 instances5 inspected pages

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

Why it matters

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

Recommended correction

To improve readability, consider increasing the contrast between the text color and background color of the 'Play Now' button. A minimum contrast ratio of 4.5:1 for normal text is recommended.

View 27 affected elements
Component · Ref XL87NR
Affected pagehttps://eseachellenger.com/
Element.btn-medium--tablet > ._1bg6cf1uj._1bg6cf1l7._1bg6cf1kf > ._1bg6cf1wv._1bg6cf1xu
Accessible namePlay Now
Markup
<div class="_1bg6cf1xu _1bg6cf1wv">Play Now</div>
Affected pages/ /dota2 /index
Component · Ref 69I199
Affected pagehttps://eseachellenger.com/
Element._1bg6cf18o._1bg6cf18r > .f--heading3--mobile._1hsdwv4h._1hsdwv3w
Accessible nameCounter-Strike: It's in our DNA Compete for $1,000 on Saturday!
Markup
<h1 class="f--heading2 f--heading3--mobile c--white _1hsdwv4h _1hsdwv3w">Counter-Strike: It's in our DNA Compete for $1,000 on Saturday!</h1>
Affected pages/ /dota2 /index /roo
Component · Ref KHV8A1
Affected pagehttps://eseachellenger.com/roo
Element.btn-base.btn-primary.cm-button--block > ._122jxl6ve._122jxl618q._122jxl6u0 > ._122jxl61c2._122jxl61dg
Accessible nameJoin Space
Markup
<div class="_122jxl61dg _122jxl61c2">Join Space</div>
Component · Ref HPQ2GZ
Affected pagehttps://eseachellenger.com/nod
Element._122jxl61vi._122jxl615y._122jxl61c2 > ._122jxl6ve._122jxl618q._122jxl61dg > .btnauth > ._122jxl61cc._122jxl615y._122jxl6g4 > .dis--blk > .btn-base.btn-primary.cm-button--min-width > ._122jxl6ve._122jxl618q._122jxl6u0 > ._122jxl61c2._122jxl61dg
Accessible nameJoin Space
Markup
<div class="_122jxl61dg _122jxl61c2">Join Space</div>
Component · Ref IFC66H
Affected pagehttps://eseachellenger.com/
Element._1hsdwvs
Accessible nameGet your event pass to play in the Spark special.
Markup
<span as="span" class="c--white _1hsdwv43 _1hsdwvs _1hsdwvp">Get your event pass to play in the Spark special.</span>
Affected pages/ /index
Component · Ref TFZC6W
Affected pagehttps://eseachellenger.com/roo
Element._15uf3s0y
Accessible nameDaily, weekly and monthly СS2 tournaments for all.
Markup
<span class="_15uf3s06o _15uf3s014 _15uf3s0y ojirey3r1">Daily, weekly and monthly СS2 tournaments for all.</span>
Component · Ref QFB09W
Affected pagehttps://eseachellenger.com/nod
Element.ojirey17s._122jxl65k._122jxl67s:nth-child(1) > ._122jxl63c._122jxl614 > div > ._122jxl6ci._122jxl618q._122jxl6u0 > ._122jxl61e0._122jxl61bs > div:nth-child(2) > .ojirey3ra._15uf3s0a._122jxl61e0 > ._15uf3s06o
Accessible name6 months ago
Markup
<span class="_15uf3s06o">6 months ago</span>
Component · Ref D19WD6
Affected pagehttps://eseachellenger.com/nod
Element.f--heading1 > .dis--blk.ellipsis > span
Accessible nameNODWIN Gaming
Markup
<span>NODWIN Gaming</span>
Component · Ref FA5BTG
Affected pagehttps://eseachellenger.com/dota2
Element.f--heading3--full-hd > .cm-marquee.dis--blk.ellipsis > span > .btnauth.cm-link--white
Accessible nameThe Aegis Defensive
Markup
<a class="cm-link--white  btnauth">The Aegis Defensive</a>
High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)76 instances5 inspected pages

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

Why it matters

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

Recommended correction

To fix this issue, ensure that all interactive elements are visible when they receive keyboard focus. You can do this by removing the element from the tab order when it is not visible, or by making the element visible when it receives focus. For example, you can add a CSS rule to display the element when it has focus, such as `:focus { display: block; }`

View 76 affected elements
Component · Ref 9YC6X5
Affected pagehttps://eseachellenger.com/
Elementdiv > div:nth-of-type(1) > div > div:nth-of-type(2) > div > a:nth-of-type(2)
Accessible nameThumbnail
Markup
<a href="/roo"><div>
                                                                                 <img src="https://www.esports.net/wp-content/uploads/2023/10/Roobet-Cup-2023-2.jpg" alt="Thumbnail" class="dis--inl-blk z--0 centering w--100 h--100" style="object-fit: cover;" data-savepage-loading="lazy">
                                                                                 <div class="child bg--shadow _1bg6cf17s _1bg6cf19j _1bg6cf1ba _1bg6cf1d1 _1bg6cf1df _1bg6cf1el _1bg6cf1e7 _1bg6cf1fd _1bg6cf1ez _1bg6cf1yw"></div>
                                                               …
Affected pages/ /dota2 /index /roo
Component · Ref P615N7
Affected pagehttps://eseachellenger.com/
Elementdiv#searererch > form > div > div > input
Markup
<input autocomplete="off" placeholder="Search" type="text" class="ant-input cm-input cm-input--small cm-input--secondary" value="">
Affected pages/ /dota2 /index
Component · Ref PYT871
Affected pagehttps://eseachellenger.com/
Elementdiv:nth-of-type(1) > span > span > span > span > a
Accessible nameNODWIN Gaming
Markup
<a class="cm-link--white" href="https://ggchallengers.uk/s/NODWIN">NODWIN Gaming</a>
Affected pages/ /index
Component · Ref WPM6GT
Affected pagehttps://eseachellenger.com/roo
Elementdiv#cm-spinner > div > div:nth-of-type(2) > a
Accessible nameLet us know!
Markup
<a data-savepage-href="mailto:[email removed]?subject=Connection problems" href="/cdn-cgi/l/email-protection#e2919792928d9096a2818a838e8e878c8587908f8d8687cc818d8fdd91978088878196dfa18d8c8c8781968b8d8cc7d0d292908d808e878f91" style="text-decoration: underline; color: #60759F;" rel="noopener noreferrer">
            Let us know!
        </a>
Affected pages/nod /roo
Component · Ref EGM0VH
Affected pagehttps://eseachellenger.com/roo
Elementbutton#close
Accessible nameClose
Markup
<button class="modal-close-btn" id="close" aria-label="Close">
        <svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor">
          <path d="m13.414 12 5.293-5.293a1 1 0 1 0-1.414-1.414L12 10.586 6.707 5.293a1 1 0 0 0-1.414 1.414L10.586 12l-5.293 5.293a1 1 0 1 0 1.414 1.414L12 13.414l5.293 5.293a1 1 0 0 0 1.414-1.414Z"></path>
        </svg>
      </button>
Affected pages/nod /roo
Component · Ref YU6K04
Affected pagehttps://eseachellenger.com/dota2
Elementinput#state
Rolecombobox
Markup
<input type="search" id="state" autocomplete="no" class="ant-select-selection-search-input" role="combobox" aria-haspopup="listbox" aria-owns="state_list" aria-autocomplete="list" aria-controls="state_list" aria-activedescendant="state_list_0" readonly="" unselectable="on" value="" style="opacity: 0;">
Component · Ref GDAUVS
Affected pagehttps://eseachellenger.com/dota2
Elementdiv > div:nth-of-type(1) > span > div > div > a
Markup
<a class="cm-link--white centering z--9999" href="/dota2#s/SecretShop/tournaments/644b3e2f-099f-45bb-7e9b-08db35e66fd0"></a>
Component · Ref TJ46TL
Affected pagehttps://eseachellenger.com/dota2
Elementform > div > div > div > div:nth-of-type(3) > button
Accessible nameFilters
Markup
<button class="btn btn-base btn-gray cm-button--min-width cm-button--bordered cm-button--input-border-radius btnauth">
                  <div class="_1bg6cf112w _1bg6cf1z4 _1bg6cf1nk _1bg6cf1og">
                    <div class="_1bg6cf112w _1bg6cf111s">Filters</div>
                  </div>
                </button>
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)76 instances5 inspected pages

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Why it matters

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Recommended correction

Add a tabindex attribute or use a focusable HTML element (like a button) to make the control reachable by keyboard. Ensure that the element can receive keyboard focus and that its interactive state is clear when focused.

View 76 affected elements
Component · Ref 4K07Z8
Affected pagehttps://eseachellenger.com/
Elementdiv#react-modal-root > div:nth-of-type(2) > div:nth-of-type(3) > p:nth-of-type(2) > a
Accessible nameCreate an account
Markup
<a class="modal-register-link" onclick="$('.2v244pbf4r7p').click();$('.modalisto').fadeOut()">Create an account</a>
Affected pages/ /dota2 /index /nod /roo
Component · Ref SUEGDZ
Affected pagehttps://eseachellenger.com/
Elementdiv#hideasdasdr > div > div > div > div:nth-of-type(1) > div:nth-of-type(1)
Markup
<div class="_1bg6cf1xu _1bg6cf1d8 _1bg6cf1l7" style="margin-bottom: .8rem;" onclick="document.location.href='/games'">
                                 <div class="_1bg6cf1xu _1bg6cf1wv _1bg6cf1d8">
                                    <div data-state="closed" class="_1bg6cf1ym">
                                       <span class="">
                                          <div class="_1bg6cf1d8 _1bg6cf1fr _1bg6cf11bg">
                                             <div class="cm-avatar-img--input br--app _1bg6cf1d8 _1bg6cf1ow _1bg6cf1fr">
                                                <div c…
Affected pages/ /dota2 /index
Component · Ref N6WA3N
Affected pagehttps://eseachellenger.com/
Elementdiv > div > div:nth-of-type(1) > span:nth-of-type(2) > div > div
Accessible name.st0{fill:#d43b3b}.st1{fill-rule:evenodd;clip-rule:evenodd;fill:#fff}
Markup
<div class="_1bg6cf1xu _1bg6cf1wv _1bg6cf1d8 ogoaoaogogogog" onclick="document.location.href='/dota2'">
                                       <div data-state="closed" class="_1bg6cf1ym">
                                          <span class="">
                                             <div class="_1bg6cf1d8 _1bg6cf1fr _1bg6cf11bg">
                                                <div class="cm-avatar-img--input br--app _1bg6cf1d8 _1bg6cf1ow _1bg6cf1fr" style="margin-top: unset">
                                                   <div class="aspect-ratio--1x1 _1bg6cf1d8" style="margin-top:…
Affected pages/ /dota2 /index
Component · Ref W0CIU0
Affected pagehttps://eseachellenger.com/
Elementdiv#menburerere > div:nth-of-type(1) > a
Accessible nameGames
Markup
<a class="dis--flx flx--0-0-auto ali-ite--center flx-gutter--small pos--rel p--xsmall cm-link--white-dark" onclick="document.location.href='/games'">
                              <div class="_1bg6cf1xu _1bg6cf1wv"><span as="span" class="_1bg6cf1y8 _1hsdwv3w _1hsdwvl _1hsdwv1k">Games</span></div>
                           </a>
Affected pages/ /dota2 /index
Component · Ref JSMD7I
Affected pagehttps://eseachellenger.com/dota2
Elementdiv > div > div:nth-of-type(1) > span:nth-of-type(1) > div > div
Markup
<div class="_1bg6cf1xu _1bg6cf1wv _1bg6cf1d8 darkasodsoadoaosdo" onclick="document.location.href='/cs2'">
                                       <div data-state="closed" class="_1bg6cf1ym">
                                          <span class="">
                                             <div class="_1bg6cf1d8 _1bg6cf1fr _1bg6cf11bg">
                                                <div class="cm-avatar-img--input br--app _1bg6cf1d8 _1bg6cf1ow _1bg6cf1fr" style="margin-top: unset">
                                                   <div class="aspect-ratio--1x1 _1bg6cf1d8" style="margin-to…
Affected pages/ /dota2 /index
Component · Ref GC89NA
Affected pagehttps://eseachellenger.com/roo
Elementdiv#cm-debug-info-button
Accessible name!
Markup
<div id="cm-debug-info-button" style="font-size: 20px; font-weight: 700; padding: 10px; cursor: pointer" onclick="toggleDebugDump()">!</div>
Affected pages/nod /roo
Component · Ref 8EF7IW
Affected pagehttps://eseachellenger.com/roo
Elementdiv:nth-of-type(1) > div:nth-of-type(2) > div:nth-of-type(1) > div:nth-of-type(2) > div:nth-of-type(3) > a
Accessible nameMarketplace
Markup
<a class="dis--flx flx--0-0-auto ali-ite--center flx-gutter--small pos--rel p--xsmall cm-link--white-dark" onclick="document.location.href='/marketplace'" data-savepage-href="/marketplace"><div class="_122jxl61dg _122jxl61c2">
                        <span class="_122jxl61e0 _15uf3s06e _15uf3s0u _15uf3s032">Marketplace</span></div></a>
High

Page has no main landmark

WCAG 1.3.1 (A)10 instances5 inspected pages

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

Why it matters

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

Recommended correction

To fix this issue, add a <main> element or an element with a role of 'main' to the page to define the primary content region. This will allow screen reader users to jump to the main content of the page. For example: <main>...</main> or <div role='main'>...</div>

View 10 affected elements
Component · Ref P0A450
Affected pagehttps://eseachellenger.com/
Elementhtml#html > body
Accessible name___ Games Spaces Marketplace Download Log in .st0{fill:#d43b3b}.st1{fill-rule:evenodd;clip-rule:evenodd;fill:#fff} …[truncated by Evolize: exceeded D1 value limit]
Markup
<body style="margin: 0px; padding: 0px;background: #171C27">
   <a href="index#" tabindex="-1" aria-hidden="true" rel="nofollow" style="opacity: 0.01; position: absolute; z-index: -999; width: 54px; height: 22px;">___</a>
   <div style="opacity: 0.01; position: absolute; z-index: -1000; width: 54px; height: 22px;"></div>
   <div id="react-root">
      <div class="popup-container--arena-layout">
         <div class="_1bg6cf1dm _1bg6cf1k8" style="top: 0px; left: 0px;">
            <div class="bg--green _1bg6cf1qg" style="background: transparent; border: 4px solid transparent; opacity: 0.5;"></di…
Affected pages/ /dota2 /index /nod /roo
High

Zooming and scaling must not be disabled

WCAG 1.4.4 (AA)28 instances5 inspected pages

Zooming and scaling must not be disabled

Why it matters

Zooming and scaling must not be disabled

Recommended correction

To fix this issue, update the meta viewport tag to allow user scaling by removing the 'user-scalable=no' parameter or setting it to 'yes'. For example: <meta name="viewport" content="width=750, user-scalable=yes">

View 28 affected elements
Component · Ref LFTOUC
Affected pagehttps://eseachellenger.com/
Elementmeta[content="width=750, user-scalable=no"][name="viewport"]:nth-child(4)
Markup
<meta name="viewport" content="width=750, user-scalable=no">
Affected pages/ /dota2 /index /nod /roo
High

Images lack text alternatives

WCAG 1.1.1 (A)10 instances4 inspected pages

Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.

Why it matters

Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.

Recommended correction

Add an alt attribute with a descriptive text to the img tag, for example: <img src="assets/img/f.png" alt="Descriptive text">

View 10 affected elements
Component · Ref J676X3
Affected pagehttps://eseachellenger.com/
Elementimg[src="assets/img/f.png"]
Markup
<img src="assets/img/f.png">
Affected pages/ /dota2 /index /roo
Component · Ref E079I9
Affected pagehttps://eseachellenger.com/
Elementdiv[onclick="document.location.href='/nod'"] > ._1bg6cf1ym[data-state="closed"] > span > ._1bg6cf11bg._1bg6cf1fr._1bg6cf1d8 > ._1bg6cf1fr._1bg6cf1ow.cm-avatar-img--input > ._1bg6cf1d8.aspect-ratio--1x1 > div > ._1bg6cf19j._1bg6cf1el._1bg6cf1e7:nth-child(2) > img
Markup
<img src="https://image1.challengermode.com/28bd36fe-3706-4a64-a9a7-08d9bbf43f76_64_64" onerror="this.onerror=null;this.src='assets/img/default-avatar.svg'">
Affected pages/ /dota2 /index
High

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)14 instances3 inspected pages

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.

Why it matters

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.

Recommended correction

Add a persistent <label> associated with each field. Keep the placeholder for example text only, not as the label.

View 14 affected elements
Component · Ref RZLVU2
Affected pagehttps://eseachellenger.com/
Elementdiv#searererch > form > div > div > input
Markup
<input autocomplete="off" placeholder="Search" type="text" class="ant-input cm-input cm-input--small cm-input--secondary" value="">
Affected pages/ /dota2 /index
Component · Ref 85XX2O
Affected pagehttps://eseachellenger.com/
Elementdiv:nth-of-type(2) > div > div:nth-of-type(2) > div > div > input
Markup
<input autocomplete="on" class="ant-input cm-input w--100" placeholder="Try searching for a community, brand or organizer" type="text" value="">
Affected pages/ /index
High

<video> elements must have captions

WCAG 1.2.2 (A)6 instances3 inspected pages

<video> elements must have captions

Why it matters

<video> elements must have captions

Recommended correction

Add captions to the video element, either by including a text track or providing an alternative way for users to access the audio content, such as a transcript.

View 6 affected elements
Component · Ref E42FDT
Affected pagehttps://eseachellenger.com/
Elementvideo[poster="/assets/img/dicki-poster.jpg"]
Markup
<video autoplay="" loop="" playsinline="" muted="" preload="none" data-lazyload="" poster="/assets/img/dicki-poster.jpg" style="object-fit: cover; height: 100%; width: 100%; transition: opacity 500ms ease-in-out 0s; opacity: 0.4;" data-loaded="1">
Affected pages/ /index /roo
High

Scrollable region must have keyboard access

WCAG 2.1.1 (A)2 instances2 inspected pages

Scrollable region must have keyboard access

Why it matters

Scrollable region must have keyboard access

Recommended correction

Review the affected element and correct the reported accessibility issue.

View 2 affected elements
Component · Ref VYZXAW
Affected pagehttps://eseachellenger.com/nod
Element._122jxl612c
Accessible nameHome Feed Tournaments Ladders About
Markup
<div class="_122jxl61dg _122jxl61bs _122jxl6iw _122jxl612c _122jxl6n2 _122jxl6208">
Component · Ref HK1TS
Affected pagehttps://eseachellenger.com/dota2
Element._1bg6cf1ts
Accessible nameOverview Tournaments Ladders Ranking
Markup
<div class="_1bg6cf112o _1bg6cf111c _1bg6cf1f4 _1bg6cf1ts _1bg6cf1ig _1bg6cf11i8 selector">
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)25 instances5 inspected pages

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

Why it matters

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

Recommended correction

Increase the size of the interactive element to at least 24x24 pixels to ensure it can be easily activated by touch.

View 25 affected elements
Component · Ref NBCGGK
Affected pagehttps://eseachellenger.com/
Elementdiv > div > span > span > span > a
Accessible nameRoobet Arena Daily 1v1 EU
Markup
<a class="cm-link--white btnauth" href="/roo">Roobet Arena Daily 1v1 EU</a>
Affected pages/ /index /nod
Component · Ref G6P6Y8
Affected pagehttps://eseachellenger.com/dota2
Elementhtml#html > body > a
Accessible name___
Markup
<a href="/dota2#" tabindex="-1" aria-hidden="true" rel="nofollow" style="opacity: 0.01; position: absolute; z-index: -999; width: 54px; height: 22px;">___</a>
Affected pages/ /dota2 /index
Component · Ref K8NSMM
Affected pagehttps://eseachellenger.com/
Elementdiv#raodsodaosd > div:nth-of-type(1) > div > div > a
Markup
<a class="cm-link--white" href="/">
						   
						   <svg class="dis--inl-blk z--0" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1000 650"><path d="M780.775 73.78q-29.555-59.11-88.666-59.11t-88.666 59.11l-251.22 472.885h133c73.888 0 88.665-29.556 118.22-88.666l88.666-177.332 44.333 88.666C780.775 458 810.33 458 854.662 458h133Z" style="fill:#f36f21"></path><path d="M396.557 251.112q-29.555-59.11-88.665-59.11-59.112 0-88.667 59.11L12.34 635.33h132.998c73.888 0 88.665-29.555 118.221-88.666L307.892 458l44.332 88.665 101.219-190.531Z" style="fill:#f15a29"></path><style xml…
Affected pages/ /dota2 /index
Component · Ref 5X20LM
Affected pagehttps://eseachellenger.com/roo
Elementdiv:nth-of-type(2) > div:nth-of-type(1) > div:nth-of-type(1) > div > div > a
Accessible nameChallengermode
Markup
<a class="cm-link--white" data-savepage-href="/" href="/">
                      <img src="data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGRhdGEtbmFtZT0iTGF5ZXIgMSIgdmlld0JveD0iMCAwIDEwMDAgNjUwIj48cGF0aCBkPSJNNzgwLjc3NSA3My43OHEtMjkuNTU1LTU5LjExLTg4LjY2Ni01OS4xMXQtODguNjY2IDU5LjExbC0yNTEuMjIgNDcyLjg4NWgxMzNjNzMuODg4IDAgODguNjY1LTI5LjU1NiAxMTguMjItODguNjY2bDg4LjY2Ni0xNzcuMzMyIDQ0LjMzMyA4OC42NjZDNzgwLjc3NSA0NTggODEwLjMzIDQ1OCA4NTQuNjYyIDQ1OGgxMzNaIiBzdHlsZT0iZmlsbDojZjM2ZjIxIi8+PHBhdGggZD0iTTM5Ni41NTcgMjUxLjExMnEtMjkuNTU1LTU5LjExLTg4LjY2NS01OS4xMS01OS4xMTIgMC04OC4…
Affected pages/nod /roo
Component · Ref LS0GSE
Affected pagehttps://eseachellenger.com/nod
Elementdiv:nth-of-type(1) > span > span > span > span > a
Accessible nameWeb_BoLT
Markup
<a class="cm-link--white" href="#">Web_BoLT</a>
Component · Ref 194N8U
Affected pagehttps://eseachellenger.com/roo
Elementbutton#radix-\:rj\:
Accessible nameMore items
Markup
<button aria-label="More items" type="button" id="radix-:rj:" aria-haspopup="menu" aria-expanded="false" data-state="closed" class="_1ow1wbqc _1ow1wbqm _1ow1wbqf _1ow1wbqe _122jxl628 _122jxl60 _122jxl612w _122jxl6iw _122jxl618g _15uf3s05u ojirey2ik ojirey2xi ojirey2wu">
                              <span class="_122jxl62b2"><span class="lh--0 dis--inl-flx">
                                <span class="_122jxl61ea _15uf3s05u" style="vertical-align: middle;"></span></span></span></button>
Medium

Content sits outside any landmark region

WCAG 1.3.1 (A)8 instances4 inspected pages

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

Why it matters

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

Recommended correction

Wrap the content in a landmark region such as a header, nav, main, footer, or aside to enable landmark navigation for assistive technology users.

View 8 affected elements
Component · Ref RJR8IC
Affected pagehttps://eseachellenger.com/roo
Elementdiv:nth-of-type(3) > div > div > div > div:nth-of-type(2) > h1
Accessible nameDo you have what it takes?
Markup
<h1 class="f--heading2 f--heading3--mobile c--white _15uf3s078 _15uf3s06e">Do you have what it takes?</h1>
Affected pages/ /index /nod /roo
Medium

Video may be missing captions

WCAG 1.2.2 (A)10 instances3 inspected pages

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

Why it matters

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

Recommended correction

Add captions or subtitles to the video, or provide an alternative way for users to access the audio content, such as a transcript.

View 10 affected elements
Component · Ref 25LZWS
Affected pagehttps://eseachellenger.com/
Elementdiv > div > div > div:nth-of-type(1) > div > video
Markup
<video autoplay="" loop="" playsinline="" muted="" preload="none" data-lazyload="" poster="/assets/img/dicki-poster.jpg" style="object-fit: cover; height: 100%; width: 100%; transition: opacity 500ms ease-in-out 0s; opacity: 0.4;" data-loaded="1">
                                                                     <source data-src="/assets/img/dicki.mp4" type="video/mp4" src="/assets/img/dicki.mp4">
                                                                  </video>
Affected pages/ /index /roo
Low

Low-quality alternative text

WCAG 1.1.1 (A)1182 instances5 inspected pages

Alt text looks like a filename, a generic word ("image", "photo"), or is duplicated across unrelated images — it likely does not describe the content.

Why it matters

Alt text looks like a filename, a generic word ("image", "photo"), or is duplicated across unrelated images — it likely does not describe the content.

Recommended correction

Provide a descriptive alt text for each image, avoiding generic words and filenames. Ensure alt text is unique and describes the content of the image.

View 1182 affected elements
Component · Ref GZ1CDF
Affected pagehttps://eseachellenger.com/
Elementdiv > a > div > div > div > img
Markup
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAoAAAAFoCAYAAADHMkpRAACAAElEQVR42uz9d5xkV3nvC3/XjpU793SYnEcTNMooCyUkJBBGgDHYBHFwxJb9se/1+773vcfHPsY2DsjYx+bYGPtyECBhjklGGEkgCQQKKM2MJufu6Z7p3JWrdljr/rH2rq7u6ZEBaRTrN5+a3bVrV9WuvVd41u95nt8jlFKKFlpooYUWWmihhRbeMDBal6CFFlpooYUWWmjhjYWWAdhCCy200EILLbTwBkPLAGyhhRZaaKGFFlp4g6FlALbQQgsttNBCCy28wdAyAFtooYUWWmihhRbeYGgZgC200EILLbTQQgtvMLQMwBZaaKGFFlpooYU3GFoGYAsttNBCCy200MIbDC0DsIUWWmihhRZaaOENhpYB2EILLbTQQgsttPAGQ8sAbKGFFlpooYUWWniDoWUAttBCCy200EILLbzB0DIAW2ihhRZaaKGFFt5gaBmALbTQQgsLIMMQVOs6tNBCC69fWK1L0EILLbzhoECqkCAIqAd1qsqnHtapeTWGZ07y9NFnWO72…
Affected pages/ /dota2 /index /nod /roo
Component · Ref LH746Z
Affected pagehttps://eseachellenger.com/roo
Elementdiv > div > div > div > div:nth-of-type(2) > img
Markup
<img src="data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAUDBAQEAwUEBAQFBQUGBwwIBwcHBw8LCwkMEQ8SEhEPERETFhwXExQaFRERGCEYGh0dHx8fExciJCIeJBweHx7/2wBDAQUFBQcGBw4ICA4eFBEUHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh7/wAARCABAAEADASIAAhEBAxEB/8QAGwAAAgIDAQAAAAAAAAAAAAAAAAcCBgQFCAP/xAAwEAABAwMCBAUDBAMBAAAAAAABAgMEBQYRACEHEjFBEyJRYYEUQpEWMnHBQ3LRsf/EABoBAAIDAQEAAAAAAAAAAAAAAAQFAQIDBgf/xAAvEQACAQIEBQMDAwUAAAAAAAABAhEAAwQFEiETMUFRYVJxkRQigSMyQqGxweHw/9oADAMBAAIRAxEAPwBC6NGsinw5VQmswoMdyRJeUENtIGVKOn7MFBJOwrMCdhWPoynOOYZ/nVohU1m1r6bp13UdU9prAcjMqKivmTlCkYI598bd99NmmzLtcYH…
Affected pages/ /dota2 /index /nod /roo
Component · Ref QXHJNU
Affected pagehttps://eseachellenger.com/dota2
Elementa > div > div > div > div > img
Markup
<img src="../assets/img/dota2thefun.jpg" alt="Thumbnail" class="dis--inl-blk z--0 centering w--100 h--100" loading="lazy" style="object-fit: cover;">
Affected pages/ /dota2 /index

05 · Most affected inspected pages

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.

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