Public accessibility assessment

Accessibility issues detected on semvid50.wiki

Evolize inspected 5 public pages on semvid50.wiki and detected 17 automatically identifiable accessibility findings.

17Findings detected
3WCAG criteria affected
5Pages inspected
26 Aug 2026Assessment date

Highest detected severity: High · 1 high-priority finding · 100% inspected-page coverage

Most widespread issueText has insufficient colour contrastDetected on 5 inspected pages
Most affected page/9 findings detected
Most represented WCAG criterionWCAG 2.5.8 — Target Size (Minimum)9 detected findings

Is semvid50.wiki 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 semvid50.wiki and detected 17 accessibility findings. The most widespread issue was "Text has insufficient colour contrast", detected on 5 inspected pages. The most affected inspected page was "/", where 9 findings were detected. The assessment identified findings mapped to 3 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. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 3 inspected pages · 5 instances
    Why this 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 action

    To fix this issue, ensure that the button is either visible when it receives focus or is removed from the tab order when it's not visible. You can do this by adding a 'display: none' or 'visibility: hidden' style when the button is not intended to be visible, or by using JavaScript to remove the button from the tab order when it's not visible.

    View technical evidence →
  2. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 4 inspected pages · 12 instances
    Why this matters

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

    Recommended action

    Increase the size of the touch target to at least 24x24px to make it easier for users to activate by touch. Consider using CSS to adjust the padding or width of the element.

    View technical evidence →
  3. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 4 inspected pages · 4 instances
    Why this matters

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

    Recommended action

    Increase the touch target size of the interactive element to at least 24x24px to make it easier for users to activate by touch.

    View technical evidence →
  4. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 3 inspected pages · 11 instances
    Why this matters

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

    Recommended action

    To fix this issue, ensure that all interactive elements, such as buttons and links, have a minimum touch target size of 24x24 pixels. Consider increasing the padding or size of the element to meet this requirement.

    View technical evidence →
  5. Medium

    Text has insufficient colour contrast

    WCAG 1.4.3 (AA) · 3 inspected pages · 5 instances
    Why this matters

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

    Recommended action

    Increase the contrast between the text color and background color of the link to meet the minimum contrast ratio thresholds. This can be achieved by changing the CSS styles for the link or its parent element to use a color combination with sufficient contrast.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
2.5.8Target Size (Minimum)AA944 / 5
1.4.3Contrast (Minimum)AA755 / 5
2.4.3Focus OrderA133 / 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

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)5 instances3 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 the button is either visible when it receives focus or is removed from the tab order when it's not visible. You can do this by adding a 'display: none' or 'visibility: hidden' style when the button is not intended to be visible, or by using JavaScript to remove the button from the tab order when it's not visible.

View 5 affected elements
Component · Ref 284WZ0
Affected pagehttps://semvid50.wiki/
Elementdialog#image-viewer > form > button
Accessible nameClose image
Markup
<button class="image-viewer-close" aria-label="Close image"><span aria-hidden="true">×</span></button>
Affected pages/ /about /semvid_virus
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)302 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

Increase the contrast between the text color and background color of the link to meet the minimum contrast ratio thresholds. This can be achieved by changing the CSS styles for the link or its parent element to use a color combination with sufficient contrast.

View 302 affected elements
Component · Ref RH8IIK
Affected pagehttps://semvid50.wiki/timeline/
Element.external
Accessible nameCC Attribution-Noncommercial-Share Alike 4.0 International
Markup
<a class="external" rel="license noopener" href="https://creativecommons.org/licenses/by-nc-sa/4.0/deed.en">CC Attribution-Noncommercial-Share Alike 4.0 International</a>
Affected pages/all-pages /semvid_virus /timeline
Component · Ref QFOF51
Affected pagehttps://semvid50.wiki/
Elementp:nth-child(1) > .external-wikipedia[rel="noopener"]:nth-child(1)
Accessible nameSchwarzhorn
Markup
<a href="https://en.wikipedia.org/wiki/Schwarzhorn_%28Fl%C3%BCela%29" class="external-wikipedia" rel="noopener">Schwarzhorn</a>
Affected pages/ /semvid_virus
Component · Ref XSC6J9
Affected pagehttps://semvid50.wiki/about/
Elementp:nth-child(5) > .external[rel="noopener"]:nth-child(1)
Accessible nameDr. Adrian Lison
Markup
<a class="external" rel="noopener" href="https://bsse.ethz.ch/cevo/the-group/people/person-detail.adrian-lison.html">Dr. Adrian Lison</a>
Affected pages/ /about
Component · Ref 88YY09
Affected pagehttps://semvid50.wiki/
Element.external-wikipedia[rel="noopener"]:nth-child(10)
Accessible namepermafrost
Markup
<a href="https://en.wikipedia.org/wiki/Permafrost" class="external-wikipedia" rel="noopener">permafrost</a>
Affected pages/ /semvid_virus
Component · Ref XSC6LK
Affected pagehttps://semvid50.wiki/about/
Elementa[href$="cevo"]
Accessible nameComputational Evolution Group
Markup
<a class="external" rel="noopener" href="https://bsse.ethz.ch/cevo">Computational Evolution Group</a>
Affected pages/ /about
Component · Ref DP9ZVF
Affected pagehttps://semvid50.wiki/all-pages/
Elementtspan[x="-254.8"][dy="19"]
Accessible nameConspiracy Theories
Markup
<tspan x="-254.8" dy="19">Conspiracy Theories</tspan>
Component · Ref 8WN3W7
Affected pagehttps://semvid50.wiki/semvid_virus/
Elementtr:nth-child(1) > td > .external-wikipedia[rel="noopener"]
Accessible nameRiboviria
Markup
<a href="https://en.wikipedia.org/wiki/Riboviria" class="external-wikipedia" rel="noopener">Riboviria</a>
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)60 instances4 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 touch target to at least 24x24px to make it easier for users to activate by touch. Consider using CSS to adjust the padding or width of the element.

View 60 affected elements
Component · Ref X5OH21
Affected pagehttps://semvid50.wiki/about/
Elementheader > div > nav > ul > li:nth-of-type(1) > a
Accessible nameHome
Markup
<a href="/">Home</a>
Affected pages/ /about /all-pages /timeline
Component · Ref 7249ES
Affected pagehttps://semvid50.wiki/about/
Elementhtml > body > aside > p > a
Accessible namehere for more about this project
Markup
<a href="/about/">here<span class="visually-hidden"> for more about this project</span></a>
Affected pages/ /about /all-pages /timeline
Component · Ref KM4J9F
Affected pagehttps://semvid50.wiki/timeline/
Elementdiv > nav > details > ol > li:nth-of-type(1) > a
Accessible name2050
Markup
<a href="#2050">2050</a>
Affected pages/ /about /timeline
Component · Ref 3J8NBZ
Affected pagehttps://semvid50.wiki/timeline/
Elementdetails > ol > li:nth-of-type(1) > ol > li:nth-of-type(1) > a
Accessible nameJune
Markup
<a href="#june">June</a>
Affected pages/ /timeline
Component · Ref FSVKR9
Affected pagehttps://semvid50.wiki/all-pages/
Elementdiv > div > section:nth-of-type(1) > ul > li:nth-of-type(1) > a
Accessible nameConspiracy Theories During SEMViD-50
Markup
<a href="/conspiracy_theories_during_semvid-50/">Conspiracy Theories During SEMViD-50</a>
Component · Ref 0QQS6Y
Affected pagehttps://semvid50.wiki/about/
Elementarticle > div > details:nth-of-type(1) > ul > li:nth-of-type(3) > a:nth-of-type(1)
Accessible nameContagion
Markup
<a class="external-wikipedia" rel="noopener" href="https://en.wikipedia.org/wiki/Contagion_(2011_film)">Contagion</a>
Component · Ref O1F4VU
Affected pagehttps://semvid50.wiki/about/
Elementmain#main > article > div > p:nth-of-type(1) > a:nth-of-type(1)
Accessible namefictional pandemic
Markup
<a href="/">fictional pandemic</a>
Component · Ref 4I1Z95
Affected pagehttps://semvid50.wiki/timeline/
Elementli:nth-of-type(1) > ol > li:nth-of-type(1) > ol > li > a
Accessible nameJune 28
Markup
<a href="#june-28">June 28</a>
Component · Ref CF40KO
Affected pagehttps://semvid50.wiki/about/
Elementdiv > details:nth-of-type(2) > section:nth-of-type(1) > ul:nth-of-type(2) > li:nth-of-type(4) > a
Accessible nameAbout 1Day Sooner
Markup
<a class="external" rel="noopener" href="https://www.1daysooner.org/about/">About 1Day Sooner</a>

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.