Public accessibility assessment

Accessibility issues detected on spoko.space

Evolize inspected 5 public pages on spoko.space and detected 85 automatically identifiable accessibility findings.

85Findings detected

5WCAG criteria affected

5Pages inspected

9 Sep 2026Assessment date

Highest detected severity: High · 7 high-priority findings · 100% inspected-page coverage

Most widespread issueHidden elements can still receive keyboard focusDetected on 5 inspected pages

Most affected page/category/ai39 findings detected

Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)65 detected findings

Is spoko.space your website?

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

ACTIVATE MONITORING RUN A FREE ASSESSMENT

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on spoko.space and detected 85 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 5 inspected pages. The most affected inspected page was "/category/ai", where 39 findings were detected. The assessment identified findings mapped to 5 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.

High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 5 inspected pages · 35 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
Keep 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.
View technical evidence →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 5 inspected pages · 25 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
Keep 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.
View technical evidence →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 5 inspected pages · 15 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
Keep 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.
View technical evidence →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 5 inspected pages · 10 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
Keep 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.
View technical evidence →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 5 inspected pages · 10 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
Keep 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.
View technical evidence →

03 · WCAG criteria affected

Criterion	Name	Level	Findings	Pages	Reach
1.4.3	Contrast (Minimum)	AA	65	5	5 / 5
2.5.8	Target Size (Minimum)	AA	12	5	5 / 5
2.4.3	Focus Order	A	6	5	5 / 5
1.3.1	Info and Relationships	A	1	1	1 / 5
4.1.2	Name, Role, Value	A	1	1	1 / 5

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

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)100 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

Keep 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.

View 100 affected elements

Component · Ref WSRBS2

Affected pagehttps://spoko.space/contact/

Elementdiv#consent-panel > button

Accessible nameSave choice

Markup

<button class="btn btn-secondary consent__save" type="button" data-astro-cid-vequyegh="" data-consent-save="">Save choice</button>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref KQYCYN

Affected pagehttps://spoko.space/contact/

Elementheader#header > div:nth-of-type(1) > div > div:nth-of-type(2) > div > a:nth-of-type(2)

Accessible namePolski

Markup

<a href="/pl/kontakt/" class="lang-segmented-btn" aria-label="Polski" hreflang="pl">PL</a>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref 9BXSK7

Affected pagehttps://spoko.space/web-application-development-services/

Elementsection:nth-of-type(1) > div > div > ul > li:nth-of-type(1) > a

Accessible nameWeb applications

Markup

<a href="/web-application-development-services/" class="post-tag" data-astro-cid-unvtsuh5="">Web applications</a>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref KJVZ98

Affected pagehttps://spoko.space/

Elementaside#site-menu-drawer > nav > a:nth-of-type(3)

Accessible nameWordPress rescue Fixes, speed-up, monthly care

Markup

<a href="/wordpress-rescue/" class="menu-drawer-primary-link"><div class="menu-drawer-primary-text"><span class="menu-drawer-primary-title">WordPress rescue</span> <span class="menu-drawer-primary-sub">Fixes, speed-up, monthly care</span></div><svg viewBox="0 0 24 24" class="menu-drawer-primary-arrow" data-icon="tabler:arrow-right" height="1em" width="1em"><use href="#ai:tabler:arrow-right"></use></svg> </a>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref XFZ5H0

Affected pagehttps://spoko.space/contact/

Elementdiv#consent-panel > ul > li:nth-of-type(2) > button

Accessible nameAnalytics

Roleswitch

Markup

<button class="consent__switch" type="button" data-astro-cid-vequyegh="" aria-checked="false" aria-labelledby="consent-analytics-label" data-consent-switch="" role="switch"><span class="consent__knob" aria-hidden="true" data-astro-cid-vequyegh=""></span></button>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref JT26OP

Affected pagehttps://spoko.space/contact/

Elementaside#site-menu-drawer > header > button

Accessible nameClose menu

Markup

<button class="menu-drawer-close" type="button" aria-label="Close menu" data-menu-drawer-close=""><span class="menu-drawer-close-icon" aria-hidden="true"><span></span> <span></span></span></button>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

High

ARIA hidden element must not be focusable or contain focusable elements

WCAG 4.1.2 (A)4 instances1 inspected page

ARIA hidden element must not be focusable or contain focusable elements

Why it matters

ARIA hidden element must not be focusable or contain focusable elements

Recommended correction

Review the affected element and correct the reported accessibility issue.

View 4 affected elements

Component · Ref UDMDMK

Affected pagehttps://spoko.space/category/ai/

Element.mb-12.md\:mb-20:nth-child(2) > article > .absolute.inset-0.z-1

Markup

<a href="/blog/zapiszprzepis-ai-first-app/" class="z-1 absolute inset-0" aria-hidden="true"></a>

Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)297 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 ratio to at least 4.5:1 for normal text and 3:1 for large text.

View 297 affected elements

Component · Ref 3FX82D

Affected pagehttps://spoko.space/web-application-development-services/

Elementa[href$="terms/"]

Accessible nameTerms of use

Markup

<a href="/terms/">Terms of use</a>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref I4EJI7

Affected pagehttps://spoko.space/category/ai/

Element.consent__text

Accessible nameI collect anonymous visit statistics in Google Analytics to see which posts people actually read. Until you agree, they are counted without cookies. Privacy policy

Markup

<p class="consent__text" data-astro-cid-vequyegh="">I collect anonymous visit statistics in Google Analytics to see which posts people actually read. Until you agree, they are counted without cookies. <a href="/privacy/" class="consent__policy" data-astro-cid-vequyegh="">Privacy policy</a></p>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref BKVTDS

Affected pagehttps://spoko.space/

Element.site-header-pill-cta

Accessible nameContact

Markup

<a href="/contact/" class="not-prose btn-primary site-header-pill-cta" rel="noopener noreferrer" target="_self">Contact</a>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref TGMR5M

Affected pagehttps://spoko.space/category/ai/

Element.site-footer__legal > a[href$="privacy/"]

Accessible namePrivacy policy

Markup

<a href="/privacy/">Privacy policy</a>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref S78A6I

Affected pagehttps://spoko.space/category/ai/

Element.site-footer__made > span:nth-child(2)

Accessible nameMADE IN POLAND

Markup

<span>MADE IN POLAND</span>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref UAB5IW

Affected pagehttps://spoko.space/category/ai/

Element.site-footer__cookies

Accessible nameCookie settings

Markup

<button class="site-footer__cookies" type="button" data-consent-reopen="">Cookie settings</button>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref SMZGDU

Affected pagehttps://spoko.space/blog/magento-open-source-end-of-support/

Elementbutton[data-consent-accept=""]

Accessible nameAccept

Markup

<button type="button" class="btn btn-primary consent__btn" data-astro-cid-vequyegh="" data-consent-accept="">Accept</button>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref DNW2AA

Affected pagehttps://spoko.space/contact/

Element.site-header-utility-sep[aria-hidden="true"]:nth-child(4)

Accessible name·

Markup

<span class="site-header-utility-sep" aria-hidden="true">·</span>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref LLIE8T

Affected pagehttps://spoko.space/web-application-development-services/

Element.site-footer__copy

Markup

<p class="site-footer__copy">© 2026 spoko<span class="site-footer__dot">.</span>space</p>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref VZUK0M

Affected pagehttps://spoko.space/category/ai/

Element

.site-header-utility-right > .lang-segmented[role="group"][aria-label="Language"] > .lang-segmented-btn[aria-label="Polski"][hreflang="pl"]

Accessible namePolski

Markup

<a href="/pl/category/ai/" class="lang-segmented-btn" aria-label="Polski" hreflang="pl">PL</a>

Affected pages/ /category/ai /contact /web-application-development-services

Component · Ref XRSMYC

Affected pagehttps://spoko.space/web-application-development-services/

Elementa[aria-label="WhatsApp +48 692 355 180"] > span

Accessible name+48 692 355 180

Markup

<span>+48 692 355 180</span>

Affected pages/ /category/ai /contact /web-application-development-services

Component · Ref LTNKT9

Affected pagehttps://spoko.space/web-application-development-services/

Element.site-header-pill-menu-label

Accessible nameMenu

Markup

<span class="site-header-pill-menu-label">Menu</span>

Affected pages/ /category/ai /contact /web-application-development-services

Component · Ref NCX7RF

Affected pagehttps://spoko.space/category/ai/

Element.site-header-utility-item[href="mailto:[email removed]"] > span

Accessible name[email removed]

Markup

<span>[email removed]</span>

Affected pages/ /category/ai /contact /web-application-development-services

Component · Ref KSI1LX

Affected pagehttps://spoko.space/

Element#consent-title

Accessible nameCookies and analytics

Markup

<h2 class="consent__title" data-astro-cid-vequyegh="" id="consent-title" tabindex="-1">Cookies and analytics</h2>

Affected pages/ /contact /blog/magento-open-source-end-of-support

Component · Ref V063LV

Affected pagehttps://spoko.space/

Element.font-normal

Accessible nameA website or web app for your business?

Markup

<span class="text-muted font-normal">A website or web app for your business?</span>

Affected pages/ /contact /blog/magento-open-source-end-of-support

Component · Ref TPA7XU

Affected pagehttps://spoko.space/blog/magento-open-source-end-of-support/

Element.consent__policy

Accessible namePrivacy policy

Markup

<a href="/privacy/" class="consent__policy" data-astro-cid-vequyegh="">Privacy policy</a>

Affected pages/ /category/ai /blog/magento-open-source-end-of-support

Component · Ref B3X2RC

Affected pagehttps://spoko.space/category/ai/

Element.is-current > .blog-side__label[data-astro-cid-rmfyhdrx=""]

Accessible nameAI

Markup

<span class="blog-side__label" data-astro-cid-rmfyhdrx="">AI</span>

Component · Ref W0KKXT

Affected pagehttps://spoko.space/

Element.about-section__bullets > li:nth-child(3) > span

Accessible nameFast and visible in Google

Markup

<span>Fast and visible in Google</span>

Component · Ref ZWQRI4

Affected pagehttps://spoko.space/

Element.about-section__p:nth-child(2)

Accessible nameYou work with me directly, from the first conversation to launch. No account managers, no handing the job to subcontractors. I'm based in Bielsko-Biała and work with clients in Poland and abroad.

Markup

<p class="about-section__p">You work with me directly, from the first conversation to launch. No account managers, no handing the job to subcontractors. I'm based in Bielsko-Biała and work with clients in Poland and abroad.</p>

Component · Ref V9XXVA

Affected pagehttps://spoko.space/

Element.about-section__links > a[href$="about/"]

Accessible nameMore about me →

Markup

<a href="/about/">More about me →</a>

Component · Ref M8V7IH

Affected pagehttps://spoko.space/

Element.about-section__h2

Accessible nameHi, I'm Szymon

Markup

<h2 class="about-section__h2">Hi, I'm Szymon</h2>

Component · Ref M8ISFM

Affected pagehttps://spoko.space/

Element.about-section__eyebrow

Accessible nameLet's meet

Markup

<div class="about-section__eyebrow">Let's meet</div>

Component · Ref MFNIFH

Affected pagehttps://spoko.space/contact/

Elementh1

Accessible nameWrite to me

Markup

<h1 class="text-default font-heading font-semibold hero-halo mb-4 md:text-6xl/[1.07] text-5xl/[1.07] tracking-[-0.035em]">Write <span class="text-accent">to me</span></h1>

Affected pages/category/ai /contact

Component · Ref JJJ2B7

Affected pagehttps://spoko.space/web-application-development-services/

Element#contact-form-submit

Accessible nameSend inquiry

Markup

<button class="btn-primary" type="submit" data-astro-cid-2lkv3ujd="true" id="contact-form-submit">Send inquiry</button>

Affected pages/contact /web-application-development-services

Component · Ref PBLAFS

Affected pagehttps://spoko.space/web-application-development-services/

Element.sm\:mb-0.btn-primary[href$="#contact-form"]

Accessible nameGet a quote

Markup

<a href="#contact-form" class="not-prose btn-primary sm:mb-0 w-full">Get a quote</a>

Showing 25 representative examples · 40 more affected elements not shown

Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)43 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 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: 87 × 17 CSS pixels; required minimum: 24 × 24 CSS pixels.

View 43 affected elements

Component · Ref 7TD72F

Affected pagehttps://spoko.space/category/ai/

Elementdiv#consent-banner > div:nth-of-type(1) > div > p > a

Accessible namePrivacy policy

Markup

<a href="/privacy/" class="consent__policy" data-astro-cid-vequyegh="">Privacy policy</a>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref 3A8TKT

Affected pagehttps://spoko.space/

Elementbody > footer > div:nth-of-type(1) > div > div:nth-of-type(2) > a:nth-of-type(2)

Accessible name+48 692 355 180

Markup

<a href="https://wa.me/48692355180" target="_blank" rel="noopener">+48 692 355 180</a>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref PGE4FV

Affected pagehttps://spoko.space/contact/

Elementbody > footer > div:nth-of-type(2) > div > nav > a:nth-of-type(2)

Accessible nameTerms of use

Markup

<a href="/terms/">Terms of use</a>

Affected pages/ /category/ai /contact /blog/magento-open-source-end-of-support /web-application-development-services

Component · Ref T12UNH

Affected pagehttps://spoko.space/contact/

Elementinput#disclaimer

Markup

<input name="disclaimer" type="checkbox" id="disclaimer" class="block bg-white border border-gray-200 dark:bg-slate-900 dark:border-gray-700 px-4 py-3 rounded-lg text-md w-full cursor-pointer mt-1" required="" data-astro-cid-2lkv3ujd="">

Affected pages/contact /web-application-development-services

Component · Ref 0US1JU

Affected pagehttps://spoko.space/category/ai/

Elementarticle > div:nth-of-type(2) > header > div > span > a

Accessible nameAI

Markup

<a href="/category/ai/" class="relative z-2 hover:underline">AI</a>

Component · Ref BKSS1W

Affected pagehttps://spoko.space/

Elementmain#main > section:nth-of-type(11) > div > p > a

Accessible nameSee all articles →

Markup

<a href="/blog/">See all articles →</a>

Component · Ref B9WT94

Affected pagehttps://spoko.space/

Elementsection:nth-of-type(10) > div > div:nth-of-type(3) > div > p:nth-of-type(3) > a

Accessible nameVerify →

Markup

<a href="https://credsverse.com/credentials/d9f99ad8-ed75-4c81-a8ae-2a014d385725" target="_blank" rel="noopener noreferrer">Verify →</a>

Component · Ref T07FNY

Affected pagehttps://spoko.space/blog/magento-open-source-end-of-support/

Elementdiv#article-content > p:nth-of-type(149) > a

Accessible namedrop me a line

Markup

<a href="/contact">drop me a line</a>

Component · Ref 7WOTU9

Affected pagehttps://spoko.space/web-application-development-services/

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

Accessible namewebsite

Markup

<a href="/web-development/">website</a>

Component · Ref EKXISY

Affected pagehttps://spoko.space/blog/magento-open-source-end-of-support/

Elementarticle#article > header > div:nth-of-type(1) > p > a

Accessible nameE-commerce

Markup

<a href="/category/e-commerce/" class="hover:underline uppercase" data-astro-cid-wo4vtnkt="">E-commerce</a>

Low

Navigation regions are not distinguishable

WCAG 1.3.1 (A)4 instances1 inspected page

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Why it matters

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Recommended correction

Give each navigation region a distinct aria-label (e.g. "Primary", "Footer") when more than one is present.

View 4 affected elements

Component · Ref AEKMYD

Affected pagehttps://spoko.space/blog/magento-open-source-end-of-support/

Elementnav#toc-panel-nav

Accessible nameA short history: how we got to “the end of Magento”What Adobe actually announced — the official timelineThe nuance the infographics don’t show: Open Source has it worse than Adobe CommerceNobody measures the scale of the problem consistentlyWhat actually happens under the hood when you stay on an unsupported versionSecurityPCI DSS and compliancePayment and shipping integrationsE-invoicing and tax automationPHP, MySQL, and infrastructureGrowing technical debtHosting and maintenance — what the platform itself doesn’t costFour real paths — from a cost and operations perspectivePath 1: Upgrade within Magento Open Source (to 2.4.8)Path 2: Adobe Commerce (the paid ecosystem)Path 3: Migration to another platformPath 4: Mage-OS + Hyvä — the option nobody with a marketing budget pushesComparison table — what you’re actually choosingB2B vs B2C — different paths for different modelsMigration and SEO — the playbook you can’t get wrongThings that must be done before the migration:After the migration:Three real migration patterns I see most oftenScenario A: mid-sized B2C on Magento Open Source 2.4.4 → Mage-OS + HyväScenario B: mid-market B2C on Magento 2.4.5 → Shopify PlusScenario C: B2B on Magento 2.4.6 → SaleorDecision tree — how I think this throughMigration plan, week by weekWhat not to do in a migration planMyths I hear regularlyThe timeline I keep for clientsWhat’s next — AI, agentic commerce, edge deliveryIn short: is the panic justified?Frequently Asked Questions

Markup

<nav data-astro-cid-ymbpksfa="" id="toc-panel-nav"><a href="#a-short-history-how-we-got-to-the-end-of-magento" class="toc-panel-link toc-active" data-astro-cid-ymbpksfa="" data-id="a-short-history-how-we-got-to-the-end-of-magento" aria-current="location">A short history: how we got to “the end of Magento”</a><a href="#what-adobe-actually-announced--the-official-timeline" class="toc-panel-link" data-astro-cid-ymbpksfa="" data-id="what-adobe-actually-announced--the-official-timeline">What Adobe actually announced — the official timeline</a><a href="#the-nuance-the-infographics-dont-show-open-sou…

Low

Touch targets are too small

WCAG 2.5.8 (AA)30 instances1 inspected page

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 this <button>'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.

View 30 affected elements

Component · Ref RMXAW4

Affected pagehttps://spoko.space/blog/magento-open-source-end-of-support/

Elementbutton[aria-label="Growing technical debt"]

Accessible nameGrowing technical debt

Markup

<button type="button" class="toc-dot-btn" aria-label="Growing technical debt" data-astro-cid-ymbpksfa="" data-depth="3" data-id="growing-technical-debt"><span class="toc-dot" aria-hidden="true" data-astro-cid-ymbpksfa=""></span></button>

Component · Ref HARAUL

Affected pagehttps://spoko.space/blog/magento-open-source-end-of-support/

Element.toc-dot-btn[data-depth="3"]:nth-child(24)

Accessible nameScenario A: mid-sized B2C on Magento Open Source 2.4.4 → Mage-OS + Hyvä

Markup

<button type="button" class="toc-dot-btn" aria-label="Scenario A: mid-sized B2C on Magento Open Source 2.4.4 → Mage-OS + Hyvä" data-astro-cid-ymbpksfa="" data-depth="3" data-id="scenario-a-mid-sized-b2c-on-magento-open-source-244--mage-os--hyvä">

05 · Most affected inspected pages

/category/ai/High40 findings
/
High
38 findings
/blog/magento-open-source-end-of-support/High38 findings
/web-application-development-services/High38 findings
/contact/High31 findings

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.

ACTIVATE MONITORING SEE PRICING

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

Accessibility issues detected on spoko.space

Is spoko.space your website?

01 · Accessibility summary

02 · Start here

Hidden elements can still receive keyboard focus

Hidden elements can still receive keyboard focus

Hidden elements can still receive keyboard focus

Hidden elements can still receive keyboard focus

Hidden elements can still receive keyboard focus

03 · WCAG criteria affected

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

04 · All detected findings

Hidden elements can still receive keyboard focus

ARIA hidden element must not be focusable or contain focusable elements

Text has insufficient colour contrast

Touch targets are too small on mobile

Navigation regions are not distinguishable

Touch targets are too small

05 · Most affected inspected pages

06 · About this assessment

07 · Continuous monitoring

Reports with similar accessibility findings