I was exploring ways to catch accessibility issues earlier in development and found an extension for Visual Studio Code that extends IntelliSense with accessibility suggestions.
It recommends things like missing attributes, ARIA roles, and other accessibility best practices as you type.
The extension is called A11yInspect, and it basically makes IntelliSense accessibility aware.
I thought that was an interesting approach because as we all know accessibility issues often show up much later during testing.
Do developers here rely on extensions like this, or do you mostly handle accessibility during QA or audits?
Top comments (3)
Thanks for sharing! Tried it out and works really well!
I am currently doing some research for integration of a11y checks for our pipeline, do you maybe have some recommendations for smth like that?
Some comments may only be visible to logged-in visitors. Sign in to view all comments.