Namu CHO·Aug 23What I Learned Building a Web Accessibility Chrome ExtensionFrom font scaling to an SSRF vulnerability I found the day before open-sourcing it
Amber Anand·Aug 6Accessibility testing in CI/CD: catching failures before they shipAxe-core catches around 40% of WCAG issues. The other 60% still needs manual review. Here’s how to wire the 40% into your into your build…
Jenny Keeper·Jul 27How to Run a Mobile App Accessibility Audit Without Missing Critical IssuesThe first mobile app accessibility audit I led was far more intimidating than I expected. I knew the basics, and had a list of…
Daniel Sánchez 🇪🇸·Jul 212026 Series: Building Accessible Products — Accessibility Debt: The Hidden Cost Product Teams Keep…Accessibility isn’t something you fix at the end of a project. Like technical debt, it accumulates with every decision your team postpones…
Emmanuel Chilaka·May 1Testing React Accessibility with Axe: Dev Console, Vitest, and the Chrome ExtensionMost React developers don’t test accessibility until a compliance audit forces it. Then they spend two weeks firefighting: missing labels…
Emmanuel Oyeyipo·Apr 5Web Accessibility? What is that? What do we even need it for?You spend 3 weeks building a slick website. It looks beautiful. Then someone tells you they can’t use it at all. Why? Because they’re…
Thomas Augot·Mar 28How I Got My Next.js Portfolio to Score 100% on Lighthouse AccessibilityA practical, honest account of everything I changed, why it matters, and how you can apply the same patterns to any animated React app.
InThe Design LoopbyPolly Taylor·Jan 22From Compliance to Commitment: Our Journey Toward Accessibility by DefaultOur journey toward becoming an accessible by default product company, meeting WCAG and providing mobility for all, began with pragmatism.
