Automated Accessibility Testing: A Key to Compliance
Discover how automated accessibility testing can streamline compliance with WCAG 2.1 AA while enhancing user experience in your digital products.
April 25, 20264 min read
Read more
Technical insights, tutorials, and updates from the RIDLY team.
Discover how automated accessibility testing can streamline compliance with WCAG 2.1 AA while enhancing user experience in your digital products.
WCAG 2.1 AA is now mandatory for EU e-commerce. This is the working reference we use on our own client projects — requirements, penalties, audit methodology, and a 90-day remediation plan.
There's a scene in The Matrix where Neo gets a cable plugged into his head, a few seconds of loading — and then he says: "I know kung fu." The audience applauds. The screenwriters are brilliant. But if Neo had gone straight to fight Agent Smith after that — he would have died in the first minute. Because he knew the moves. He had zero experience using them in a real fight.
have been with Magento for over 15 years. I built my first store on Magento 1 when it was practically the only serious e-commerce option. I migrated clients to Magento 2 when Adobe took over. I watched the community split between "stay monolith" and "go headless." I have seen the best and the worst this platform has to offer.
New technologies emerge faster than teams can evaluate them. Platforms that looked like the safe bet three years ago are now legacy. Vendors change pricing models. Standards shift. And every time the market moves, someone is left holding an architecture that made perfect sense when they built it — and now costs a fortune to change I've spent fifteen years in e-commerce watching this happen. And after enough migrations, rebuilds, and conversations with CTOs who couldn't sleep at night — I stopped asking "what's the best technology right now" and started asking a different question: <b>what architecture gives you the right to change your mind later?
I was not planning to write a separate article about Core Web Vitals. For me it has always been obvious — a store should be fast, period. But after dozens of conversations with store owners and agencies I realized the topic is far more confusing than it seems. People either do not understand what CWV is, or understand but do not know what to do about it, or know what to do but do not have the resources. So let me break it all down. Why CWV Is Not a Developer Metric — It Is Money Core Web Vitals are three metrics Google uses to evaluate how pleasant it is for a user to interact with your site. Not how beautiful the design is. Not how wide the product range is. How fast the page loads, how stable things appear, and how quickly the site responds to actions. Three metrics: LCP (Largest Contentful Paint) — how long until the largest element on the page becomes visible. For a store this is usually the main product image or a homepage banner. Google says good is under 2.5 seconds. Over 4 is poor.ф INP (Interaction to Next Paint) — how long from the moment a user clicks a button until the site reacts. Added to cart — and then what? Froze for a second? Two? INP measures this. Good is under 200 milliseconds. CLS (Cumulative Layout Shift) — how much the page jumps during loading. You know that moment when you are about to tap "Buy Now" and a banner loads at the top and the button shifts down and you tap something else entirely? That is CLS. Good is below 0.1.
This idea has been with me for a long time. I have over 15 years of experience in e-commerce — I've seen projects across the widest range of niches: from kitchenware and recipe stores to building materials and complex B2B platforms. And throughout all of it, I kept noticing the same pattern: e-commerce stores rarely have a proper mobile app. Or they have nothing at all.