Accessible web testing with Cypress and wick-a11y

I spent a couple of hours building a custom logging callback for cypress-axe. It formatted violations into a console table and registered Cypress tasks in the config file. It worked. Then I installed wick-a11y and got better output with zero custom code. This is the second article in my accessibility testing series. The first one covered Cypress with cypress-axe, and you can find it here: Accessible web testing with Cypress and Axe Core Vitaly Skadorva Vitaly Skadorva Vitaly Skadorva Follow for Cypress Mar 23 Accessible web testing with Cypress and Axe Core # cypress # a11y # testing # webdev Comments Add Comment 9 min read Sebastian Clavijo Suero ( @sebastianclavijo ) built wick-a11y on top of the same axe-core engine that powers cypress-axe. The difference is what happens after the scan. Where cypress-axe gives you a raw violations array and leaves the rest to you, wick-a11y processes the results into color-coded Cypress logs with visual highlighting in the runner, plus HTML reports