A lot of eslint rules and reusable components already exist for accessibility in HTML, Javascript and React. When working with developers with varying levels of theoretical and practical experience with accessibility implementations, we realised that the mistakes that our devs were making with respect to accessible implementations, were either not general enough to have an existing eslint rule and / or the mitigation was very specific to the usages in our codebase. We started with a simple thought: can we automate the detection and fixes for these repeated mistakes?
