The latest articles on DEV Community by Daniel Morgan (@daniel_morgan_23). https://dev.to/daniel_morgan_23 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3791148%2Fe2cabe34-7f53-49d1-9a99-0d1464ac66ca.png https://dev.to/daniel_morgan_23 en Daniel Morgan Fri, 13 Mar 2026 08:29:10 +0000 https://dev.to/daniel_morgan_23/do-any-vs-code-extensions-suggest-accessibility-fixes-while-coding-i2i https://dev.to/daniel_morgan_23/do-any-vs-code-extensions-suggest-accessibility-fixes-while-coding-i2i <p>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.</p> <p>It recommends things like missing <strong>attributes, ARIA roles,</strong> and other <strong>accessibility best practices</strong> as you type. </p> <p>The extension is called <a href="https://www.barrierbreak.com/a11yinspect-vs-code-extension/" rel="noopener noreferrer">A11yInspect</a>, and it basically makes IntelliSense accessibility aware. </p> <p>I thought that was an interesting approach because as we all know accessibility issues often show up much later during testing. </p> <p>Do developers here rely on extensions like this, or do you mostly handle accessibility during QA or audits?</p> <h1> devtools #vscode #webdev #accessibility </h1> a11y discuss tooling vscode