I'm trying to come up with Linter rules that the Herb Linter could ship with, so far I got these:
https://github.com/marcoroth/herb/issues?q=is%3Aissue%20state%3Aopen%20label%3Alinter
@marcoroth that may represent a lot, but I would appreciate linter rules to enforce accessibility good practices would be helpful.
Itβs something that I appreciated a lot when working on EmberJS projects to be guided on the a11y path
@notgrm oh yes, 100%!
I think Rails developers usually aren't too aware of a11y issues (myself included).
I wasn't aware of this project, but this is definitely the kind of intelligence I want to have built-in, this is great! Thanks!
@marcoroth I still have a bunch that remains to open; sorry for the spam tho π
Next step will be to contribute πͺ
@remi ah yeah, this one is tricky.
I think I do have a generally applicable and opinionated rule of how I would write it, but I can also see how people would be upset with it π π