My accessibility is broken!

You are now ready to release version 2.0 of your flagship product! In version 1.0 you were very concerned about accessibility, and you even hired a consultant who helped you make it 100% accessible.

You release the version... and suddenly, you start getting tweets from a lot of angry users telling you that what was once accessible is no longer accessible. The first thing you think about: damned twitter! And the second thing: what happened? How could such a regression have occurred?

In this talk I will tell you how to keep your website accessible over time, without having to constantly perform manual tests every time you make a change in the interface. We will learn how to create automated tests (analyzing entire pages or individual components), and even create tests using screen readers, all fully automated, and include them as part of your CI/CD flow.

Thanks to this talk, you will be able to make accessibility a mainstay of your product, preventing any accessibility issues from being published in production. Now your pull requests will also take into account accessibility tests as an additional quality parameter before they are approved!

Don't let the effort invested in accessibility be carried away by entropy! :)