Lucas and Luna dig into a specific case from May 2026: a major fintech app's checkout flow broke for screen-reader users after a seemingly harmless CSS update. They walk through how the bug slipped past unit and visual regression tests, why the team missed it, and what they changed to catch it next time. Luna brings data from WebAIM's 2025 screen-reader survey showing 67% of users encounter accessibility barriers monthly. Lucas explains the three-layer testing strategy the fintech team adopted: automated axe-core checks in CI, manual keyboard-only walkthroughs, and real screen-reader sessions on every release candidate. They also touch on the cost of ignoring accessibility — including a class-action lawsuit threat that got the company's attention. The episode ends with a practical takeaway: you don't need a dedicated accessibility team to start catching these bugs. A concrete number, one real company's mistake, and a fix any team can borrow.

#AccessibilityTesting #AxeCore #ScreenReader #WebAIM #Fintech #CSSBug #CheckoutFlow #CI #WCAG #DisabilityInTech #InclusiveDesign #ManualTesting #QA #SoftwareTesting #Technology #FexingoBusiness #BusinessPodcast #Episode33

Keep every episode free: buymeacoffee.com/fexingo